lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Fix versions
Date Wed, 05 Jul 2017 21:13:04 GMT
I'm just including a fix version for each push I make. I.e.

If I push to master I'll add "master (8.0)".
If I push to 7x, at this point I'll add 7.1
If I push to 7_0 I'll add 7.0
If I push to 6x I'll add 6.7
If for some reason I wanted to push it to branch_6_6 I'd add 6.6.1

I think one push == one label is unambiguous. You do have to realize
that if there may never be, say, a 6.6.1 in my example. But we do
remove the onus of people having to figure out what a fix version of
plain "master" or "7x" means.


On Wed, Jul 5, 2017 at 1:48 PM, Dawid Weiss <> wrote:
> There's been a fairly recent discussion about it on the mailing list
> (David Smiley and were involved in that discussion, among other
> people). There are many different takes on how to handle fix-for and
> branches. I don't think we can find the "best" strategy, although
> perhaps we can agree on something project-specific. I've expressed my
> opinion on that previous post, but I'm open to any strategy.
> Dawid
> On Wed, Jul 5, 2017 at 10:42 PM, Anshum Gupta <> wrote:
>> Hi,
>> I was a bit confused in terms of setting the ‘fix version’ for JIRAs that
>> are being committed right now. I think it makes sense for the fixVersion to
>> just be 7.0, and nothing else for everything that is going into branch_7_0,
>> instead of being both 7.0, and master (8.0).
>> Any thoughts?
>> -Anshum
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message