Milestones

List view

• Post-1.0

  The short list of important issues to resolve just after 1.0

  No due date

  •0/7 issues closed
  0% complete7 open0 closed

• Recycle Bin

  We don't know if we really need these issues anymore, but we aren't sure yet if we want to close them.

  No due date

  •0/9 issues closed
  0% complete9 open0 closed

• 1.0 - Nonessential

  No due date

  •8/123 issues closed
  6% complete115 open8 closed

• 1.0

  The 1.0 release of Azle. This release is considered ready for general production usage. An issue may only be included if it materially addresses one or more of the following areas of stability, security, or usability: - Stable API (few missing APIs/breaking changes are highly discouraged) - Public API JSDocs are accurate and sufficient (all Azle imports are documented with function signatures and descriptions) - Free from critical bugs and errors - Clean and simple developer experience (easy to install, easy to create functioning canister code, easy to deploy) - Only essential public API test coverage (end-to-end, property, fuzz) - Dependencies production-ready - Basic essential security processes (code review guidelines, private key rotation and protection, policies for things like this) - Internal Security Review (cleanup and comment as necessary) - External Security Review

  Overdue by 1 year(s)

  •

  Due by July 1, 2025

  •72/80 issues closed
  90% complete8 open72 closed

• Next

  Issues we might want to do eventually

  No due date

  •1/28 issues closed
  3% complete27 open1 closed

• Experimental

  No due date

  •3/62 issues closed
  4% complete59 open3 closed