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 release notes generated.
Project following that methodology often have a release branch for the next release. However, as OFBiz is not like any other project, I suggest you familiarise yourself again with the documentation ( https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz ). 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:42 PM Michael Brohl <michael.br...@ecomify.de> 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 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 > > > >
