Denis
you can consider me as a resource, would like to contribute in
4.3.1 as well as other tasks.
-arvind
On Thu, Dec 13, 2012 at 11:04 PM, Vincent Massol <vinc...@massol.net> wrote:
> Hi Denis,
>
> On Dec 13, 2012, at 6:06 PM, Denis Gervalle <d...@softec.lu> wrote:
>
> > On Thu, Dec 13, 2012 at 5:42 PM, Vincent Massol <vinc...@massol.net>
> wrote:
> >
> >> Hi devs,
> >>
> >> We have too many test failures on
> >> http://ci.xwiki.org/view/Functional%20Tests/ and too many emails sent
> by
> >> Jenkins on the list.
> >>
> >> It has become a nightmare and it's impossible to perform a release
> anymore
> >> with a good confidence it's going to work.
> >>
> >> This is all the more bad that we're ending the 4.x cycle.
> >>
> >> Thus I propose to do the following:
> >> * Don't release 4.4M1 till all tests are passing with no more flickers
> >> (say the tests should all pass during 10 full builds for example)
> >> * Create a Commando unit in charge of solving the flickers. Since I've
> >> already discussed this with Marius I propose that Marius and myself be
> the
> >> first 2 members. If anyone else would like to help please reply to this
> >> mail and join us.
> >> * This commando unit gives itself 1 full week to solve the flickers (ie
> >> till the 21st of December). We'll decide what to do next if we fail to
> >> achieve our goal after that deadline.
> >> * We start by creating a branch for 4.4M1 so that we isolate ourselves
> >> from the rest of the devs who continue to work for 4.4RC1 (reminder:
> only
> >> important bug fixes should go in 4.4RC1)
> >> * When we have fixed all flickers on the 4.4M1 branch we merge the
> changes
> >> to both master and the stable-4.3 branch
> >> * At the end of next week we also propose a strategy so that this mess
> >> doesn't happen again in the future
> >>
> >> WDYT?
> >>
> >> Thanks
> >> -Vincent
> >>
> >> Note: We need to release 4.3.1 ASAP so this strategy above will not
> apply
> >> to 4.3.1. For 4.3.1 Edy will need to figure out if all the failing tests
> >> are real issues or test issues. I think Edy could do this by a
> combination
> >> of running them locally and doing some manual tests where they also fail
> >> locally. Edy WDYT?
> >>
> >
> > There are still a blocker issue for 4.3.1, shouldn't we also have that
> > solve first ? There is also a lot of other issue marked to be fix, I
> > suppose Edy will triage, and if some are important, these should be fixed
> > first. I am just afraid, because most of these issue are assigned to
> > Marius, and IMO it is more important to focus on the 4.3.1 release than
> on
> > the 4.4M1 one.
>
> At this stage it's more important to release 4.3.1 ASAP and we can do a
> 4.3.2 after for less important bugs if we want but I don't think it'll be
> needed because we'll be released 4.4 which is a stabilization/bug fix
> release and same for 4.5 so we'll recommend users to upgrade to 4.4 and
> then 4.5 and not 4.3.1 or 4.3.2...
>
> If you know of some issues that you consider blocking for 4.3.1 please
> raise them in a different thread and we can decide if they warrant
> postponing 4.3.1 more.
>
> Thanks
> -Vincent
>
> PS: I suggest you be the next release manager so that you can really
> decide if it's more important to fix the build or fix bugs… ;) There are
> some committers that don't help much in fixing the build so it's quite easy
> if you've not been doing this to consider that the build isn't important..
> The most important is to have a stable build. That comes first. Even before
> bugs because it's a prerequisite for fixing bugs.
>
> _______________________________________________
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
_______________________________________________
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
