You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@htrace.apache.org by Nick Dimiduk <nd...@apache.org> on 2015/06/30 00:20:28 UTC
Cleaning up JIRA
Hi folks,
I looked up our release announcements from 3.1 and 3.2, marked those
versions as released over in JIRA. We have a 2.3 version, which I guess was
sort-of pre-incubator. I think those tickets should be moved over into 3.1
and the version number dropped. We also have a "master" version, which is a
bit useless. However, there's 12 tickets set there, most of which are also
tagged 3.1. I don't know if master also meant 3.2 for these tickets. Would
the RM's mind looking through the logs and cleaning things up?
For future releases, what version are those tickets tagged? Seems like most
stuff is getting FixVersion 3.3.
Thanks,
Nick
Re: Cleaning up JIRA
Posted by "Colin P. McCabe" <cm...@apache.org>.
Thanks, Nick. It probably makes sense to tag changes for future
releases as 3.3 at the moment. We can always move them out if needed
when we cut the 3.3 release.
cheers,
Colin
On Mon, Jun 29, 2015 at 3:20 PM, Nick Dimiduk <nd...@apache.org> wrote:
> Hi folks,
>
> I looked up our release announcements from 3.1 and 3.2, marked those
> versions as released over in JIRA. We have a 2.3 version, which I guess was
> sort-of pre-incubator. I think those tickets should be moved over into 3.1
> and the version number dropped. We also have a "master" version, which is a
> bit useless. However, there's 12 tickets set there, most of which are also
> tagged 3.1. I don't know if master also meant 3.2 for these tickets. Would
> the RM's mind looking through the logs and cleaning things up?
>
> For future releases, what version are those tickets tagged? Seems like most
> stuff is getting FixVersion 3.3.
>
> Thanks,
> Nick