Clarification about Jira version named "16.11.02"

[Jacopo Cappellato-5]

Hi all,

whenever a Jira ticket is resolved and the fix is back-ported to the 16.11
branch, please add the version "16.11.02" to the "Fix Version/s" field: in
fact 16.11.02 is the first release of the 16.11 branch in which the fix
will be published.

As a side note, when you report a bug that affects the 16.11 branch you can
set:
"Affects Version/s" = "Release Branch 16.11"
However it would be nice to know if the same bug affects also the release
16.11.01; if this is the case then please set:
"Affects Version/s" = "16.11.01"
In this case it is not necessary to specify "Release Branch 16.11" because
it is implied that if the bug affects the "16.11.01" release then it also
affected the 16.11 branch.
In short: "Release Branch 16.11" should only be used when the bug was
introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
or if you don't know if the bug affects the 16.11.01 release.

Regards,

Jacopo

[Deepak Dixit-3]

Thanks Jacopo for detail,

I found some some issues that have Trunk as fix version, I think it should
be "Upcoming Release"

And if fixes backported to older release it should set as described by
Jacopo in this thread.

Please correct me if I am missing something :)

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Mon, Dec 19, 2016 at 9:19 PM, Jacopo Cappellato <
[hidden email]> wrote:

> Hi all,
>
> whenever a Jira ticket is resolved and the fix is back-ported to the 16.11
> branch, please add the version "16.11.02" to the "Fix Version/s" field: in
> fact 16.11.02 is the first release of the 16.11 branch in which the fix
> will be published.
>
> As a side note, when you report a bug that affects the 16.11 branch you can
> set:
> "Affects Version/s" = "Release Branch 16.11"
> However it would be nice to know if the same bug affects also the release
> 16.11.01; if this is the case then please set:
> "Affects Version/s" = "16.11.01"
> In this case it is not necessary to specify "Release Branch 16.11" because
> it is implied that if the bug affects the "16.11.01" release then it also
> affected the 16.11 branch.
> In short: "Release Branch 16.11" should only be used when the bug was
> introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
> or if you don't know if the bug affects the 16.11.01 release.
>
> Regards,
>
> Jacopo
>

[Jacques Le Roux]

Hi Deepak, Jacopo,

I recently fixed a such issue at https://issues.apache.org/jira/browse/OFBIZ-9160 and put 2 comments there. Please refer to them, I don't want to
rehash all here.

I put comments there because things changed and I think it needs now a bit more explanation here and in wiki in the "OFBiz Committers Roles and
Responsibilities" page.

First I'm unsure it's you Jacopo who made the change, but I guess so. So this message is mostly questions for you, and I hope you had a happy birthday
(saw Sharan message on HipChat ;))

The "Upcoming Branch" unreleased version has disappeared and a new 17.12.01 unreleased version has been created.

I guess you (Jacopo) tried to follow the schema you suggested at "Guidelines for resolving Jira tickets",
<http://markmail.org/message/v3yswhnusu4elta5> but got sidetracked because of the postponing of the R17.12 creation.

So I went ahead as explained in my last OFBIZ-9160 comment:

<<I don't know if the previous "Upcoming Branch" has been renamed into 17.12.01 version in Jira but I just changed its date creation to 28/12/2017 and
created a new "Upcoming Branch" antedated as if it was created the 28/12/2017>>

I ask that because I want to update the "OFBiz Committers Roles and Responsibilities" page where these things are detailed and I want to be sure
before changing it.

Thanks

Jacques


Le 09/11/2017 à 10:13, Deepak Dixit a écrit :

