Ledge & Coral projects have been stuck with 0.x releases for a very long time. This does not reflect on the actual status of this software which is deployed in a few production, large scale systems for several years now.
Here's my plans regarding releases and versions of Ledge & Coral in near future:
- next releases of Ledge & Coral will be versioned 1.0.0
- those releases will coincide with release of Cyklotron 2.5
- releases 1.0.0 will be not contain significant changes over current 0.3.15 / 0.1.11 releases
- unreleased versions currently in Jira will be dropped. issues with affects set to any of those versions will be pushed down to last released version, those with fix for set to any of those versions will get unscheduled
- the above means that all the open issues will end up as unscheduled for now. I'll create 1.0.x versions as I go and include issues that are actually needed / incidentally done in time for the upcoming release
- I'm going to drop the notion of documentation / testing centered releases - this concept did not work. I'll try to include some of these tasks in regular releases
- I'll fill in component information in Jira to give a better overview what's happening
- generally, I'm going to file LEDGE/CORAL issues whenever I do something in those projects - this way we'll have usable changelogs
- release cycles of Ledge & Coral will remain tied to Cyklotron releases for now. There's no compelling reason to do otherwise at this point
- all modules within each of the projects will go on the same release schedule for now. This is a bit superfluous because we re release much code with no changes at all, but it's easier to maintain. We can consider splitting up ledge modules into individual components to give them separate schedules later.