Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

... for any value of "X"

Like most software projects, sipXecs has approximate target dates for when any given release will happen. Like most software projects, those target dates are not always met.

The best way to watch the progress toward any given release is the sipXecs Project Roadmap page in the issue tracker. If you see lots of Unresolved issues, the release is probably not happening soon. If you don't see any Unresolved issues, it probably is soon (note however, that some issues that have commercial importance may not show, and some problems known to QA and/or the developers may not have been filed yet, so the picture is not always perfect). There is some lag from the last issues being Resolved to a release as the builds are subjected to final QA; sometimes, releases are posted in the public download areas during this period, but if you don't see an announcement on the list and the LatestStable link is not switched to it yet, then you should not consider it released yet.

The issue tracker is how we track everything we're doing... to see the flow for how an issue is created and progresses, see How to report a problem with sipXecs.

Will Release X fix XX-????

Two important things to note in an issue:

  • Fix Version
    in an Unresolved issue, this is the release (or sometimes releases) that we plan to address the issue.
    in a Resolved issue means that the issue has been addressed, and that's the release it will be available in.
    if Fix Version is empty, the issue is not scheduled for any release yet (which could be an oversight - feel free to ask on the mailing list)

Plans sometimes change, but you can use the Priority to get some idea of this:

  • Blocker or Critical
    issues are ones that we currently believe the release cannot do without. Any lower priority issues might be moved to a later release in order to avoid holding up features or fixes that the community needs more urgently.

You should also understand SipXecs - Open Source PBX and what it implies.

  • No labels