Re: Release cycle proposal

2010-11-03 Thread Stephan Witt
Am 03.11.2010 um 12:13 schrieb Abdelrazak Younes: > People should have two checkout: branch and trunk, period. I have three: * branch, * trunk for work and another * trunk for trying out my patches before posting to list. Stephan

Re: Release cycle proposal

2010-11-03 Thread Abdelrazak Younes
On 11/03/2010 03:17 PM, Pavel Sanda wrote: True but this is a drawback that comes from our linear development model. As soon as we switch to "one feature = one branch" then citing branch or a tag (don't forget that git tags are real tags) will be just fine. No more needs to cite a commit.

Re: Release cycle proposal

2010-11-03 Thread Pavel Sanda
Abdelrazak Younes wrote: >> there is also compromise possible - we freeze until the horrible number of >> bugs >> shrinks somewhat. >> > > Do you have numbers? I am not sure trunk is so full of bugs when compared > to pre-1.6 or pre-1.5... I am quite sure though that the first 1.5 or 1.6 i

Re: Release cycle proposal

2010-11-03 Thread Abdelrazak Younes
On 11/03/2010 01:27 PM, Pavel Sanda wrote: Abdelrazak Younes wrote: It's the job of the maintainer to recall the relevent developer his duty with regards to the branch bug fixing. And Juergen is very goo at it. Artificially imposing a not convincing. in many bugs its hard to decide wh

Re: Release cycle proposal

2010-11-03 Thread Pavel Sanda
Abdelrazak Younes wrote: > It's the job of the > maintainer to recall the relevent developer his duty with regards to the > branch bug fixing. And Juergen is very goo at it. Artificially imposing a not convincing. in many bugs its hard to decide whose is in charge and they just stay. > limit o