Hi All,
Since we don't have a consensus about my proposition and I don't see much
backporting efforts for about 3 months, I'll start a vote about it
Thanks
Jacques
Le 23/01/2020 à 14:35, Pierre Smits a écrit :
+1 on skipping r17
+1 on releasing first of r18
According to
https://issues.apache.org/jira/projects/OFBIZ?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased
the r18.12.01 is more ready to be released than r17.12.01.
Best regards,
Pierre Smits
*Apache Trafodion <https://trafodion.apache.org>, Vice President*
*Apache Directory <https://directory.apache.org>, PMC Member*
Apache Incubator <https://incubator.apache.org>, committer
*Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges)
since 2008*
Apache Steve <https://steve.apache.org>, committer
On Wed, Jan 22, 2020 at 12:21 PM Michael Brohl <[email protected]>
wrote:
According to
https://issues.apache.org/jira/projects/OFBIZ/versions/12338772 there is
not too much to do to get the r17 branch issues solved.
We could start an initiative to check the issues and their relevance,
fix the remaining and and do the release.
What do you think?
Thanks,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 22.01.20 um 12:11 schrieb Michael Brohl:
I am also in favor to get the r17 Branch released soon and not
skipping it.
Thanks,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 09.10.19 um 11:56 schrieb Deepak Dixit:
Yes Jacques,
We can make 16 as old, release R17 as current release (once we
officially
released it), start working on R18 to make it ready for release.
Kind Regards,
Deepak Dixit
On Wed, Oct 9, 2019 at 1:01 PM Jacques Le Roux
<[email protected]>
wrote:
Hi Deepak,
I have no problems with that. For demo R16 would stay our stable or we
could have it as old but not deprecated for instance? Ie we would
continue
to
maintain R16 (as we currently do as much as possible) it but not
demo it
and demo R17 as stable, right?
Jacques
Le 09/10/2019 à 08:19, Deepak Dixit a écrit :
I think due to one feature/bug skipping R17 is not good idea, I'll
try to
backport this work to R17.
We all are working since long to make R17 stable, and I think R17
is in
good shape.
Making R16 deprecate, I think we need to think about Release life
cycle,
release should have at least 5-7 year of life span. As a developer
perspective it's easy to switch to new branch, but as a user
perspective
its not easy to switch to new branch frequently.
Thanks & Regards
--
Deepak Dixit
ofbiz.apache.org
On Sat, Sep 28, 2019 at 5:11 PM Jacques Le Roux <
[email protected]> 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
