|[libra-dev] Plans for Kepler|
Time passes really quickly. Juno SR1, Kepler M1 and M2 are already out. I haven’t noticed any changes in the Git repository since the Juno release in June, so for these deliveries the Libra content didn’t actually changed.
Perhaps, having no changes means that everything in Libra is quite stable and all adopters are satisfied enough with what we have. Nevertheless, it won’t hurt if we talk a little bit about planning for the Juno SR2 and the Kepler release.
For Juno SR2, I can see only one bug targeted . If anyone plans to do any fixes, please target them to the 0.2.2 milestone so we have the complete picture here.
For Kepler, I can see only one bug and one enhancement . Again, please document your intentions by targeting the respective bugs to the 0.3 milestone. And for the enhancements, please add the “plan” keyword, so it appears in our Kepler project plan .
At the end, if there isn’t many improvements planned for Kepler, then perhaps we may discuss whether it is time to get out of incubation and graduate Libra to version 1.0. We already have some really valuable features and if we are not going to change them significantly, then it would be better to declare them as mature, which may be an important sign for the broader community. There would be also some benefits like including these features in the Eclipse JEE EPP package. Currently, the rules for this EPP package is the it includes only mature (non-incubating) components.
I’ll be happy to hear your opinion about the direction for getting out of incubation. And, of course, I’ll be happy to hear anything else related to Libra and the Kepler release.