Re: [cmake-developers] Pushing to next and closing bugs?

2010-07-27 Thread Alexander Neundorf
On Tuesday 06 July 2010, Eric Noulard wrote: > 2010/7/5 Bill Hoffman :> > > > So, although not perfect, I prefer to close the bug when it is checked in > > to next.   My reason is that we have wa too many bugs open as it is. > >  I don't want to have to wait on the reporter to close it, as ofte

Re: [cmake-developers] Pushing to next and closing bugs?

2010-07-27 Thread Alexander Neundorf
On Monday 05 July 2010, Bill Hoffman wrote: > On 7/5/2010 2:06 PM, Eric Noulard wrote: ... > > Yes it does. > > I'll re-open the prematurely closed bug and propose the following > > "process": > > > > 1) A bug is reported (by a "Reporter") > > > > 2) The bug is assigned (to the "Assignee") which ei

Re: [cmake-developers] Pushing to next and closing bugs?

2010-07-05 Thread Eric Noulard
2010/7/5 Bill Hoffman :> > So, although not perfect, I prefer to close the bug when it is checked in to > next.   My reason is that we have wa too many bugs open as it is.  I > don't want to have to wait on the reporter to close it, as often times they > have lost interest and gone away never t

Re: [cmake-developers] Pushing to next and closing bugs?

2010-07-05 Thread Bill Hoffman
On 7/5/2010 2:06 PM, Eric Noulard wrote: 2010/7/5 David Cole: We don't really have a well-defined procedure that everybody follows w.r.t. resolving/closing bugs in the bug database. I typically just add a note when I push a change to 'next', saying that it is in next, and then go back to resolve

Re: [cmake-developers] Pushing to next and closing bugs?

2010-07-05 Thread Eric Noulard
2010/7/5 David Cole : > We don't really have a well-defined procedure that everybody follows w.r.t. > resolving/closing bugs in the bug database. > I typically just add a note when I push a change to 'next', saying that it > is in next, and then go back to resolve the bug when it is merged to maste

Re: [cmake-developers] Pushing to next and closing bugs?

2010-07-05 Thread David Cole
We don't really have a well-defined procedure that everybody follows w.r.t. resolving/closing bugs in the bug database. I typically just add a note when I push a change to 'next', saying that it is in next, and then go back to resolve the bug when it is merged to master. For example, see this one

[cmake-developers] Pushing to next and closing bugs?

2010-07-04 Thread Eric Noulard
Hi there, I did push some bug fixes to next today since the changes correspond to bug fixes I did close the corresponding as I was doing that before when using CVS. Now I wonder, when shall I close a bug? 1) when the fix is pushed to next? or 2) when I'm sure the fix reached master? I did