> Thanks Jacopo for detail,
>
> I found some some issues that have Trunk as fix version, I think it should
> be "Upcoming Release"
>
> And if fixes backported to older release it should set as described by
> Jacopo in this thread.
>
> Please correct me if I am missing something :)
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
> www.hotwax.co
>
> On Mon, Dec 19, 2016 at 9:19 PM, Jacopo Cappellato <
> [hidden email]> wrote:
>
>> Hi all,
>>
>> whenever a Jira ticket is resolved and the fix is back-ported to the 16.11
>> branch, please add the version "16.11.02" to the "Fix Version/s" field: in
>> fact 16.11.02 is the first release of the 16.11 branch in which the fix
>> will be published.
>>
>> As a side note, when you report a bug that affects the 16.11 branch you can
>> set:
>> "Affects Version/s" = "Release Branch 16.11"
>> However it would be nice to know if the same bug affects also the release
>> 16.11.01; if this is the case then please set:
>> "Affects Version/s" = "16.11.01"
>> In this case it is not necessary to specify "Release Branch 16.11" because
>> it is implied that if the bug affects the "16.11.01" release then it also
>> affected the 16.11 branch.
>> In short: "Release Branch 16.11" should only be used when the bug was
>> introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
>> or if you don't know if the bug affects the 16.11.01 release.
>>
>> Regards,
>>
>> Jacopo
>>

[Jacques Le Roux]

Mmm, I'm not sure what I meant there :D http://markmail.org/message/3avgt6xopra3ieok

I can't find any "What's new" page or any warning about that anywhere or even the words "What's new"

I'd need to get back this day in history, not sure a tool like Confluence as the same agility than a version control tool (my favourite for this kind
of thing being svn)

Jacques


Le 08/01/2018 à 21:24, Jacques Le Roux a écrit :

> Hi Deepak, Jacopo,
>
> I recently fixed a such issue at https://issues.apache.org/jira/browse/OFBIZ-9160 and put 2 comments there. Please refer to them, I don't want to
> rehash all here.
>
> I put comments there because things changed and I think it needs now a bit more explanation here and in wiki in the "OFBiz Committers Roles and
> Responsibilities" page.
>
> First I'm unsure it's you Jacopo who made the change, but I guess so. So this message is mostly questions for you, and I hope you had a happy
> birthday (saw Sharan message on HipChat ;))
>
> The "Upcoming Branch" unreleased version has disappeared and a new 17.12.01 unreleased version has been created.
>
> I guess you (Jacopo) tried to follow the schema you suggested at "Guidelines for resolving Jira tickets",
> <http://markmail.org/message/v3yswhnusu4elta5> but got sidetracked because of the postponing of the R17.12 creation.
>
> So I went ahead as explained in my last OFBIZ-9160 comment:
>
> <<I don't know if the previous "Upcoming Branch" has been renamed into 17.12.01 version in Jira but I just changed its date creation to 28/12/2017
> and created a new "Upcoming Branch" antedated as if it was created the 28/12/2017>>
>
> I ask that because I want to update the "OFBiz Committers Roles and Responsibilities" page where these things are detailed and I want to be sure
> before changing it.
>
> Thanks
>
> Jacques
>
>
> Le 09/11/2017 à 10:13, Deepak Dixit a écrit :
>> Thanks Jacopo for detail,
>>
>> I found some some issues that have Trunk as fix version, I think it should
>> be "Upcoming Release"
>>
>> And if fixes backported to older release it should set as described by
>> Jacopo in this thread.
>>
>> Please correct me if I am missing something :)
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>> www.hotwax.co
>>
>> On Mon, Dec 19, 2016 at 9:19 PM, Jacopo Cappellato <
>> [hidden email]> wrote:
>>
>>> Hi all,
>>>
>>> whenever a Jira ticket is resolved and the fix is back-ported to the 16.11
>>> branch, please add the version "16.11.02" to the "Fix Version/s" field: in
>>> fact 16.11.02 is the first release of the 16.11 branch in which the fix
>>> will be published.
>>>
>>> As a side note, when you report a bug that affects the 16.11 branch you can
>>> set:
>>> "Affects Version/s" = "Release Branch 16.11"
>>> However it would be nice to know if the same bug affects also the release
>>> 16.11.01; if this is the case then please set:
>>> "Affects Version/s" = "16.11.01"
>>> In this case it is not necessary to specify "Release Branch 16.11" because
>>> it is implied that if the bug affects the "16.11.01" release then it also
>>> affected the 16.11 branch.
>>> In short: "Release Branch 16.11" should only be used when the bug was
>>> introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
>>> or if you don't know if the bug affects the 16.11.01 release.
>>>
>>> Regards,
>>>
>>> Jacopo
>>>
>
>

