-Re: Closing issues (as opposed to Resolving).
Jonathan Hsieh 2012-09-01, 11:16
Links to closed jiras still work -- it is just that edits to history and
discussion gets frozen after the release. (edits seem to at least for
committers). Talking to a committer from another project, it is actually
part of their release process (once release bits have been posted, close
all issues resolved by the release). The point is that once closed
(released), an issue cannot be reopened -- a new issue must be filed.
Ideally, all backports go through on the original jira. If not within the
"short period", and we figure out we want/need it later, just file a new
issue to backport it to a sustaining release. This seems reasonable --
those issues would get closed once that minor release gets out.
On Fri, Aug 31, 2012 at 11:30 AM, Gregory Chanan <[EMAIL PROTECTED]>wrote:
> If we later figure out that an issue caused a bug (even after a release),
> will we be able to mention that in the original JIRA? I find it useful to
> be able to track that, particularly for forward/backport purposes.
> Also, can we reopen issues after they have been closed? If so, what's the
> point of closing?
> On Fri, Aug 31, 2012 at 10:53 AM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:
> > Hey all,
> > I propose that we close issues after a release is done.
> > Close is stronger than resolve -- I believe it makes the issue
> > read only. There are many resolved issues from 0.20, 0.89, and 0.90.6 <
> > that could be closed, (as well as issues from 0.92.1, and 0.94.1..
> > This would force discussion on old topics to new jiras and make things a
> > little tidier.
> > Thoughts?
> > Jon.
> > --
> > // Jonathan Hsieh (shay)
> > // Software Engineer, Cloudera
> > // [EMAIL PROTECTED]
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// [EMAIL PROTECTED]