Skip to content

Milestones

List view

  • Vault

    Issues related to CodeSnip Vault

    No due date
    •1/1 issues closed
    100% complete0 open1 closed

  • Planned for next patch

    Issues that are planned for inclusion in next bug fix / hot fix / patch release. _May_ be included in a point release if one is due to be released within a suitable time.

    No due date
    •0/1 issues closed
    0% complete1 open0 closed

  • Confirmed for next patch

    Issues that are confirmed for inclusion in next bug fix / hot fix / patch release. _May_ be included in a point release if one is due to be released within a suitable time.

    No due date
    0% complete0 open0 closed

  • Planned for next v4.x release

    Accepted but incomplete issues that are scheduled to be included in the next point release (hotfix & patch releases excepted), but this is not guaranteed. The purpose of the milestone is to help users know which issues are likely to be implemented in the next release. Issues should be moved, to the _Confirmed for next v4.x release_ milestone when completed or if absolutely guaranteed to be included in the relsase.

    No due date
    0% complete0 open0 closed

  • Confirmed for next v4.x release

    Issues definitely to be included in next release (hotfix releases excepted). Such issues should either be completed or be guaranteed to be included in the release. The purpose of the milestone is to help users know that an issue is **definitely** to be included in the next release **and** to help with the creation of the change log. Issues should remain here until the release is made and then be removed from this milestone.

    No due date
    0% complete0 open0 closed

  • Planned for later v4.x release

    Accepted issues planned to be fixed in a **v4** release, but not to be included in the **next** scheduled release. Issues may be not started, in progress or completed **but** they must be left open. The purpose of this milestone is to inform users which accepted issues **will not** be included in the next release, but should be included in a subsequent v4 release rather than being deferred to v5.

    No due date
    •0/1 issues closed
    0% complete1 open0 closed