Jonathan Hsieh
2012-08-31, 17:53
Gregory Chanan
2012-08-31, 18:30
Andrew Purtell
2012-09-01, 07:47
Jonathan Hsieh
2012-09-01, 11:16
lars hofhansl
2012-10-12, 04:08
Stack
2012-10-12, 05:28
lars hofhansl
2012-10-12, 05:36
Stack
2012-10-12, 06:21
lars hofhansl
2012-10-12, 16:14
-
Closing issues (as opposed to Resolving).Jonathan Hsieh 2012-08-31, 17:53
Hey all,
I propose that we close issues after a release is done.
Close is stronger than resolve -- I believe it makes the issue essentially
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]
I propose that we close issues after a release is done.
Close is stronger than resolve -- I believe it makes the issue essentially
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]
-
Re: Closing issues (as opposed to Resolving).Gregory Chanan 2012-08-31, 18:30
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?
Greg
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 essentially
> 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]
>
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?
Greg
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 essentially
> 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]
>
-
Re: Closing issues (as opposed to Resolving).Andrew Purtell 2012-09-01, 07:47
We had a discussion with Todd IIRC a whole back where we agreed that we'd
only commit multiple times under the same JIRA within a short period. I
think the consensus was a few hours. Otherwise we'd open a new JIRA to
record the change, with a pointer to the other issue of course. In this
context, closing after a release does no harm. If the consensus is to not
reopen after close, then we can adopt that too.
On Friday, August 31, 2012, Gregory Chanan 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?
>
> Greg
>
> On Fri, Aug 31, 2012 at 10:53 AM, Jonathan Hsieh <[EMAIL PROTECTED]<javascript:;>>
> 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
> essentially
> > 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] <javascript:;>
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
only commit multiple times under the same JIRA within a short period. I
think the consensus was a few hours. Otherwise we'd open a new JIRA to
record the change, with a pointer to the other issue of course. In this
context, closing after a release does no harm. If the consensus is to not
reopen after close, then we can adopt that too.
On Friday, August 31, 2012, Gregory Chanan 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?
>
> Greg
>
> On Fri, Aug 31, 2012 at 10:53 AM, Jonathan Hsieh <[EMAIL PROTECTED]<javascript:;>>
> 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
> essentially
> > 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] <javascript:;>
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
-
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.
Jon.
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?
>
> Greg
>
> 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
> essentially
> > 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]
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.
Jon.
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?
>
> Greg
>
> 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
> essentially
> > 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]
-
Re: Closing issues (as opposed to Resolving).lars hofhansl 2012-10-12, 04:08
Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
-- Lars
________________________________
From: Jonathan Hsieh <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Friday, August 31, 2012 10:53 AM
Subject: Closing issues (as opposed to Resolving).
Hey all,
I propose that we close issues after a release is done.
Close is stronger than resolve -- I believe it makes the issue essentially
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]
-- Lars
________________________________
From: Jonathan Hsieh <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Friday, August 31, 2012 10:53 AM
Subject: Closing issues (as opposed to Resolving).
Hey all,
I propose that we close issues after a release is done.
Close is stronger than resolve -- I believe it makes the issue essentially
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]
-
Re: Closing issues (as opposed to Resolving).Stack 2012-10-12, 05:28
On Thu, Oct 11, 2012 at 9:08 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>
I think we should (I meant to start doing it for old releases).
St.Ack
> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>
I think we should (I meant to start doing it for old releases).
St.Ack
-
Re: Closing issues (as opposed to Resolving).lars hofhansl 2012-10-12, 05:36
Done for 0.94.0 and 0.94.1.
________________________________
From: Stack <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
Sent: Thursday, October 11, 2012 10:28 PM
Subject: Re: Closing issues (as opposed to Resolving).
On Thu, Oct 11, 2012 at 9:08 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>
I think we should (I meant to start doing it for old releases).
St.Ack
________________________________
From: Stack <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
Sent: Thursday, October 11, 2012 10:28 PM
Subject: Re: Closing issues (as opposed to Resolving).
On Thu, Oct 11, 2012 at 9:08 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>
I think we should (I meant to start doing it for old releases).
St.Ack
-
Re: Closing issues (as opposed to Resolving).Stack 2012-10-12, 06:21
Closed from 0.1.0 all the ways up through 0.92 (w/ the 'do not send
mail' unclicked -- smile).
St.Ack
On Thu, Oct 11, 2012 at 10:36 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Done for 0.94.0 and 0.94.1.
>
>
>
> ________________________________
> From: Stack <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
> Sent: Thursday, October 11, 2012 10:28 PM
> Subject: Re: Closing issues (as opposed to Resolving).
>
> On Thu, Oct 11, 2012 at 9:08 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
>> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>>
>
> I think we should (I meant to start doing it for old releases).
> St.Ack
mail' unclicked -- smile).
St.Ack
On Thu, Oct 11, 2012 at 10:36 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Done for 0.94.0 and 0.94.1.
>
>
>
> ________________________________
> From: Stack <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
> Sent: Thursday, October 11, 2012 10:28 PM
> Subject: Re: Closing issues (as opposed to Resolving).
>
> On Thu, Oct 11, 2012 at 9:08 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
>> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>>
>
> I think we should (I meant to start doing it for old releases).
> St.Ack
-
Re: Closing issues (as opposed to Resolving).lars hofhansl 2012-10-12, 16:14
Yeah, I had the 'do not send mail' when I did 0.94.0 but then forgot for 0.94.1 :(
________________________________
From: Stack <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
Sent: Thursday, October 11, 2012 11:21 PM
Subject: Re: Closing issues (as opposed to Resolving).
Closed from 0.1.0 all the ways up through 0.92 (w/ the 'do not send
mail' unclicked -- smile).
St.Ack
On Thu, Oct 11, 2012 at 10:36 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Done for 0.94.0 and 0.94.1.
>
>
>
> ________________________________
> From: Stack <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
> Sent: Thursday, October 11, 2012 10:28 PM
> Subject: Re: Closing issues (as opposed to Resolving).
>
> On Thu, Oct 11, 2012 at 9:08 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
>> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>>
>
> I think we should (I meant to start doing it for old releases).
> St.Ack
________________________________
From: Stack <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
Sent: Thursday, October 11, 2012 11:21 PM
Subject: Re: Closing issues (as opposed to Resolving).
Closed from 0.1.0 all the ways up through 0.92 (w/ the 'do not send
mail' unclicked -- smile).
St.Ack
On Thu, Oct 11, 2012 at 10:36 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
> Done for 0.94.0 and 0.94.1.
>
>
>
> ________________________________
> From: Stack <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]; lars hofhansl <[EMAIL PROTECTED]>
> Sent: Thursday, October 11, 2012 10:28 PM
> Subject: Re: Closing issues (as opposed to Resolving).
>
> On Thu, Oct 11, 2012 at 9:08 PM, lars hofhansl <[EMAIL PROTECTED]> wrote:
>> Should we start putting this into practice? I'm happy to do this for 0.94.0 and 0.94.1 (provided that mass change functionality in jira actually works).
>>
>
> I think we should (I meant to start doing it for old releases).
> St.Ack
