Planning for the creation of new 18.12 branches
Locked
Planning for the creation of new 18.12 branches
 
|
Hello,
The time pass and the end year is near, maybe it's the time to prepare next releases branches. Two questions : * Are you agree to create releases 18.12 branches for framework and plugin ? * Do you have some priority issue that you absolutely need fbefore create theses branches ? I see for my point of view OFBIZ-4361 and OFBIZ-10145. I believe/will/try to free some time for working on. Cheers, Nicolas -- logoNrd <https://nereide.fr/> Nicolas Malin The apache way <http://theapacheway.com/> : *Charity* Apache’s mission is providing software for the public good. [hidden email] 8 rue des Déportés 37000 TOURS, 02 47 50 30 54 Apache OFBiz <http://ofbiz.apache.org/>|The Apache Way <http://theapacheway.com/>|réseau LE <http://www.libre-entreprise.org/> |
Re: Planning for the creation of new 18.12 branches
Administrator
|
Le 19/12/2018 à 10:14, Nicolas Malin a écrit :
> Hello, > > The time pass and the end year is near, maybe it's the time to prepare next releases branches. > > Two questions : > > * Are you agree to create releases 18.12 branches for framework and plugin ? > > * Do you have some priority issue that you absolutely need fbefore create theses branches ? > > I see for my point of view OFBIZ-4361 and OFBIZ-10145. I believe/will/try to free some time for working on. > > Cheers, > > Nicolas > As I think we agreed, we need to check all the blocker before releasing (not freezing) . So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a possible 18.12 branches (trunk+plugins) Thanks Jacques |
Re: Planning for the creation of new 18.12 branches
|
|
I agree,
We should create the next release (18.12) for framework and plugins. I'll check for issues, and if found will share here. Thanks & Regards -- Deepak Dixit On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < [hidden email]> wrote: > Le 19/12/2018 à 10:14, Nicolas Malin a écrit : > > Hello, > > > > The time pass and the end year is near, maybe it's the time to prepare > next releases branches. > > > > Two questions : > > > > * Are you agree to create releases 18.12 branches for framework and > plugin ? > > > > * Do you have some priority issue that you absolutely need fbefore > create theses branches ? > > > > I see for my point of view OFBIZ-4361 and OFBIZ-10145. I > believe/will/try to free some time for working on. > > > > Cheers, > > > > Nicolas > > > Hi Nicolas, All, > > As I think we agreed, we need to check all the blocker before releasing > (not freezing) . > > So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a possible > 18.12 branches (trunk+plugins) > > Thanks > > Jacques > > |
Re: Planning for the creation of new 18.12 branches
|
|
Four days before the end of year :)
If no opposition, I will create it tomorrow Nicolas On 19/12/2018 11:44, Deepak Dixit wrote: > I agree, > > We should create the next release (18.12) for framework and plugins. > I'll check for issues, and if found will share here. > Thanks & Regards > -- > Deepak Dixit > > > > On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < > [hidden email]> wrote: > >> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>> Hello, >>> >>> The time pass and the end year is near, maybe it's the time to prepare >> next releases branches. >>> Two questions : >>> >>> * Are you agree to create releases 18.12 branches for framework and >> plugin ? >>> * Do you have some priority issue that you absolutely need fbefore >> create theses branches ? >>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >> believe/will/try to free some time for working on. >>> Cheers, >>> >>> Nicolas >>> >> Hi Nicolas, All, >> >> As I think we agreed, we need to check all the blocker before releasing >> (not freezing) . >> >> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a possible >> 18.12 branches (trunk+plugins) >> >> Thanks >> >> Jacques >> >> |
|
It's okay whatever folks decide, but I think it would be nice if we
can upgrade Java for a new branch. On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin <[hidden email]> wrote: > > Four days before the end of year :) > > If no opposition, I will create it tomorrow > > Nicolas > > On 19/12/2018 11:44, Deepak Dixit wrote: > > I agree, > > > > We should create the next release (18.12) for framework and plugins. > > I'll check for issues, and if found will share here. > > Thanks & Regards > > -- > > Deepak Dixit > > > > > > > > On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < > > [hidden email]> wrote: > > > >> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : > >>> Hello, > >>> > >>> The time pass and the end year is near, maybe it's the time to prepare > >> next releases branches. > >>> Two questions : > >>> > >>> * Are you agree to create releases 18.12 branches for framework and > >> plugin ? > >>> * Do you have some priority issue that you absolutely need fbefore > >> create theses branches ? > >>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I > >> believe/will/try to free some time for working on. > >>> Cheers, > >>> > >>> Nicolas > >>> > >> Hi Nicolas, All, > >> > >> As I think we agreed, we need to check all the blocker before releasing > >> (not freezing) . > >> > >> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a possible > >> 18.12 branches (trunk+plugins) > >> > >> Thanks > >> > >> Jacques > >> > >> |
Re: Planning for the creation of new 18.12 branches
|
Administrator
|
That's something that must be put in the balance indeed. No problems if we create a 19.01 or later branch for me...
Jacques Le 27/12/2018 à 10:50, Taher Alkhateeb a écrit : > It's okay whatever folks decide, but I think it would be nice if we > can upgrade Java for a new branch. > > On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin <[hidden email]> wrote: >> Four days before the end of year :) >> >> If no opposition, I will create it tomorrow >> >> Nicolas >> >> On 19/12/2018 11:44, Deepak Dixit wrote: >>> I agree, >>> >>> We should create the next release (18.12) for framework and plugins. >>> I'll check for issues, and if found will share here. >>> Thanks & Regards >>> -- >>> Deepak Dixit >>> >>> >>> >>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < >>> [hidden email]> wrote: >>> >>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>>>> Hello, >>>>> >>>>> The time pass and the end year is near, maybe it's the time to prepare >>>> next releases branches. >>>>> Two questions : >>>>> >>>>> * Are you agree to create releases 18.12 branches for framework and >>>> plugin ? >>>>> * Do you have some priority issue that you absolutely need fbefore >>>> create theses branches ? >>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >>>> believe/will/try to free some time for working on. >>>>> Cheers, >>>>> >>>>> Nicolas >>>>> >>>> Hi Nicolas, All, >>>> >>>> As I think we agreed, we need to check all the blocker before releasing >>>> (not freezing) . >>>> >>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a possible >>>> 18.12 branches (trunk+plugins) >>>> >>>> Thanks >>>> >>>> Jacques >>>> >>>> |
Re: Planning for the creation of new 18.12 branches
|
|
In reply to this post by taher
We can create a branch and can backport java upgrade changes to 18.12 as
well. Thanks & Regards -- Deepak Dixit On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb <[hidden email]> wrote: > It's okay whatever folks decide, but I think it would be nice if we > can upgrade Java for a new branch. > > On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin <[hidden email]> > wrote: > > > > Four days before the end of year :) > > > > If no opposition, I will create it tomorrow > > > > Nicolas > > > > On 19/12/2018 11:44, Deepak Dixit wrote: > > > I agree, > > > > > > We should create the next release (18.12) for framework and plugins. > > > I'll check for issues, and if found will share here. > > > Thanks & Regards > > > -- > > > Deepak Dixit > > > > > > > > > > > > On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < > > > [hidden email]> wrote: > > > > > >> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : > > >>> Hello, > > >>> > > >>> The time pass and the end year is near, maybe it's the time to > prepare > > >> next releases branches. > > >>> Two questions : > > >>> > > >>> * Are you agree to create releases 18.12 branches for framework and > > >> plugin ? > > >>> * Do you have some priority issue that you absolutely need fbefore > > >> create theses branches ? > > >>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I > > >> believe/will/try to free some time for working on. > > >>> Cheers, > > >>> > > >>> Nicolas > > >>> > > >> Hi Nicolas, All, > > >> > > >> As I think we agreed, we need to check all the blocker before > releasing > > >> (not freezing) . > > >> > > >> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a > possible > > >> 18.12 branches (trunk+plugins) > > >> > > >> Thanks > > >> > > >> Jacques > > >> > > >> > |
Re: Planning for the creation of new 18.12 branches
|
Administrator
|
Yes I thought about that too, would not be a problem for me
Jacques Le 27/12/2018 à 11:35, Deepak Dixit a écrit : > We can create a branch and can backport java upgrade changes to 18.12 as > well. > Thanks & Regards > -- > Deepak Dixit > > > > On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb <[hidden email]> > wrote: > >> It's okay whatever folks decide, but I think it would be nice if we >> can upgrade Java for a new branch. >> >> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin <[hidden email]> >> wrote: >>> Four days before the end of year :) >>> >>> If no opposition, I will create it tomorrow >>> >>> Nicolas >>> >>> On 19/12/2018 11:44, Deepak Dixit wrote: >>>> I agree, >>>> >>>> We should create the next release (18.12) for framework and plugins. >>>> I'll check for issues, and if found will share here. >>>> Thanks & Regards >>>> -- >>>> Deepak Dixit >>>> >>>> >>>> >>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < >>>> [hidden email]> wrote: >>>> >>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>>>>> Hello, >>>>>> >>>>>> The time pass and the end year is near, maybe it's the time to >> prepare >>>>> next releases branches. >>>>>> Two questions : >>>>>> >>>>>> * Are you agree to create releases 18.12 branches for framework and >>>>> plugin ? >>>>>> * Do you have some priority issue that you absolutely need fbefore >>>>> create theses branches ? >>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >>>>> believe/will/try to free some time for working on. >>>>>> Cheers, >>>>>> >>>>>> Nicolas >>>>>> >>>>> Hi Nicolas, All, >>>>> >>>>> As I think we agreed, we need to check all the blocker before >> releasing >>>>> (not freezing) . >>>>> >>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a >> possible >>>>> 18.12 branches (trunk+plugins) >>>>> >>>>> Thanks >>>>> >>>>> Jacques >>>>> >>>>> |
|
|
In reply to this post by Deepak Dixit-4
yeah I guess that would work too if it is okay to push a big change
into that branch On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> wrote: > > We can create a branch and can backport java upgrade changes to 18.12 as > well. > Thanks & Regards > -- > Deepak Dixit > > > > On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb <[hidden email]> > wrote: > > > It's okay whatever folks decide, but I think it would be nice if we > > can upgrade Java for a new branch. > > > > On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin <[hidden email]> > > wrote: > > > > > > Four days before the end of year :) > > > > > > If no opposition, I will create it tomorrow > > > > > > Nicolas > > > > > > On 19/12/2018 11:44, Deepak Dixit wrote: > > > > I agree, > > > > > > > > We should create the next release (18.12) for framework and plugins. > > > > I'll check for issues, and if found will share here. > > > > Thanks & Regards > > > > -- > > > > Deepak Dixit > > > > > > > > > > > > > > > > On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < > > > > [hidden email]> wrote: > > > > > > > >> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : > > > >>> Hello, > > > >>> > > > >>> The time pass and the end year is near, maybe it's the time to > > prepare > > > >> next releases branches. > > > >>> Two questions : > > > >>> > > > >>> * Are you agree to create releases 18.12 branches for framework and > > > >> plugin ? > > > >>> * Do you have some priority issue that you absolutely need fbefore > > > >> create theses branches ? > > > >>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I > > > >> believe/will/try to free some time for working on. > > > >>> Cheers, > > > >>> > > > >>> Nicolas > > > >>> > > > >> Hi Nicolas, All, > > > >> > > > >> As I think we agreed, we need to check all the blocker before > > releasing > > > >> (not freezing) . > > > >> > > > >> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a > > possible > > > >> 18.12 branches (trunk+plugins) > > > >> > > > >> Thanks > > > >> > > > >> Jacques > > > >> > > > >> > > |
Re: Planning for the creation of new 18.12 branches
|
|
Yes, that would be a solution.
I'm also fine if we would do a 19.x branch. For the future, we could aim to have a release more towards the middle of the year to avoid last-minute branching between Christmas and New Year ;-) The above would fit perfectly with this plan: 1. create an 18.12 branch and stabilize it 2. release 17.12 ;-) 3. create a 19.x (x = {6..10} branch with the Java Upgrade This would not break the yearly release branch and give us time for the Java 11 Update in 19.x. 19.x would be earlier next year so we get out of the end of year-hurries . Thanks, Michael Am 27.12.18 um 12:38 schrieb Taher Alkhateeb: > yeah I guess that would work too if it is okay to push a big change > into that branch > > > On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> wrote: >> We can create a branch and can backport java upgrade changes to 18.12 as >> well. >> Thanks & Regards >> -- >> Deepak Dixit >> >> >> >> On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb <[hidden email]> >> wrote: >> >>> It's okay whatever folks decide, but I think it would be nice if we >>> can upgrade Java for a new branch. >>> >>> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin <[hidden email]> >>> wrote: >>>> Four days before the end of year :) >>>> >>>> If no opposition, I will create it tomorrow >>>> >>>> Nicolas >>>> >>>> On 19/12/2018 11:44, Deepak Dixit wrote: >>>>> I agree, >>>>> >>>>> We should create the next release (18.12) for framework and plugins. >>>>> I'll check for issues, and if found will share here. >>>>> Thanks & Regards >>>>> -- >>>>> Deepak Dixit >>>>> >>>>> >>>>> >>>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < >>>>> [hidden email]> wrote: >>>>> >>>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>>>>>> Hello, >>>>>>> >>>>>>> The time pass and the end year is near, maybe it's the time to >>> prepare >>>>>> next releases branches. >>>>>>> Two questions : >>>>>>> >>>>>>> * Are you agree to create releases 18.12 branches for framework and >>>>>> plugin ? >>>>>>> * Do you have some priority issue that you absolutely need fbefore >>>>>> create theses branches ? >>>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >>>>>> believe/will/try to free some time for working on. >>>>>>> Cheers, >>>>>>> >>>>>>> Nicolas >>>>>>> >>>>>> Hi Nicolas, All, >>>>>> >>>>>> As I think we agreed, we need to check all the blocker before >>> releasing >>>>>> (not freezing) . >>>>>> >>>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a >>> possible >>>>>> 18.12 branches (trunk+plugins) >>>>>> >>>>>> Thanks >>>>>> >>>>>> Jacques >>>>>> >>>>>> |
smime.p7s (5K)
Re: Planning for the creation of new 18.12 branches
|
|
Hello
On 27/12/2018 13:49, Michael Brohl wrote: > Yes, that would be a solution. > > I'm also fine if we would do a 19.x branch. For the future, we could > aim to have a release more towards the middle of the year to avoid > last-minute branching between Christmas and New Year ;-) > > The above would fit perfectly with this plan: > > 1. create an 18.12 branch and stabilize it > > 2. release 17.12 ;-) > > 3. create a 19.x (x = {6..10} branch with the Java Upgrade I agree with that and I have no problem to backport huge commit on the first few month after branch creation. :) sure create a branch on the last days of the year for respect own release rules it's not perfect but i'm sure help to activity community I'm also in favor to create the release branch in october. I'll be careful with that the next year ! Nicolas > > > This would not break the yearly release branch and give us time for > the Java 11 Update in 19.x. 19.x would be earlier next year so we get > out of the end of year-hurries . > > Thanks, > > Michael > > > Am 27.12.18 um 12:38 schrieb Taher Alkhateeb: >> yeah I guess that would work too if it is okay to push a big change >> into that branch >> >> >> On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> >> wrote: >>> We can create a branch and can backport java upgrade changes to >>> 18.12 as >>> well. >>> Thanks & Regards >>> -- >>> Deepak Dixit >>> >>> >>> >>> On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb >>> <[hidden email]> >>> wrote: >>> >>>> It's okay whatever folks decide, but I think it would be nice if we >>>> can upgrade Java for a new branch. >>>> >>>> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin >>>> <[hidden email]> >>>> wrote: >>>>> Four days before the end of year :) >>>>> >>>>> If no opposition, I will create it tomorrow >>>>> >>>>> Nicolas >>>>> >>>>> On 19/12/2018 11:44, Deepak Dixit wrote: >>>>>> I agree, >>>>>> >>>>>> We should create the next release (18.12) for framework and plugins. >>>>>> I'll check for issues, and if found will share here. >>>>>> Thanks & Regards >>>>>> -- >>>>>> Deepak Dixit >>>>>> >>>>>> >>>>>> >>>>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < >>>>>> [hidden email]> wrote: >>>>>> >>>>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>>>>>>> Hello, >>>>>>>> >>>>>>>> The time pass and the end year is near, maybe it's the time to >>>> prepare >>>>>>> next releases branches. >>>>>>>> Two questions : >>>>>>>> >>>>>>>> * Are you agree to create releases 18.12 branches for >>>>>>>> framework and >>>>>>> plugin ? >>>>>>>> * Do you have some priority issue that you absolutely need >>>>>>>> fbefore >>>>>>> create theses branches ? >>>>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >>>>>>> believe/will/try to free some time for working on. >>>>>>>> Cheers, >>>>>>>> >>>>>>>> Nicolas >>>>>>>> >>>>>>> Hi Nicolas, All, >>>>>>> >>>>>>> As I think we agreed, we need to check all the blocker before >>>> releasing >>>>>>> (not freezing) . >>>>>>> >>>>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a >>>> possible >>>>>>> 18.12 branches (trunk+plugins) >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Jacques >>>>>>> >>>>>>> > |
Re: Planning for the creation of new 18.12 branches
|
|
In reply to this post by Michael Brohl-3
I agree that to proceed and create the branch now and then, over the next
few months, as a community we will refine our strategy and even decide on which of the various branches we should focus on more. Jacopo On Thu, Dec 27, 2018 at 1:59 PM Michael Brohl <[hidden email]> wrote: > Yes, that would be a solution. > > I'm also fine if we would do a 19.x branch. For the future, we could aim > to have a release more towards the middle of the year to avoid > last-minute branching between Christmas and New Year ;-) > > The above would fit perfectly with this plan: > > 1. create an 18.12 branch and stabilize it > > 2. release 17.12 ;-) > > 3. create a 19.x (x = {6..10} branch with the Java Upgrade > > > This would not break the yearly release branch and give us time for the > Java 11 Update in 19.x. 19.x would be earlier next year so we get out of > the end of year-hurries . > > Thanks, > > Michael > > > Am 27.12.18 um 12:38 schrieb Taher Alkhateeb: > > yeah I guess that would work too if it is okay to push a big change > > into that branch > > > > > > On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> > wrote: > >> We can create a branch and can backport java upgrade changes to 18.12 as > >> well. > >> Thanks & Regards > >> -- > >> Deepak Dixit > >> > >> > >> > >> On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb < > [hidden email]> > >> wrote: > >> > >>> It's okay whatever folks decide, but I think it would be nice if we > >>> can upgrade Java for a new branch. > >>> > >>> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin < > [hidden email]> > >>> wrote: > >>>> Four days before the end of year :) > >>>> > >>>> If no opposition, I will create it tomorrow > >>>> > >>>> Nicolas > >>>> > >>>> On 19/12/2018 11:44, Deepak Dixit wrote: > >>>>> I agree, > >>>>> > >>>>> We should create the next release (18.12) for framework and plugins. > >>>>> I'll check for issues, and if found will share here. > >>>>> Thanks & Regards > >>>>> -- > >>>>> Deepak Dixit > >>>>> > >>>>> > >>>>> > >>>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < > >>>>> [hidden email]> wrote: > >>>>> > >>>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : > >>>>>>> Hello, > >>>>>>> > >>>>>>> The time pass and the end year is near, maybe it's the time to > >>> prepare > >>>>>> next releases branches. > >>>>>>> Two questions : > >>>>>>> > >>>>>>> * Are you agree to create releases 18.12 branches for framework > and > >>>>>> plugin ? > >>>>>>> * Do you have some priority issue that you absolutely need > fbefore > >>>>>> create theses branches ? > >>>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I > >>>>>> believe/will/try to free some time for working on. > >>>>>>> Cheers, > >>>>>>> > >>>>>>> Nicolas > >>>>>>> > >>>>>> Hi Nicolas, All, > >>>>>> > >>>>>> As I think we agreed, we need to check all the blocker before > >>> releasing > >>>>>> (not freezing) . > >>>>>> > >>>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a > >>> possible > >>>>>> 18.12 branches (trunk+plugins) > >>>>>> > >>>>>> Thanks > >>>>>> > >>>>>> Jacques > >>>>>> > >>>>>> > > |
Re: Planning for the creation of new 18.12 branches
|
|
Thanks all for your comments,
I created release18.12 at r1849861 for framework and r1849862 for plugins. Rest to update website, prepare the release17.12 as stable and publish the 17.12.01 but sure on the next year :) Nicolas On 28/12/2018 11:10, Jacopo Cappellato wrote: > I agree that to proceed and create the branch now and then, over the next > few months, as a community we will refine our strategy and even decide on > which of the various branches we should focus on more. > > Jacopo > > > On Thu, Dec 27, 2018 at 1:59 PM Michael Brohl <[hidden email]> > wrote: > >> Yes, that would be a solution. >> >> I'm also fine if we would do a 19.x branch. For the future, we could aim >> to have a release more towards the middle of the year to avoid >> last-minute branching between Christmas and New Year ;-) >> >> The above would fit perfectly with this plan: >> >> 1. create an 18.12 branch and stabilize it >> >> 2. release 17.12 ;-) >> >> 3. create a 19.x (x = {6..10} branch with the Java Upgrade >> >> >> This would not break the yearly release branch and give us time for the >> Java 11 Update in 19.x. 19.x would be earlier next year so we get out of >> the end of year-hurries . >> >> Thanks, >> >> Michael >> >> >> Am 27.12.18 um 12:38 schrieb Taher Alkhateeb: >>> yeah I guess that would work too if it is okay to push a big change >>> into that branch >>> >>> >>> On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> >> wrote: >>>> We can create a branch and can backport java upgrade changes to 18.12 as >>>> well. >>>> Thanks & Regards >>>> -- >>>> Deepak Dixit >>>> >>>> >>>> >>>> On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb < >> [hidden email]> >>>> wrote: >>>> >>>>> It's okay whatever folks decide, but I think it would be nice if we >>>>> can upgrade Java for a new branch. >>>>> >>>>> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin < >> [hidden email]> >>>>> wrote: >>>>>> Four days before the end of year :) >>>>>> >>>>>> If no opposition, I will create it tomorrow >>>>>> >>>>>> Nicolas >>>>>> >>>>>> On 19/12/2018 11:44, Deepak Dixit wrote: >>>>>>> I agree, >>>>>>> >>>>>>> We should create the next release (18.12) for framework and plugins. >>>>>>> I'll check for issues, and if found will share here. >>>>>>> Thanks & Regards >>>>>>> -- >>>>>>> Deepak Dixit >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> The time pass and the end year is near, maybe it's the time to >>>>> prepare >>>>>>>> next releases branches. >>>>>>>>> Two questions : >>>>>>>>> >>>>>>>>> * Are you agree to create releases 18.12 branches for framework >> and >>>>>>>> plugin ? >>>>>>>>> * Do you have some priority issue that you absolutely need >> fbefore >>>>>>>> create theses branches ? >>>>>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >>>>>>>> believe/will/try to free some time for working on. >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Nicolas >>>>>>>>> >>>>>>>> Hi Nicolas, All, >>>>>>>> >>>>>>>> As I think we agreed, we need to check all the blocker before >>>>> releasing >>>>>>>> (not freezing) . >>>>>>>> >>>>>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a >>>>> possible >>>>>>>> 18.12 branches (trunk+plugins) >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> Jacques >>>>>>>> >>>>>>>> >> |
Re: Planning for the creation of new 18.12 branches
|
Administrator
|
I think Jiras would fit ;)
Jacques Le 28/12/2018 à 15:48, Nicolas Malin a écrit : > Thanks all for your comments, > > I created release18.12 at r1849861 for framework and r1849862 for plugins. > > Rest to update website, prepare the release17.12 as stable and publish the 17.12.01 but sure on the next year :) > > Nicolas > > On 28/12/2018 11:10, Jacopo Cappellato wrote: >> I agree that to proceed and create the branch now and then, over the next >> few months, as a community we will refine our strategy and even decide on >> which of the various branches we should focus on more. >> >> Jacopo >> >> >> On Thu, Dec 27, 2018 at 1:59 PM Michael Brohl <[hidden email]> >> wrote: >> >>> Yes, that would be a solution. >>> >>> I'm also fine if we would do a 19.x branch. For the future, we could aim >>> to have a release more towards the middle of the year to avoid >>> last-minute branching between Christmas and New Year ;-) >>> >>> The above would fit perfectly with this plan: >>> >>> 1. create an 18.12 branch and stabilize it >>> >>> 2. release 17.12 ;-) >>> >>> 3. create a 19.x (x = {6..10} branch with the Java Upgrade >>> >>> >>> This would not break the yearly release branch and give us time for the >>> Java 11 Update in 19.x. 19.x would be earlier next year so we get out of >>> the end of year-hurries . >>> >>> Thanks, >>> >>> Michael >>> >>> >>> Am 27.12.18 um 12:38 schrieb Taher Alkhateeb: >>>> yeah I guess that would work too if it is okay to push a big change >>>> into that branch >>>> >>>> >>>> On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> >>> wrote: >>>>> We can create a branch and can backport java upgrade changes to 18.12 as >>>>> well. >>>>> Thanks & Regards >>>>> -- >>>>> Deepak Dixit >>>>> >>>>> >>>>> >>>>> On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb < >>> [hidden email]> >>>>> wrote: >>>>> >>>>>> It's okay whatever folks decide, but I think it would be nice if we >>>>>> can upgrade Java for a new branch. >>>>>> >>>>>> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin < >>> [hidden email]> >>>>>> wrote: >>>>>>> Four days before the end of year :) >>>>>>> >>>>>>> If no opposition, I will create it tomorrow >>>>>>> >>>>>>> Nicolas >>>>>>> >>>>>>> On 19/12/2018 11:44, Deepak Dixit wrote: >>>>>>>> I agree, >>>>>>>> >>>>>>>> We should create the next release (18.12) for framework and plugins. >>>>>>>> I'll check for issues, and if found will share here. >>>>>>>> Thanks & Regards >>>>>>>> -- >>>>>>>> Deepak Dixit >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>>>>>>>>> Hello, >>>>>>>>>> >>>>>>>>>> The time pass and the end year is near, maybe it's the time to >>>>>> prepare >>>>>>>>> next releases branches. >>>>>>>>>> Two questions : >>>>>>>>>> >>>>>>>>>> * Are you agree to create releases 18.12 branches for framework >>> and >>>>>>>>> plugin ? >>>>>>>>>> * Do you have some priority issue that you absolutely need >>> fbefore >>>>>>>>> create theses branches ? >>>>>>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >>>>>>>>> believe/will/try to free some time for working on. >>>>>>>>>> Cheers, >>>>>>>>>> >>>>>>>>>> Nicolas >>>>>>>>>> >>>>>>>>> Hi Nicolas, All, >>>>>>>>> >>>>>>>>> As I think we agreed, we need to check all the blocker before >>>>>> releasing >>>>>>>>> (not freezing) . >>>>>>>>> >>>>>>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a >>>>>> possible >>>>>>>>> 18.12 branches (trunk+plugins) >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> Jacques >>>>>>>>> >>>>>>>>> >>> > |
Re: Planning for the creation of new 18.12 branches
|
|
Updated website with svn repository of the new release18.12 branch
at r1850150. Thanks and Regards, *Aditya Sharma* | Enterprise Software Engineer HotWax Commerce <http://www.hotwax.co/> by HotWax Systems <http://www.hotwaxsystems.com/> [image: https://www.linkedin.com/in/aditya-p-sharma/] <https://www.linkedin.com/in/aditya-p-sharma/> On Fri, Dec 28, 2018 at 8:41 PM Jacques Le Roux < [hidden email]> wrote: > I think Jiras would fit ;) > > Jacques > > Le 28/12/2018 à 15:48, Nicolas Malin a écrit : > > Thanks all for your comments, > > > > I created release18.12 at r1849861 for framework and r1849862 for > plugins. > > > > Rest to update website, prepare the release17.12 as stable and publish > the 17.12.01 but sure on the next year :) > > > > Nicolas > > > > On 28/12/2018 11:10, Jacopo Cappellato wrote: > >> I agree that to proceed and create the branch now and then, over the > next > >> few months, as a community we will refine our strategy and even decide > on > >> which of the various branches we should focus on more. > >> > >> Jacopo > >> > >> > >> On Thu, Dec 27, 2018 at 1:59 PM Michael Brohl <[hidden email] > > > >> wrote: > >> > >>> Yes, that would be a solution. > >>> > >>> I'm also fine if we would do a 19.x branch. For the future, we could > aim > >>> to have a release more towards the middle of the year to avoid > >>> last-minute branching between Christmas and New Year ;-) > >>> > >>> The above would fit perfectly with this plan: > >>> > >>> 1. create an 18.12 branch and stabilize it > >>> > >>> 2. release 17.12 ;-) > >>> > >>> 3. create a 19.x (x = {6..10} branch with the Java Upgrade > >>> > >>> > >>> This would not break the yearly release branch and give us time for the > >>> Java 11 Update in 19.x. 19.x would be earlier next year so we get out > of > >>> the end of year-hurries . > >>> > >>> Thanks, > >>> > >>> Michael > >>> > >>> > >>> Am 27.12.18 um 12:38 schrieb Taher Alkhateeb: > >>>> yeah I guess that would work too if it is okay to push a big change > >>>> into that branch > >>>> > >>>> > >>>> On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> > >>> wrote: > >>>>> We can create a branch and can backport java upgrade changes to > 18.12 as > >>>>> well. > >>>>> Thanks & Regards > >>>>> -- > >>>>> Deepak Dixit > >>>>> > >>>>> > >>>>> > >>>>> On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb < > >>> [hidden email]> > >>>>> wrote: > >>>>> > >>>>>> It's okay whatever folks decide, but I think it would be nice if we > >>>>>> can upgrade Java for a new branch. > >>>>>> > >>>>>> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin < > >>> [hidden email]> > >>>>>> wrote: > >>>>>>> Four days before the end of year :) > >>>>>>> > >>>>>>> If no opposition, I will create it tomorrow > >>>>>>> > >>>>>>> Nicolas > >>>>>>> > >>>>>>> On 19/12/2018 11:44, Deepak Dixit wrote: > >>>>>>>> I agree, > >>>>>>>> > >>>>>>>> We should create the next release (18.12) for framework and > plugins. > >>>>>>>> I'll check for issues, and if found will share here. > >>>>>>>> Thanks & Regards > >>>>>>>> -- > >>>>>>>> Deepak Dixit > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < > >>>>>>>> [hidden email]> wrote: > >>>>>>>> > >>>>>>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : > >>>>>>>>>> Hello, > >>>>>>>>>> > >>>>>>>>>> The time pass and the end year is near, maybe it's the time to > >>>>>> prepare > >>>>>>>>> next releases branches. > >>>>>>>>>> Two questions : > >>>>>>>>>> > >>>>>>>>>> * Are you agree to create releases 18.12 branches for > framework > >>> and > >>>>>>>>> plugin ? > >>>>>>>>>> * Do you have some priority issue that you absolutely need > >>> fbefore > >>>>>>>>> create theses branches ? > >>>>>>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I > >>>>>>>>> believe/will/try to free some time for working on. > >>>>>>>>>> Cheers, > >>>>>>>>>> > >>>>>>>>>> Nicolas > >>>>>>>>>> > >>>>>>>>> Hi Nicolas, All, > >>>>>>>>> > >>>>>>>>> As I think we agreed, we need to check all the blocker before > >>>>>> releasing > >>>>>>>>> (not freezing) . > >>>>>>>>> > >>>>>>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a > >>>>>> possible > >>>>>>>>> 18.12 branches (trunk+plugins) > >>>>>>>>> > >>>>>>>>> Thanks > >>>>>>>>> > >>>>>>>>> Jacques > >>>>>>>>> > >>>>>>>>> > >>> > > > |
Re: Planning for the creation of new 18.12 branches
|
|
:) thanks for you support
On 02/01/2019 06:21, Aditya Sharma wrote: > Updated website with svn repository of the new release18.12 branch > at r1850150. > > Thanks and Regards, > > *Aditya Sharma* | Enterprise Software Engineer > HotWax Commerce <http://www.hotwax.co/> by HotWax Systems > <http://www.hotwaxsystems.com/> > [image: https://www.linkedin.com/in/aditya-p-sharma/] > <https://www.linkedin.com/in/aditya-p-sharma/> > > > On Fri, Dec 28, 2018 at 8:41 PM Jacques Le Roux < > [hidden email]> wrote: > >> I think Jiras would fit ;) >> >> Jacques >> >> Le 28/12/2018 à 15:48, Nicolas Malin a écrit : >>> Thanks all for your comments, >>> >>> I created release18.12 at r1849861 for framework and r1849862 for >> plugins. >>> Rest to update website, prepare the release17.12 as stable and publish >> the 17.12.01 but sure on the next year :) >>> Nicolas >>> >>> On 28/12/2018 11:10, Jacopo Cappellato wrote: >>>> I agree that to proceed and create the branch now and then, over the >> next >>>> few months, as a community we will refine our strategy and even decide >> on >>>> which of the various branches we should focus on more. >>>> >>>> Jacopo >>>> >>>> >>>> On Thu, Dec 27, 2018 at 1:59 PM Michael Brohl <[hidden email] >>>> wrote: >>>> >>>>> Yes, that would be a solution. >>>>> >>>>> I'm also fine if we would do a 19.x branch. For the future, we could >> aim >>>>> to have a release more towards the middle of the year to avoid >>>>> last-minute branching between Christmas and New Year ;-) >>>>> >>>>> The above would fit perfectly with this plan: >>>>> >>>>> 1. create an 18.12 branch and stabilize it >>>>> >>>>> 2. release 17.12 ;-) >>>>> >>>>> 3. create a 19.x (x = {6..10} branch with the Java Upgrade >>>>> >>>>> >>>>> This would not break the yearly release branch and give us time for the >>>>> Java 11 Update in 19.x. 19.x would be earlier next year so we get out >> of >>>>> the end of year-hurries . >>>>> >>>>> Thanks, >>>>> >>>>> Michael >>>>> >>>>> >>>>> Am 27.12.18 um 12:38 schrieb Taher Alkhateeb: >>>>>> yeah I guess that would work too if it is okay to push a big change >>>>>> into that branch >>>>>> >>>>>> >>>>>> On Thu, Dec 27, 2018 at 1:44 PM Deepak Dixit <[hidden email]> >>>>> wrote: >>>>>>> We can create a branch and can backport java upgrade changes to >> 18.12 as >>>>>>> well. >>>>>>> Thanks & Regards >>>>>>> -- >>>>>>> Deepak Dixit >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Dec 27, 2018 at 3:21 PM Taher Alkhateeb < >>>>> [hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>>> It's okay whatever folks decide, but I think it would be nice if we >>>>>>>> can upgrade Java for a new branch. >>>>>>>> >>>>>>>> On Thu, Dec 27, 2018 at 12:05 PM Nicolas Malin < >>>>> [hidden email]> >>>>>>>> wrote: >>>>>>>>> Four days before the end of year :) >>>>>>>>> >>>>>>>>> If no opposition, I will create it tomorrow >>>>>>>>> >>>>>>>>> Nicolas >>>>>>>>> >>>>>>>>> On 19/12/2018 11:44, Deepak Dixit wrote: >>>>>>>>>> I agree, >>>>>>>>>> >>>>>>>>>> We should create the next release (18.12) for framework and >> plugins. >>>>>>>>>> I'll check for issues, and if found will share here. >>>>>>>>>> Thanks & Regards >>>>>>>>>> -- >>>>>>>>>> Deepak Dixit >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wed, Dec 19, 2018 at 3:38 PM Jacques Le Roux < >>>>>>>>>> [hidden email]> wrote: >>>>>>>>>> >>>>>>>>>>> Le 19/12/2018 à 10:14, Nicolas Malin a écrit : >>>>>>>>>>>> Hello, >>>>>>>>>>>> >>>>>>>>>>>> The time pass and the end year is near, maybe it's the time to >>>>>>>> prepare >>>>>>>>>>> next releases branches. >>>>>>>>>>>> Two questions : >>>>>>>>>>>> >>>>>>>>>>>> * Are you agree to create releases 18.12 branches for >> framework >>>>> and >>>>>>>>>>> plugin ? >>>>>>>>>>>> * Do you have some priority issue that you absolutely need >>>>> fbefore >>>>>>>>>>> create theses branches ? >>>>>>>>>>>> I see for my point of view OFBIZ-4361 and OFBIZ-10145. I >>>>>>>>>>> believe/will/try to free some time for working on. >>>>>>>>>>>> Cheers, >>>>>>>>>>>> >>>>>>>>>>>> Nicolas >>>>>>>>>>>> >>>>>>>>>>> Hi Nicolas, All, >>>>>>>>>>> >>>>>>>>>>> As I think we agreed, we need to check all the blocker before >>>>>>>> releasing >>>>>>>>>>> (not freezing) . >>>>>>>>>>> >>>>>>>>>>> So IMO OFBIZ-4361 and OFBIZ-10145 are not blocker for freezing a >>>>>>>> possible >>>>>>>>>>> 18.12 branches (trunk+plugins) >>>>>>>>>>> >>>>>>>>>>> Thanks >>>>>>>>>>> >>>>>>>>>>> Jacques >>>>>>>>>>> >>>>>>>>>>> |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |