Thanks, Jacopo!
Will amend my fix versions.
Michael
Am 24.02.20 um 15:56 schrieb Jacopo Cappellato:
Hi Michael,
I have just created the version in Jira for 17.12.02: we should now use it.
Thanks,
Jacopo
On Mon, Feb 24, 2020 at 3:42 PM Michael Brohl
wrote:
Hi all,
how do set the "fixed
Hi Michael,
I have just created the version in Jira for 17.12.02: we should now use it.
Thanks,
Jacopo
On Mon, Feb 24, 2020 at 3:42 PM Michael Brohl
wrote:
> Hi all,
>
> how do set the "fixed versions" in the case of a pending release like we
> have with 17.12.01 now?
>
> IMO 17.12.01 would b
I should have mentioned that there is no 17.12.02 release available at
the moment, therefore I chose the Release Branch.
The provided link does not seem to be related to my particular question
though.
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 24.02.20 um 15:52 schrieb Pierre Smits:
M
As an addendum to my previous posting regarding 'Project following that
methodology often have a release branch for the next release.'
In this case 'r17.12.01' so that there is an alignment between ticket and
repository.
Met vriendelijke groet,
Pierre Smits
*Proud* *contributor** of* Apache OFB
Michael, all,
It is very common that when an issue is identified for a particular release
(in this case 17.12.01) that, when fixed, the 'version field' is set to the
next version (to be released). That way, when the moment of releasing the
next release comes around, tickets can be identified. And
Reference to the issue where I selected "Release branch 17.12":
https://issues.apache.org/jira/browse/OFBIZ-11346
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 24.02.20 um 15:42 schrieb Michael Brohl:
Hi all,
how do set the "fixed versions" in the case of a pending release like
we have wi
Hi all,
how do set the "fixed versions" in the case of a pending release like we
have with 17.12.01 now?
IMO 17.12.01 would be wrong because it was tagged before and the change
would go to 17.12.02. In some case at the weekend I selected "Release
Branch 17.12" but not sure about it.
Curren
