Re: [Pacemaker] Release model

2013-06-28 Thread Andrew Beekhof
On 29/06/2013, at 12:15 AM, Digimer wrote: > On 06/28/2013 08:04 AM, Andrew Beekhof wrote: >> Under this model, not only do I have to find the time to write and test the >> new addition, but I also have to: >> * keep maintaining the old code until... when? >> * probably write and maintain a com

Re: [Pacemaker] Release model

2013-06-28 Thread Andrew Beekhof
On 28/06/2013, at 11:37 PM, Lars Marowsky-Bree wrote: >>> >>> I'm not sure there's a huge downside in it for you? >> Ok, lets take attrd for example - which I've been wanted to rewrite to be >> truly atomic for half a decade or more. > > If it's rewritten in a way that doesn't affect external

Re: [Pacemaker] Release model

2013-06-28 Thread Dejan Muhamedagic
On Fri, Jun 28, 2013 at 03:32:05PM +0200, Lars Marowsky-Bree wrote: > On 2013-06-28T14:49:06, Dejan Muhamedagic wrote: > > > > If cluster-glue's LRM had had such a suite, it'd certainly have > > > helped tons.) > > It did have a regression suite. > > Yes, well, but it didn't test for LRM_MAX_CHI

Re: [Pacemaker] Release model

2013-06-28 Thread Digimer
On 06/28/2013 08:04 AM, Andrew Beekhof wrote: > Under this model, not only do I have to find the time to write and test the > new addition, but I also have to: > * keep maintaining the old code until... when? > * probably write and maintain a compatibility layer > * make it possible to choose whic

Re: [Pacemaker] Release model

2013-06-28 Thread Lars Marowsky-Bree
On 2013-06-28T22:04:48, Andrew Beekhof wrote: > I think he did actually. Well, yes, but the hg history or reading the existing code would probably have been quite helpful. I'll take "not well documented", but it's hard to say the rewrite was handled very well. But I don't want to get drawn into

Re: [Pacemaker] Release model

2013-06-28 Thread Lars Marowsky-Bree
On 2013-06-28T14:49:06, Dejan Muhamedagic wrote: > > If cluster-glue's LRM had had such a suite, it'd certainly have > > helped tons.) > It did have a regression suite. Yes, well, but it didn't test for LRM_MAX_CHILDREN or the secret support, for example. So it didn't really document the interfa

Re: [Pacemaker] Release model

2013-06-28 Thread Dejan Muhamedagic
Hi Lars, On Fri, Jun 28, 2013 at 12:59:22PM +0200, Lars Marowsky-Bree wrote: [...] > If > cluster-glue's LRM had had such a suite, it'd certainly have helped > tons.) It did have a regression suite. Thanks, Dejan ___ Pacemaker mailing list: Pacemaker

Re: [Pacemaker] Release model

2013-06-28 Thread Andrew Beekhof
On 28/06/2013, at 8:59 PM, Lars Marowsky-Bree wrote: > On 2013-06-28T18:41:35, Andrew Beekhof wrote: > >>> There's an exception: dropping commonly used external interfaces (say, >>> "ptest") needs to be announced a few releases in advance before enacted >>> upstream. (And if Enterprise distrib

Re: [Pacemaker] Release model

2013-06-28 Thread Lars Marowsky-Bree
On 2013-06-28T18:41:35, Andrew Beekhof wrote: > > There's an exception: dropping commonly used external interfaces (say, > > "ptest") needs to be announced a few releases in advance before enacted > > upstream. (And if Enterprise distributions want to keep something, they > > have time to prepare