Ah OK, It was not clear to me (and to Jacopo I guess), anyway the 1st vote was
confusing, thanks for voting again.
I must say I'm mostly against because of the surplus of effort necessary to
backport to both R17 and R18
About R20, as Pierre Smits mentioned in Slack should we not create a R19 before
;)
Then we would have to backport to 3 branches, and sincerely it's more work with Git than it was with Svn where we had scripts for that. I'd maybe
change my mind if OFBIZ-11297 would be done...
Jacques
Le 24/01/2020 à 14:44, Nicolas Malin a écrit :
Finally I voted to didn't skip the R17 in contradiction with my previous
message for the simple reason to respect the old deprecation code
process and increase the release activity.
For OFBiz integrator this change nothing because mostly use directly the
release branch on git, so the choice must be oriented for end user and
societies that develop some product for official release published.
In the end year we would be publish the R18 and create on the same time
the R20
Nicolas
On 30/09/2019 19:08, Nicolas Malin wrote:
I'm agree with idea to skip the R17 and go directly to R18,
We currently have many improvement and correction, present on R18 and
not R17 that are stable and fully functionnal
Nicolas
On 9/28/19 1:29 PM, Jacques Le Roux wrote:
Hi,
As reported by Rashi Dhagat in OFBIZ-11215 "Email password is not
working" in R16, and actually nor in R17.
It has been fixed in trunk and R18 with OFBIZ-4361. As mentioned
there, it's hard to backport to R17 not even speaking about R16!
I wonder if a case like that would not make R16 deprecated and start
to release R18, skipping R17.
Of course if people has the time, the nerves and the guts to backport
to R17 and R16 they are welcome
What do you think?
Jacques