[Jacopo Cappellato-5]

Hi Jacques,

thanks for your review.
To summarize: I have indeed edited the versions (I did changes for 16.11.*
because of the new release and for 17.12) in Jira according to the
guidelines and more specifically renamed "Upcoming Branch" to "17.12.01";
however I forgot to create the new "Upcoming branch" version (thanks for
doing that).
As regards the start start date of the 17.12.01 version, we could consider
to set it on 28th November 2016 rather than on the date of the actual
creation of the branch: my reasoning is that when we will create the
release 17.12.01, we will publish for the first time all the features
implemented in the trunk since the date of the creation of the previous
feature branch (i.e. 27th, November 2016).

Jacopo

On Mon, Jan 8, 2018 at 9:24 PM, Jacques Le Roux <
[hidden email]> wrote:

> Hi Deepak, Jacopo,
>
> I recently fixed a such issue at https://issues.apache.org/jira
> /browse/OFBIZ-9160 and put 2 comments there. Please refer to them, I
> don't want to rehash all here.
>
> I put comments there because things changed and I think it needs now a bit
> more explanation here and in wiki in the "OFBiz Committers Roles and
> Responsibilities" page.
>
> First I'm unsure it's you Jacopo who made the change, but I guess so. So
> this message is mostly questions for you, and I hope you had a happy
> birthday (saw Sharan message on HipChat ;))
>
> The "Upcoming Branch" unreleased version has disappeared and a new
> 17.12.01 unreleased version has been created.
>
> I guess you (Jacopo) tried to follow the schema you suggested at
> "Guidelines for resolving Jira tickets", <http://markmail.org/message/v
> 3yswhnusu4elta5> but got sidetracked because of the postponing of the
> R17.12 creation.
>
> So I went ahead as explained in my last OFBIZ-9160 comment:
>
> <<I don't know if the previous "Upcoming Branch" has been renamed into
> 17.12.01 version in Jira but I just changed its date creation to 28/12/2017
> and created a new "Upcoming Branch" antedated as if it was created the
> 28/12/2017>>
>
> I ask that because I want to update the "OFBiz Committers Roles and
> Responsibilities" page where these things are detailed and I want to be
> sure before changing it.
>
> Thanks
>
> Jacques
>
>
>
> Le 09/11/2017 à 10:13, Deepak Dixit a écrit :
>
>> Thanks Jacopo for detail,
>>
>> I found some some issues that have Trunk as fix version, I think it should
>> be "Upcoming Release"
>>
>> And if fixes backported to older release it should set as described by
>> Jacopo in this thread.
>>
>> Please correct me if I am missing something :)
>>
>> Thanks & Regards
>> --
>> Deepak Dixit
>> www.hotwaxsystems.com
>> www.hotwax.co
>>
>> On Mon, Dec 19, 2016 at 9:19 PM, Jacopo Cappellato <
>> [hidden email]> wrote:
>>
>> Hi all,
>>>
>>> whenever a Jira ticket is resolved and the fix is back-ported to the
>>> 16.11
>>> branch, please add the version "16.11.02" to the "Fix Version/s" field:
>>> in
>>> fact 16.11.02 is the first release of the 16.11 branch in which the fix
>>> will be published.
>>>
>>> As a side note, when you report a bug that affects the 16.11 branch you
>>> can
>>> set:
>>> "Affects Version/s" = "Release Branch 16.11"
>>> However it would be nice to know if the same bug affects also the release
>>> 16.11.01; if this is the case then please set:
>>> "Affects Version/s" = "16.11.01"
>>> In this case it is not necessary to specify "Release Branch 16.11"
>>> because
>>> it is implied that if the bug affects the "16.11.01" release then it also
>>> affected the 16.11 branch.
>>> In short: "Release Branch 16.11" should only be used when the bug was
>>> introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
>>> or if you don't know if the bug affects the 16.11.01 release.
>>>
>>> Regards,
>>>
>>> Jacopo
>>>
>>>
>

[Jacques Le Roux]

Hi Jacopo,

OK makes totally sense for the date. I'll change that back

Jacques


Le 09/01/2018 à 08:50, Jacopo Cappellato a écrit :

> Hi Jacques,
>
> thanks for your review.
> To summarize: I have indeed edited the versions (I did changes for 16.11.*
> because of the new release and for 17.12) in Jira according to the
> guidelines and more specifically renamed "Upcoming Branch" to "17.12.01";
> however I forgot to create the new "Upcoming branch" version (thanks for
> doing that).
> As regards the start start date of the 17.12.01 version, we could consider
> to set it on 28th November 2016 rather than on the date of the actual
> creation of the branch: my reasoning is that when we will create the
> release 17.12.01, we will publish for the first time all the features
> implemented in the trunk since the date of the creation of the previous
> feature branch (i.e. 27th, November 2016).
>
> Jacopo
>
> On Mon, Jan 8, 2018 at 9:24 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Hi Deepak, Jacopo,
>>
>> I recently fixed a such issue at https://issues.apache.org/jira
>> /browse/OFBIZ-9160 and put 2 comments there. Please refer to them, I
>> don't want to rehash all here.
>>
>> I put comments there because things changed and I think it needs now a bit
>> more explanation here and in wiki in the "OFBiz Committers Roles and
>> Responsibilities" page.
>>
>> First I'm unsure it's you Jacopo who made the change, but I guess so. So
>> this message is mostly questions for you, and I hope you had a happy
>> birthday (saw Sharan message on HipChat ;))
>>
>> The "Upcoming Branch" unreleased version has disappeared and a new
>> 17.12.01 unreleased version has been created.
>>
>> I guess you (Jacopo) tried to follow the schema you suggested at
>> "Guidelines for resolving Jira tickets", <http://markmail.org/message/v
>> 3yswhnusu4elta5> but got sidetracked because of the postponing of the
>> R17.12 creation.
>>
>> So I went ahead as explained in my last OFBIZ-9160 comment:
>>
>> <<I don't know if the previous "Upcoming Branch" has been renamed into
>> 17.12.01 version in Jira but I just changed its date creation to 28/12/2017
>> and created a new "Upcoming Branch" antedated as if it was created the
>> 28/12/2017>>
>>
>> I ask that because I want to update the "OFBiz Committers Roles and
>> Responsibilities" page where these things are detailed and I want to be
>> sure before changing it.
>>
>> Thanks
>>
>> Jacques
>>
>>
>>
>> Le 09/11/2017 à 10:13, Deepak Dixit a écrit :
>>
>>> Thanks Jacopo for detail,
>>>
>>> I found some some issues that have Trunk as fix version, I think it should
>>> be "Upcoming Release"
>>>
>>> And if fixes backported to older release it should set as described by
>>> Jacopo in this thread.
>>>
>>> Please correct me if I am missing something :)
>>>
>>> Thanks & Regards
>>> --
>>> Deepak Dixit
>>> www.hotwaxsystems.com
>>> www.hotwax.co
>>>
>>> On Mon, Dec 19, 2016 at 9:19 PM, Jacopo Cappellato <
>>> [hidden email]> wrote:
>>>
>>> Hi all,
>>>> whenever a Jira ticket is resolved and the fix is back-ported to the
>>>> 16.11
>>>> branch, please add the version "16.11.02" to the "Fix Version/s" field:
>>>> in
>>>> fact 16.11.02 is the first release of the 16.11 branch in which the fix
>>>> will be published.
>>>>
>>>> As a side note, when you report a bug that affects the 16.11 branch you
>>>> can
>>>> set:
>>>> "Affects Version/s" = "Release Branch 16.11"
>>>> However it would be nice to know if the same bug affects also the release
>>>> 16.11.01; if this is the case then please set:
>>>> "Affects Version/s" = "16.11.01"
>>>> In this case it is not necessary to specify "Release Branch 16.11"
>>>> because
>>>> it is implied that if the bug affects the "16.11.01" release then it also
>>>> affected the 16.11 branch.
>>>> In short: "Release Branch 16.11" should only be used when the bug was
>>>> introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
>>>> or if you don't know if the bug affects the 16.11.01 release.
>>>>
>>>> Regards,
>>>>
>>>> Jacopo
>>>>
>>>>

[Jacques Le Roux]

Done, should we not remove R14 and R15 version?


Le 09/01/2018 à 10:12, Jacques Le Roux a écrit :

> Hi Jacopo,
>
> OK makes totally sense for the date. I'll change that back
>
> Jacques
>
>
> Le 09/01/2018 à 08:50, Jacopo Cappellato a écrit :
>> Hi Jacques,
>>
>> thanks for your review.
>> To summarize: I have indeed edited the versions (I did changes for 16.11.*
>> because of the new release and for 17.12) in Jira according to the
>> guidelines and more specifically renamed "Upcoming Branch" to "17.12.01";
>> however I forgot to create the new "Upcoming branch" version (thanks for
>> doing that).
>> As regards the start start date of the 17.12.01 version, we could consider
>> to set it on 28th November 2016 rather than on the date of the actual
>> creation of the branch: my reasoning is that when we will create the
>> release 17.12.01, we will publish for the first time all the features
>> implemented in the trunk since the date of the creation of the previous
>> feature branch (i.e. 27th, November 2016).
>>
>> Jacopo
>>
>> On Mon, Jan 8, 2018 at 9:24 PM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> Hi Deepak, Jacopo,
>>>
>>> I recently fixed a such issue at https://issues.apache.org/jira
>>> /browse/OFBIZ-9160 and put 2 comments there. Please refer to them, I
>>> don't want to rehash all here.
>>>
>>> I put comments there because things changed and I think it needs now a bit
>>> more explanation here and in wiki in the "OFBiz Committers Roles and
>>> Responsibilities" page.
>>>
>>> First I'm unsure it's you Jacopo who made the change, but I guess so. So
>>> this message is mostly questions for you, and I hope you had a happy
>>> birthday (saw Sharan message on HipChat ;))
>>>
>>> The "Upcoming Branch" unreleased version has disappeared and a new
>>> 17.12.01 unreleased version has been created.
>>>
>>> I guess you (Jacopo) tried to follow the schema you suggested at
>>> "Guidelines for resolving Jira tickets", <http://markmail.org/message/v
>>> 3yswhnusu4elta5> but got sidetracked because of the postponing of the
>>> R17.12 creation.
>>>
>>> So I went ahead as explained in my last OFBIZ-9160 comment:
>>>
>>> <<I don't know if the previous "Upcoming Branch" has been renamed into
>>> 17.12.01 version in Jira but I just changed its date creation to 28/12/2017
>>> and created a new "Upcoming Branch" antedated as if it was created the
>>> 28/12/2017>>
>>>
>>> I ask that because I want to update the "OFBiz Committers Roles and
>>> Responsibilities" page where these things are detailed and I want to be
>>> sure before changing it.
>>>
>>> Thanks
>>>
>>> Jacques
>>>
>>>
>>>
>>> Le 09/11/2017 à 10:13, Deepak Dixit a écrit :
>>>
>>>> Thanks Jacopo for detail,
>>>>
>>>> I found some some issues that have Trunk as fix version, I think it should
>>>> be "Upcoming Release"
>>>>
>>>> And if fixes backported to older release it should set as described by
>>>> Jacopo in this thread.
>>>>
>>>> Please correct me if I am missing something :)
>>>>
>>>> Thanks & Regards
>>>> --
>>>> Deepak Dixit
>>>> www.hotwaxsystems.com
>>>> www.hotwax.co
>>>>
>>>> On Mon, Dec 19, 2016 at 9:19 PM, Jacopo Cappellato <
>>>> [hidden email]> wrote:
>>>>
>>>> Hi all,
>>>>> whenever a Jira ticket is resolved and the fix is back-ported to the
>>>>> 16.11
>>>>> branch, please add the version "16.11.02" to the "Fix Version/s" field:
>>>>> in
>>>>> fact 16.11.02 is the first release of the 16.11 branch in which the fix
>>>>> will be published.
>>>>>
>>>>> As a side note, when you report a bug that affects the 16.11 branch you
>>>>> can
>>>>> set:
>>>>> "Affects Version/s" = "Release Branch 16.11"
>>>>> However it would be nice to know if the same bug affects also the release
>>>>> 16.11.01; if this is the case then please set:
>>>>> "Affects Version/s" = "16.11.01"
>>>>> In this case it is not necessary to specify "Release Branch 16.11"
>>>>> because
>>>>> it is implied that if the bug affects the "16.11.01" release then it also
>>>>> affected the 16.11 branch.
>>>>> In short: "Release Branch 16.11" should only be used when the bug was
>>>>> introduced in the branch after the 16.11.01 (and doesn't affect 16.11.01)
>>>>> or if you don't know if the bug affects the 16.11.01 release.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Jacopo
>>>>>
>>>>>
>
>

[Jacopo Cappellato-5]

On Tue, Jan 9, 2018 at 10:18 AM, Jacques Le Roux <
[hidden email]> wrote:

> Done, should we not remove R14 and R15 version?
>
>
This is a good question.
In fact I have spent some time thinking about it and I propose to archive
all the Jira versions for "release branches" that are:
* "Release Branch 16.11": we will use instead 16.11.04 for the "Affects
Version" field and the 16.11.05 for the "Fix Version" field
* "Release Branch 15.12": we can simply archive it as Jacques suggested
* "Release Branch 14.12": we can simply archive it as Jacques suggested
* "Release Branch 13.07": we can simply archive it as Jacques suggested
* "Trunk": this is a special one; I propose to archive it and use "Upcoming
Branch" instead of it but rename it from "Upcoming Branch" to
"Trunk/Upcoming Branch" (or similar)

In this way we will have two simpler and less confusing groups of Jira
versions:
A) released (to be used for the "Affects Version" field):
- "16.11.04"
B) unreleased (to be used for the "Fix Version" field):
- "16.11.05"
- "Trunk/Upcoming Branch"

