Jira version tag for master branch

[Ryan Ernst <ry...@iernst.net>]

FYI, I just renamed the "Trunk" version to "master", to match what we have
now with git. Since it was just a rename, it appears all the existing
issues that used Trunk as a fix version are already updated.

Re: Jira version tag for master branch

[Michael McCandless <lu...@mikemccandless.com>]

>From what I understand, "trunk" should go away and be renamed to
"master".  Can a Solr dev do this for existing Solr issues?

When I cut the 6.0 branch (after 5.5 release seems close to done),
I'll rename all "master" issues to 6.0 and new (master) issues are
then 7.0.

Mike McCandless

http://blog.mikemccandless.com

On Tue, Feb 9, 2016 at 9:49 AM, Jan Høydahl <ja...@cominvent.com> wrote:
> Could you do the same to Solr’s JIRA?
>
> We now both have both a “master” and “6.0” version. Which of them should we
> tag “trunk” issues with?
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> 3. feb. 2016 kl. 21.26 skrev Ryan Ernst <ry...@iernst.net>:
>
> FYI, I just renamed the "Trunk" version to "master", to match what we have
> now with git. Since it was just a rename, it appears all the existing issues
> that used Trunk as a fix version are already updated.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

Re: Jira version tag for master branch

[Jan Høydahl <ja...@cominvent.com>]

Could you do the same to Solr’s JIRA?

We now both have both a “master” and “6.0” version. Which of them should we tag “trunk” issues with?

--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com

> 3. feb. 2016 kl. 21.26 skrev Ryan Ernst <ry...@iernst.net>:
> 
> FYI, I just renamed the "Trunk" version to "master", to match what we have now with git. Since it was just a rename, it appears all the existing issues that used Trunk as a fix version are already updated.