accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher <>
Subject Re: [DISCUSS] Setting 1.4 versions to "archive" in Jira
Date Sun, 11 May 2014 18:02:53 GMT
Unfortunately, I think this list strips attachments, so the IRC
transcript didn't get attached.

Personally, I think it's probably okay to archive 1.4.0-1.4.3 now, and
leave 1.4.4 and 1.4.5 available for filing bugs against. If somebody
is using 1.4.0-1.4.3, we should be encouraging them to update and
verify their bug is still an issue. In the meantime, they can get
support from the user@ list and the IRC channel for
workarounds/assistance with verifying the issue. Comments,
environment, and descriptions in issues still allow additional
versions to be mentioned, but not making EOL'd versions available in
the menu is an additional reminder to users that they're using an
unsupported version and that they should investigate whether their
issues are fixed in newer versions.

I think archiving helps keep things in JIRA relevant for development
priorities and tracking, by omitting archived versions from generated
JIRA reports, and reduces the burden on those who triage issues (an
activity in which I participate, though admittedly, I could quite
easily ignore 1.4 issues, deferring them to another volunteer to

We can archive the remaining 1.4.x versions after a time, when people
bug reports against them slow and we can be reasonably assured the
largest portions of our user base have migrated to newer, supported

On the other hand, I think it'd be fine to wait and archive all the
1.4.x versions at the same time. Mainly, what I'd be concerned about
is leaving these versions around indefinitely, and allowing bug
reports against them to pollute the JIRA, reducing its utility, long
after we've stopped supporting it.

In short, I'm fine with playing by ear, as long as they get archived
eventually (maybe when we EOL 1.5.x?)

Christopher L Tubbs II

On Thu, May 8, 2014 at 11:55 PM, Sean Busbey <> wrote:
> Hey Folks!
> Jira uses the notation of "archived" to mean that a version is no longer in
> active use. The status means that a given version no longer autocompletes
> and can not be used when editing tickets.
> Earlier there was a brief discussion on IRC about the matter (attached as a
> log), and I wanted to make sure everyone had a chance to participate in the
> discussion.
> Relevant questions, as I see it
> 1) Do we wish to leave more 1.4.x versions active on jira to make things
> easier for contributors filing tickets against the older releases? Or do we
> wish to leave fewer active to make it easier for contributors who are
> handling triage of new issues?
> 2) Do we want to set an approximate time for when all 1.4.x versions will be
> archived in jira, e.g. end of 2014? Since the user announcement for the end
> of 1.4 is still in draft form, we could include this information so that
> users can plan now.
> Personally, I'd like to 1) leave all the 1.4.x releases active for now and
> 2) not set a hard cut off and instead play it by ear depending on issues we
> see filed.
> --
> Sean

View raw message