[DISCUSSION] R16 and R17: email password issue and releases

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[DISCUSSION] R16 and R17: email password issue and releases

Jacques Le Roux
Administrator
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

Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] R16 and R17: email password issue and releases

Nicolas Malin-2
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
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] R16 and R17: email password issue and releases

Gil Portenseigne
In reply to this post by Jacques Le Roux
Hello,

I think that the one year stabilisation period needed for a new branch
to be released is not that far for R18 (less than two month), so I
suppose that skipping R17 to avoid maintaining two release branches is a
good call.

Gil


Le 13:29 - samedi 28 sept., Jacques Le Roux a écrit :

> 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
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] R16 and R17: email password issue and releases

Jacques Le Roux
Administrator
Thanks Nicolas and Gil,

Because a release is an important thing, and without other answers than yours, I'll start a vote for that

Jacques


Le 04/10/2019 à 15:27, Gil Portenseigne a écrit :

> Hello,
>
> I think that the one year stabilisation period needed for a new branch
> to be released is not that far for R18 (less than two month), so I
> suppose that skipping R17 to avoid maintaining two release branches is a
> good call.
>
> Gil
>
>
> Le 13:29 - samedi 28 sept., Jacques Le Roux a écrit :
>> 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
>>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] R16 and R17: email password issue and releases

Deepak Dixit-5
In reply to this post by Jacques Le Roux
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 <
[hidden email]> 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
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] R16 and R17: email password issue and releases

Jacques Le Roux
Administrator
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 <
> [hidden email]> 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
>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: [DISCUSSION] R16 and R17: email password issue and releases

Deepak Dixit-5
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 <[hidden email]>
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 <
> > [hidden email]> 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
> >>
> >>
>