Re: [tracecompass-dev] Trace Compass 2.0/Neon RC1 posted

[Alexandre Montplaisir <alexmonthy@xxxxxxxxxxxx>]

On 2016-05-19 08:48 AM, Bernd Hufmann wrote:
> Hello
>
> I've created the stable-2.0 branch.
>
> Any fixes from now on have to be submitted on both master and 
> stable-2.0 branch (at least till the 2.0 release).
> The recommendation is to create the fix on master and when it's merged 
> cherry-pick it on stable-2.0.

Whose responsibility is it to push the fixes to the stable-2.0 branch? 
The original author of the patch? Or is there a "release manager" who 
takes care of the contents of the release branch? Should we name such a 
person?

Also, should all cherry-picked fixes go through Gerrit a second time?

I realize we should have discussed these points earlier, it just didn't 
occur to me until, well, now ;)

Thanks,
Alex


> Thanks to everybody working hard to get all the features and API 
> changes in for RC1.
>
> Next steps for the release are the manual feature and integration 
> tests as well as preparation of the
> release documentation.
>
> Best Regards
> Bernd
>
>
> On 05/18/2016 07:59 PM, Marc-André Laperle wrote:
> > Hi,
> >
> > I posted the Trace Compass 2.0/Neon RC1 build:
> >
> > http://download.eclipse.org/tracecompass/neon/milestones/rc1/
> >
> > It is based on commit: ed48dc75057206ed8992076bdfb1c3be1e74b2ff
> >
> > Neon RC2 build will be Wednesday, May 25th, 2016.
> >
> > Regards
> > Marc-André
> >
> >
> > _______________________________________________
> > tracecompass-dev mailing list
> > tracecompass-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or 
> > unsubscribe from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
>
>
>
>
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev