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 <
jacques.le.r...@les7arts.com> 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 <
>> jacopo.cappell...@hotwaxsystems.com> 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
>>>
>>>
>

Reply via email to