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 OFBiz <https://ofbiz.apache.org/> since 2008 (without privileges) *Apache Trafodion <https://trafodion.apache.org>, Vice President* *Apache Directory <https://directory.apache.org>, PMC Member* Apache Incubator <https://incubator.apache.org>, committer Apache Steve <https://steve.apache.org>, committer On Mon, Feb 24, 2020 at 3:52 PM Michael Brohl <[email protected]> wrote: > 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 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. > > > > Current example which reminds me of it: > > https://issues.apache.org/jira/browse/OFBIZ-11410 > > > > Thanks, > > > > Michael Brohl > > > > ecomify GmbH - www.ecomify.de > > > > > > > >
