Re: [linuxtools-dev] API breaks and branching strategy

2012-06-29 Thread Alexandre Montplaisir
On 12-06-29 02:59 AM, akurtakov wrote: >> So no API break in 'master' before SR2 (including November LT v2.0)? Fine >> with me. > The proposal for November Linux Tools 2.0 was in order to make it > easier to get your API breaking things in. If we manage to not break > the API the release should be

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread akurtakov
On Fri, Jun 29, 2012 at 8:39 AM, Francois Chouinard wrote: > > On Thu, Jun 28, 2012 at 6:38 PM, akurtakov wrote: >> >> >> Projects should try hard to not break API - the easiest way is to >> export less but going the ISomething2 might be an option too. >> We want to provide our work to customers

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread Francois Chouinard
On Thu, Jun 28, 2012 at 6:38 PM, akurtakov wrote: > > Projects should try hard to not break API - the easiest way is to > export less but going the ISomething2 might be an option too. > We want to provide our work to customers faster, we want to ship in > maintenance releases that's why breaking

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread akurtakov
On Fri, Jun 29, 2012 at 1:11 AM, Francois Chouinard wrote: >> >> When a project goes out of incubation everything in it goes out of >> incubation there is no middle ground. Once a project is out of incubation it >> can setup its own incubator but it would be pretty weird to move lttng back >> to i

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread Andrew Overholt
> A question for Alex: Can we bump the LT major number in a Juno maintenance > releases? It would be largely frowned upon. Andrew ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread Francois Chouinard
> > > When a project goes out of incubation everything in it goes out of > incubation there is no middle ground. Once a project is out of incubation > it can setup its own incubator but it would be pretty weird to move lttng > back to incubation and even if we do that it would have to be kept api >

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread Aleksandar Kurtakov
- Original Message - > From: "Alexandre Montplaisir" > To: "Linux Tools developer discussions" , > "akurtakov" > Sent: Thursday, June 28, 2012 11:24:04 PM > Subject: Re: [linuxtools-dev] API breaks and branching strategy > > On 12-

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread Otávio Pontes
On 06/28/2012 04:54 PM, akurtakov wrote: On Thu, Jun 28, 2012 at 10:47 PM, Alexandre Montplaisir wrote: Hello Linux Toolers, We of the LTTng group already have some changes in the pipeline that will break our 1.0 API. If I understood correctly, the 1.1, 1.2, etc. releases (if applicable) will

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread Alexandre Montplaisir
On 12-06-28 03:54 PM, akurtakov wrote: > On Thu, Jun 28, 2012 at 10:47 PM, Alexandre Montplaisir > wrote: >> Hello Linux Toolers, >> >> We of the LTTng group already have some changes in the pipeline that >> will break our 1.0 API. If I understood correctly, the 1.1, 1.2, etc. >> releases (if appl

Re: [linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread akurtakov
On Thu, Jun 28, 2012 at 10:47 PM, Alexandre Montplaisir wrote: > Hello Linux Toolers, > > We of the LTTng group already have some changes in the pipeline that > will break our 1.0 API. If I understood correctly, the 1.1, 1.2, etc. > releases (if applicable) will be based off the current stable-1.0

[linuxtools-dev] API breaks and branching strategy

2012-06-28 Thread Alexandre Montplaisir
Hello Linux Toolers, We of the LTTng group already have some changes in the pipeline that will break our 1.0 API. If I understood correctly, the 1.1, 1.2, etc. releases (if applicable) will be based off the current stable-1.0 branch, not the master. Does this mean we can switch our plugins to 2.0.