wrote:

+1 Alex On 10/20/2010 09:31 AM, Vincent Massol wrote: 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: 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): Stream): Raluca + Caty + JV to apply the patch this release? If nobody volunteers I can do it. 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. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On 10/20/2010 09:31 AM, Vincent Massol wrote: 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'd move the RC one week later. I could do it as well, if nobody else volunteers. 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. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On 10/20/2010 09:31 AM, Vincent Massol wrote: 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'd move the RC one week later.

I could do it as well, if nobody else volunteers. 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.

On 10/25/2010 12:32 PM, Vincent Massol wrote: WDYM 3 weeks?

When did you start counting? 1st is next week, so just one week between 2.5 and 2.6RC1. Also, trunk became 2.6 on the 14th, so that would be only two weeks since the 2.6 version was introduced, I really don't understand where the 3 weeks before the RC came. Note that I only proposed moving the RC date, not the final date.

> In addition this gives less chance for people to test the stabilization release(s) (people only test when there are final releases). > > I'd really like to keep the proposed dates. Please let me know if it's ok with you since you're the only one who voiced a concern on the date.

On 10/25/2010 02:26 PM, Vincent Massol wrote: I'm +0 on either date, my statement was just a "if possible", since 18 days between a RC and the final release is a more than what we usually do.

-- Sergiu Dumitriu http://purl.org/net/sergiu/

On 10/20/2010 09:31 AM, Vincent Massol wrote: 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'd move the RC one week later. I could do it as well, if nobody else volunteers. 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. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On Oct 26, 2010, at 5:39 PM, Jerome Velociter wrote: Could you be more specific re annotations?

For 2.6? Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

On Oct 28, 2010, at 5:29 PM, Jerome Velociter wrote: > On Tue, Oct 26, 2010 at 6:44 PM, Vincent Massol <vincent(a)massol.net> wrote: >> >> On Oct 26, 2010, at 5:39 PM, Jerome Velociter wrote: >> >>> On Thu, Oct 21, 2010 at 1:08 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> 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 would like to add "annotations" to this list (especially making them >>> work w/o JS and and activated by default) >> >> Could you be more specific re annotations? > > Yes. I meant at least two things : > > * Activate annotations as a default setting > * Have annotations displayed even when JavaScript is not available > (that means moving code from the annotation application to the > platform - but that's another story) > > And a third item, a bit more ambitious (so maybe for 2.7 ?) : > > * Fusion annotations with comments (at least in the U. Probably in the > storage (read: XClass) by default too - to make the UI easier to > write). Comments would then become annotations without a context. > > That would already be great.

Are you proposing to implement these features yourself?

If not, we need someone to volunteer. Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs