You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jclouds.apache.org by Ignasi Barrera <na...@apache.org> on 2014/07/16 22:00:47 UTC
JIRA versions cleanup
Now that there seems to be an agreement that next release will be
1.8.0, what about removing from JIRA the earlier unreleased versions?
We still have there 1.5.11, 1.6.4 and 1.7.4, and IMO that only causes
the expectation that those releases are planned. I think we should
remove them to avoid confusion and move all issues that were marked to
be fixed in those versions to 1.8.0 or 2.0.0.
Thoughts?
Re: JIRA versions cleanup
Posted by Andrea Turli <an...@gmail.com>.
+1
Andrea
Il 16/lug/2014 22:01 "Ignasi Barrera" <na...@apache.org> ha scritto:
> Now that there seems to be an agreement that next release will be
> 1.8.0, what about removing from JIRA the earlier unreleased versions?
>
> We still have there 1.5.11, 1.6.4 and 1.7.4, and IMO that only causes
> the expectation that those releases are planned. I think we should
> remove them to avoid confusion and move all issues that were marked to
> be fixed in those versions to 1.8.0 or 2.0.0.
>
> Thoughts?
>
Re: JIRA versions cleanup
Posted by Everett Toews <ev...@RACKSPACE.COM>.
+1
Everett
On Jul 16, 2014, at 3:00 PM, Ignasi Barrera <na...@apache.org> wrote:
> Now that there seems to be an agreement that next release will be
> 1.8.0, what about removing from JIRA the earlier unreleased versions?
>
> We still have there 1.5.11, 1.6.4 and 1.7.4, and IMO that only causes
> the expectation that those releases are planned. I think we should
> remove them to avoid confusion and move all issues that were marked to
> be fixed in those versions to 1.8.0 or 2.0.0.
>
> Thoughts?
Re: JIRA versions cleanup
Posted by Andrew Phillips <ap...@qrmedia.com>.
> We still have there 1.5.11, 1.6.4 and 1.7.4, and IMO that only causes
> the expectation that those releases are planned. I think we should
> remove them to avoid confusion and move all issues that were marked to
> be fixed in those versions to 1.8.0 or 2.0.0.
>
> Thoughts?
Sounds like a good idea. An email to user@ once the cleanup has been
carried out would also be useful, I think.
I guess that would mean that any issues that were explicitly opened as
a backport of a fix on master for 1.7.x (or an older branch) will not
be addressed/should be closed as "Won't Fix"?
ap