Thanks for your explanation Jacopo, inline...
Le 21/03/2016 15:10, Jacopo Cappellato a écrit :
Jacques, thanks for raising this point that I think is worth of some
clarifications and enhancements to get the best out of the Jira reports.
When we backport a patch to the 15.12 branch, the patch will be published
in the first release of that branch: and this is why we need the 15.12.01
version and we should set the "fix version" to 15.12.01 rather than 15.12
Yes, I thought about it afterwards and I could see the reason.
So far I tried to remove all not released versions (like 15.12) out of the "fixed
versions" field.
I used "Upcoming branch" for the not yet released branches.
And of course pending next release versions (like 13.07.02) when appropriate
(ie when backporting in a supported and already released branch)
But if we have 2 unreleased branches (like at the moment 14 and 15) we indeed
need to differentiate them.
"Upcoming branch" should be used to mark all the issues that are
implemented in the trunk and not backported in the release branches;
OK, I thought we were also using that for backports in not yet released
branches.
when, at a later time, we create a new release branch from the trunk, this
release branch will of course contain all these enhancements/fixes; at that
point we should rename the "Upcoming branch" version into the name of the
first (future) release of the new branch and we should create a brand new
empty version with the name "Upcoming branch"
You mean rename in the admin side, right? So Jira will automatically relate all
the issues with the new name.
Frankly speaking, I don't remember if I have done this when I have created
the 15.12 branch, but I think it should be good to move some of the tickets
accordingly, specifically:
* change all the issues with the "fix version" set to "release 15.12" to
"15.12.01"
I expect no issues with the "fix version" set to "release 15.12"
Because I monitored that and allowed only "Upcoming branch" or pending next
release versions (like 13.07.02) in this field
(I just checked, indeed none)
* move the issues with the "fix version" set to "upcoming branch", that
have been backported to the 15.12 branch, to the "15.12.01" version
I can "easily" do that for the issues where I removed "15.12.01" from the "Fix
Version" field
For the others backported since the branch has been created it will be harder.
Anyway we will do our best...
I also realise we did not use the (Community Day 1 - 2016 ends 28/Mar/16)
enough in the recent effort.
I hope it makes any sense
Yes thanks!
Jacques
Jacopo
On Sun, Mar 20, 2016 at 8:09 PM, Jacques Le Roux <
[email protected]> wrote:
I ask this because not understanding the purpose I removed some in few
"Fix Version/s:" fields, thinking it was a duplicate of "Upcoming Branch"
Jacques
Le 20/03/2016 14:46, Jacques Le Roux a écrit :
I thought we were only using Upcoming Branch for that. So now the
Upcoming Branch is one which is not yet created or is 15.12.01 unreleased
version a duplicate?
Jacques
Le 20/03/2016 12:29, Jacopo Cappellato a écrit :
Hi Jacques,
I have added it because it is required as a "Fix for" version for patches
that are backported to the 15.12 release.
Jacopo
On Sat, Mar 19, 2016 at 10:23 PM, Jacques Le Roux <
[email protected]> wrote:
Hi,
Who added the 15.12.01 unreleased version in Jira and why?
Thanks
Jacques
