Andrei, we just released 4.4.3 save the release notes and hence the announcement. Full focus should be on stabalizing and finalizing 4.5.1, now. We didn't discuss going forth with 4.6 yet, though the topic of release management for 4.6 has passed the dev list. Are there any concerns you have with the 4.5 release in particular?
The idea of abandoning 4.5 in favour of 4.6 does not appeal to me much. <hat type="mycompany">We at our shop will probably be skipping 4.5.</hat>. I can not say much on release schedule/dates. I think making fixed promises makes only sense if we can easily abandon features that are proven to be unstable. At the moment our release process doesn't facilitate this. So the answer to your last question is yes. We are working to move away from this impediment and will probably vote for fixed short release cycles in the future where fixes go in 2 to 4 week cycles and features in 2 to 4 month cycles. Hope you agree. If not, this discussion is still open. On Tue, Apr 21, 2015 at 10:26 AM, Andrei Mikhailovsky <and...@arhont.com> wrote: > Hello guys, > > Looking at the dev and user lists it is becoming less certain if version > 4.5.x is ever coming out. It seems like a few months have passed since the > not so fortunate release of 4.5.0 and I can't find a release schedule for the > 4.5.1, which seems to have stopped at rc2 stage and haven't progressed > further to a release stage. > > Are we likely to see any progress with the 4.5.x branch or is the community > switching towards the 4.6.x branch without releasing the 4.5.x? > > I am a bit unclear as there are no release dates, schedules or dead lines > that the community should work with. Possibly as a result of this, the ACS > releases are not being released on time or fast enough. > > Does it make sense to introduce release schedules for ACS that the dev > community should stick to? Similar to what is being done in many other > projects, like Ubuntu, etc. Or would this break the ACS project releases even > more? > > Andrei -- Daan