When we will create the new branch we will rename it to xx.yy.01 and we
will create a new version with the "Trunk/Upcoming Branch" name (exactly as
we are doing with the "Upcoming Branch" version).

Jacopo

[Jacques Le Roux]

Le 09/01/2018 à 14:55, Jacopo Cappellato a écrit :

> On Tue, Jan 9, 2018 at 10:18 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Done, should we not remove R14 and R15 version?
>>
>>
> This is a good question.
> In fact I have spent some time thinking about it and I propose to archive
> all the Jira versions for "release branches" that are:
> * "Release Branch 16.11": we will use instead 16.11.04 for the "Affects
> Version" field and the 16.11.05 for the "Fix Version" field
> * "Release Branch 15.12": we can simply archive it as Jacques suggested
> * "Release Branch 14.12": we can simply archive it as Jacques suggested
> * "Release Branch 13.07": we can simply archive it as Jacques suggested
> * "Trunk": this is a special one; I propose to archive it and use "Upcoming
> Branch" instead of it but rename it from "Upcoming Branch" to
> "Trunk/Upcoming Branch" (or similar)
>
> In this way we will have two simpler and less confusing groups of Jira
> versions:
> A) released (to be used for the "Affects Version" field):
> - "16.11.04"
> B) unreleased (to be used for the "Fix Version" field):
> - "16.11.05"
> - "Trunk/Upcoming Branch"
>
> When we will create the new branch we will rename it to xx.yy.01 and we
> will create a new version with the "Trunk/Upcoming Branch" name (exactly as
> we are doing with the "Upcoming Branch" version).
>
> Jacopo
>

Hi Jacopo,

That sounds good to me.  Should we not document the whole Jira process at
https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz ?

BTW I'll have a look at the "Updating related files" section

Thanks

Jacques