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

2019-10-09 Thread 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 wrote: > Hi Deepak, > > I have no problems with that. For demo R16

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

2019-10-09 Thread Jacques Le Roux
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 à

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

2019-10-09 Thread Deepak Dixit
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