On Thu, Oct 21, 2010 at 01:08, Sergiu Dumitriu <[email protected]> wrote:
> On 10/20/2010 09:31 AM, Vincent Massol wrote: > > Hi, > > > > I'd like to propose that we have a short XE 2.6 release. The > > rationale is that we've been developing lots of new features in the > > past releases and I think it's time to stabilize what we have. By > > stabilize I mean: - fix bugs - homogenize UI - clean up stuff > > (refactoring, etc) > > I don't quite agree with only one quick release, but instead I'd propose > to sprint for a winter 3.0 release. I believe that since 2.0 we've added > (or started) enough new features to make up for a major release. > > So, I'd propose monthly releases until we get a polished version ready > to be promoted as 3.0. This means that the number of new features should > be kept to a minimum, trying to finish all the stuff that was already > started: gadgets, portlets (a bit difficult, so this is not a hard > requirement), new UIs (administration, multipage export, standard forms, > maybe rights), xwiki/2.1 syntax, extension manager. > I strongly agree with Sergui. There are many small issues (event not yet discovered) and annoyances that have been left back and that should not go into a 3.0 release. There is probably also some improvement on security required. So pursuing a while with regular 2.x release to stabilized the 3.0 release is for me a must. I know that I have not much time to participate these days, and hopelessly this will not improve soo, but I will try to helps as much as I can on these one. > > > In addition we have 2 features we had planned for 2.5 which have > > slipped and we could finish them in 2.6 too (Sergiu said he was > > almost done with the "Email this page" feature and didn't have the > > time to slip it in the 2.5): > > - Email this page: Sergiu > > - Recent Activity (refactoring of Recent Changes based on the Activity > > Stream): Raluca + Caty + JV to apply the patch > > > > The idea would be to have the following dates: > > - 2.6RC1: 1st of November 2010 (there's no M1) > > - 2.6 final: 18h of November > > I'd move the RC one week later. > > > If we agree, is there anyone who'd like to be the release manager for > > this release? If nobody volunteers I can do it. > > I could do it as well, if nobody else volunteers. > > > If we agree, I'll send another mail afterwards with some ideas for XE > > 2.7 and a potential XE 3.0 release. Note that XE 2.6 would be a first > > step in stabilizing XE for an upcoming 3.0 release :) But even > > without this vision doing a short stabilization release from time to > > time is always a good think I believe. It's also not too long so that > > people don't need to hold new stuff for too long. > > We could already create a 3.1 branch/trunk for new stuff when needed, > although this will increase the number of maintained branches a bit too > much. To help here, we can decide not to do maintainance releases for > the 2.6+ branches, since these are short releases. > Starting development on 3.x trunk simultaneously is a good way to keep visual improvements going. Discussion on what the 3.x should be is obviously required. Ttargeting an old core and legacy code free version for 4.0 is really what I am dreaming about. WDYT ? My +1 for stabilisations releases. Denis > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
