Re: [linuxtools-dev] Linux Tools Luna plan - initial proposal

[Wainer Moschetta <wainersm@xxxxxxxxxxxxxxxxxx>]

On 06/11/2013 11:01 AM, Aleksandar Kurtakov wrote:
> ----- Original Message -----
> > From: "Wainer Moschetta" <wainersm@xxxxxxxxxxxxxxxxxx>
> > To: linuxtools-dev@xxxxxxxxxxx
> > Sent: Tuesday, June 11, 2013 4:55:31 PM
> > Subject: Re: [linuxtools-dev] Linux Tools Luna plan - initial proposal
> >
> > On 06/11/2013 03:38 AM, Aleksandar Kurtakov wrote:
> > > ----- Original Message -----
> > > > From: "Wainer Moschetta" <wainersm@xxxxxxxxxxxxxxxxxx>
> > > > To: linuxtools-dev@xxxxxxxxxxx
> > > > Sent: Tuesday, June 11, 2013 12:31:22 AM
> > > > Subject: Re: [linuxtools-dev] Linux Tools Luna plan - initial proposal
> > > >
> > > > On 06/04/2013 02:57 AM, Aleksandar Kurtakov wrote:
> > > > > ----- Original Message -----
> > > > > > From: "Aleksandar Kurtakov" <akurtako@xxxxxxxxxx>
> > > > > > To: "Linux Tools developer discussions" <linuxtools-dev@xxxxxxxxxxx>
> > > > > > Sent: Monday, June 3, 2013 9:16:16 AM
> > > > > > Subject: [linuxtools-dev] Linux Tools Luna plan - initial proposal
> > > > > >
> > > > > > Hi everyone,
> > > > > > Let's try to plan our releases during Luna . Here is what I have in mind
> > > > > > -
> > > > > > feel free to say I'm nuts and propose a better one :):
> > > > > > * 2.0.1 release - our Kepler SR1 (August 28th?) - strictly bug fixing -
> > > > > > no
> > > > > > API breakage.
> > > > > > * 2.1 - new feature release (Late November) - new features and new API
> > > > > > allowed but no breakage of the 2.0 API.
> > > > > > * 2.1.1(if needed) - our Kepler SR2(January 22th?) - bug fixes on top of
> > > > > > 2.1,
> > > > > > no API breakage.
> > > > > >
> > > > > > Once 2.1 is released, master will be targeting Luna (aka our 3.0
> > > > > > release)
> > > > > > -
> > > > > > API breakage, new features, etc allowed.
> > > > > After talking to Jeff, he proposed making all the releases new features
> > > > > aka
> > > > > 2.1, 2.2 and 2.3 at pretty much same time as the initial proposal.
> > > > > Lttng devs, is this what you were asking for in the other thread?
> > > > Hi Alexander,
> > > >
> > > > You are proposing following schedule or did I misunderstand?
> > > >
> > > > 2.1 release - Kepler SR1 (09/27/2013) - bug fixes and *new features*
> > > > 2.2 release - Kepler SR2 (02/28/2014) - bug fixes and *new features*
> > > > 3.0 release - Luna - bug fixes, new features and *API breakage*
> > > >
> > > > * http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#Schedule
> > > Hi Wainer,
> > > Almost like this but our new releases have to be done for the RC1 SR
> > > releases so it's more of
> > > * 2.1 release - Kepler SR1 (08/23/2013) - bug fixes and *new features*
> > > * 2.2 release - Kepler SR2 (01/24/2014) - bug fixes and *new features*
> > > * 3.0 release - Luna - bug fixes, new features and *API breakage*
> > Great. Sounds good to me.
> >
> > Will the contribution policy for new features be 1 week for committers
> > and 3 weeks before code freeze for non-committers?
> Yes with the detail that some features might be rejected if they are invasive and a non-committer try to push them exactly 3 weeks before the release as we would not be able to accept his/her changes after submitting the iplog.

OK, got it.

Hey, thanks Alexander!

>   
>
> Alexander Kurtakov
> Red Hat Eclipse team
>
> > > Alex
> > >
> > >
> > > > - Wainer
> > > >
> > > > > Alexander Kurtakov
> > > > > Red Hat Eclipse team
> > > > >
> > > > > > Any thoughts?
> > > > > >
> > > > > > Alexander Kurtakov
> > > > > > Red Hat Eclipse team
> > > > > >
> > > > > > _______________________________________________
> > > > > > linuxtools-dev mailing list
> > > > > > linuxtools-dev@xxxxxxxxxxx
> > > > > > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > > > > _______________________________________________
> > > > > linuxtools-dev mailing list
> > > > > linuxtools-dev@xxxxxxxxxxx
> > > > > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > > > _______________________________________________
> > > > linuxtools-dev mailing list
> > > > linuxtools-dev@xxxxxxxxxxx
> > > > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > > _______________________________________________
> > > linuxtools-dev mailing list
> > > linuxtools-dev@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> > _______________________________________________
> > linuxtools-dev mailing list
> > linuxtools-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
> _______________________________________________
> linuxtools-dev mailing list
> linuxtools-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/linuxtools-dev