Right, but the fixVersion for the released version that we thought it was fixed in, should be removed in that case, and a comment should be made on the ticket, to describe the discrepancy with the CHANGES file in the release tarball.
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Fri, Sep 13, 2013 at 7:49 PM, Mike Drob <[email protected]> wrote: > While in general I agree with Sean that once resolved in a released > version, JIRAs should stay resolved, I have no problem with re-opening > issues that are marked resolved in a non-released version, since, well, > they were never resolved. > > > On Fri, Sep 13, 2013 at 6:20 PM, Sean Busbey <[email protected]> wrote: > >> If the issues are marked resolved in a released version, please please >> please make a new issue and include a relationship to the older one. >> >> We can't go back and change the releases, and it's much harder to track >> things later on when we have patches for the same issue that span months >> and/or releases. >> >> -- >> Sean >> On Sep 13, 2013 2:36 PM, "John Vines" <[email protected]> wrote: >> >> > I say reopen >> > >> > >> > On Fri, Sep 13, 2013 at 5:29 PM, Michael Berman <[email protected]> >> wrote: >> > >> > > Looks like the RestartIT issue could have been introduced with the >> > > introduction of a configurable GC in the MAC in Josh's a028e7 last >> week, >> > > and from the commit log it looks like the 1.5.1 and 1.4.5 branches >> might >> > > have the same issue. >> > > >> > > Seems like the ReadWriteIT error was introduced in Billie's 6e7269 two >> > days >> > > ago. >> > > >> > > Process question: the relevant issues are all marked resolved. If I >> want >> > > to submit patches, should I reopen the bugs? Or file new bugs >> > specifically >> > > about the ITs? >> > > >> > >>
