On 13-06-04 01:57 AM, Aleksandar Kurtakov wrote: > ----- Original Message ----- >> From: "Aleksandar Kurtakov" <akurt...@redhat.com> >> To: "Linux Tools developer discussions" <linuxtools-dev@eclipse.org> >> 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, Yes, it would accommodate us more if the SR1, 2 and 3 are 2.1, 2.2 and 2.3 respectively. This way we wouldn't need to either handle 2+ branches at the same time, or delay changes until 3.0. Thanks, Alexandre > > Alexander Kurtakov > Red Hat Eclipse team > >> Any thoughts? >> >> Alexander Kurtakov >> Red Hat Eclipse team >> >> _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
