Planning for the creation of the new 17.xx branch(es)
Locked
123
123
Re: Planning for the creation of the new 17.xx branch(es)
 
|
+1 to using Flat Grey theme as the default for the upcoming release for the reason given by Jacques
Was trying out on Visual Theme selection. Saw some rough edges on the OFBiz logo for Tomahawk & Flat Grey themes. Actual OFBiz logo seen in the application for Tomahawk & Flat Grey themes doesn't tally with the logos in the screenshots. Regards, James Yong On 2017-11-30 23:02, Jacques Le Roux <[hidden email]> wrote: > Should we keep Tomahawk as the default in trunk or change before freezing for R17.12? > > We know Tomahawk does not support RTL languages and we have a such users base using demos (I see it every time I use demos). > > There is still work to do for Rainbow[1], so maybe the old Flat Grey? > > Jacques > [1] http://markmail.org/message/nvgzvs4twqlwdoep > > > Le 30/11/2017 à 08:39, Nicolas Malin a écrit : > > Nice, the end of the years will be hardest :) > > > > Nicolas > > > > > > Le 29/11/2017 à 11:06, Jacopo Cappellato a écrit : > >> Ok, thanks for all the feedback guys! > >> Let's plan to create the branches before the end of the year. > >> > >> Jacopo > >> > >> > >> > >> On Tue, Nov 28, 2017 at 7:54 PM, Taher Alkhateeb <[hidden email] > >>> wrote: > >>> I think Rishi makes a good point. OFBIZ-9501 is a big task but it > >>> would be nice to create the release after the majority of data is > >>> moved. Rishi is already progressing in this task I think it might be > >>> worth waiting a little bit to have a clean datamodel component. > >>> > >>> On Tue, Nov 28, 2017 at 7:20 PM, Rishi Solanki <[hidden email]> > >>> wrote: > >>>> Jacopo, > >>>> Thanks for heads-up, I have OFBIZ-9501 with me, and I think it should be > >>>> part of new release. As the data movement will impact on ease of > >>> debugging > >>>> and maintenance. I'm planning to move most seed and seed-initial data by > >>>> this weekend. > >>>> > >>>> This should not impact the release date, because If community allow to > >>>> commit after release cut then we can migrate the changes to new release > >>>> after that as well. I'm saying this because I have already move few > >>>> components data to data model component like party, content and work > >>>> effort. So for the release the data consistency should be there at least > >>>> for seed and seed-initial data. > >>>> > >>>> If community not allowing to move data after release cut then I would say > >>>> to hold for few days, so that we can make the data pattern consistent. > >>> Also > >>>> may be others may have more tickets/bugs with them. > >>>> > >>>> Kind Regards, > >>>> > >>>> -- > >>>> Rishi Solanki > >>>> Sr Manager, Enterprise Software Development > >>>> HotWax Systems Pvt. Ltd. > >>>> Direct: +91-9893287847 > >>>> http://www.hotwaxsystems.com > >>>> www.hotwax.co > >>>> > >>>> On Tue, Nov 28, 2017 at 9:12 PM, Jacopo Cappellato <jacopo.cappellato@ > >>>> hotwaxsystems.com> wrote: > >>>> > >>>>> It's the end of November and we are close to the deadline for the > >>> creation > >>>>> of the 17.11 branches: how do we feel about it? > >>>>> Let me know if you want me to proceed, otherwise we will create the > >>>>> branches in December and they will be named 17.12 > >>>>> > >>>>> Regards, > >>>>> > >>>>> Jacopo > >>>>> > >>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < > >>> [hidden email]> > >>>>> wrote: > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> Agree to create the release 17.11 with a separate products framework & > >>>>>> plugins. > >>>>>> > >>>>>> It's woulb be nice to create this release one week after the next > >>>>>> community days :) > >>>>>> > >>>>>> Nicolas > >>>>>> > >>>>>> > >>>>>> > >>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : > >>>>>> > >>>>>>> Hi all, > >>>>>>> > >>>>>>> I think it is time to start thinking about if, when, how we should > >>>>> create > >>>>>>> the new release branch out of the trunk. Actually, for the first > >>> time, > >>>>> we > >>>>>>> should probably create two branches: one for the framework and one > >>> for > >>>>> the > >>>>>>> plugins. > >>>>>>> What do you think? > >>>>>>> > >>>>>>> In my opinion we could try to get all the changes we want to have in > >>> the > >>>>>>> trunk to be included in the branch by end of November: this means > >>> that > >>>>> the > >>>>>>> the creation of the branch could happen at the end of November. > >>>>>>> If this is the case then the names could be: > >>>>>>> release17.11-framework > >>>>>>> release17.11-plugins > >>>>>>> > >>>>>>> The above is for the release *branches* only, not for the actual > >>>>> releases. > >>>>>>> We could decide at a later point if the actual releases will be > >>> shipped > >>>>> as > >>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and > >>>>> "Apache > >>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz > >>>>>>> 17.11.01"). > >>>>>>> > >>>>>>> Best regards, > >>>>>>> > >>>>>>> Jacopo > >>>>>>> > >>>>>>> > > > > > > |
Re: Planning for the creation of the new 17.xx branch(es)
Administrator
|
Hi James,
Le 30/11/2017 à 16:30, James Yong a écrit : > +1 to using Flat Grey theme as the default for the upcoming release for the reason given by Jacques > > Was trying out on Visual Theme selection. > Saw some rough edges on the OFBiz logo for Tomahawk & Flat Grey themes. > Actual OFBiz logo seen in the application for Tomahawk & Flat Grey themes doesn't tally with the logos in the screenshots. Yes I have opened https://issues.apache.org/jira/browse/OFBIZ-9990 for that I'll see if I can fix it before switching (Anyway we need to use the new logo) I have also opened somehow related https://issues.apache.org/jira/browse/OFBIZ-9924 to "Make the general.SystemPropertyValue same than the related property in general properties" BTW, I'll maybe before fix http://markmail.org/message/nvgzvs4twqlwdoep and then, use rather Rainbow Saphir It's not totally clear in my mind at the moment, maybe those are not specific to Rainbow Saphir and we can use it as default WIP... Thanks Jacques > > Regards, > James Yong > > On 2017-11-30 23:02, Jacques Le Roux <[hidden email]> wrote: >> Should we keep Tomahawk as the default in trunk or change before freezing for R17.12? >> >> We know Tomahawk does not support RTL languages and we have a such users base using demos (I see it every time I use demos). >> >> There is still work to do for Rainbow[1], so maybe the old Flat Grey? >> >> Jacques >> [1] http://markmail.org/message/nvgzvs4twqlwdoep >> >> >> Le 30/11/2017 à 08:39, Nicolas Malin a écrit : >>> Nice, the end of the years will be hardest :) >>> >>> Nicolas >>> >>> >>> Le 29/11/2017 à 11:06, Jacopo Cappellato a écrit : >>>> Ok, thanks for all the feedback guys! >>>> Let's plan to create the branches before the end of the year. >>>> >>>> Jacopo >>>> >>>> >>>> >>>> On Tue, Nov 28, 2017 at 7:54 PM, Taher Alkhateeb <[hidden email] >>>>> wrote: >>>>> I think Rishi makes a good point. OFBIZ-9501 is a big task but it >>>>> would be nice to create the release after the majority of data is >>>>> moved. Rishi is already progressing in this task I think it might be >>>>> worth waiting a little bit to have a clean datamodel component. >>>>> >>>>> On Tue, Nov 28, 2017 at 7:20 PM, Rishi Solanki <[hidden email]> >>>>> wrote: >>>>>> Jacopo, >>>>>> Thanks for heads-up, I have OFBIZ-9501 with me, and I think it should be >>>>>> part of new release. As the data movement will impact on ease of >>>>> debugging >>>>>> and maintenance. I'm planning to move most seed and seed-initial data by >>>>>> this weekend. >>>>>> >>>>>> This should not impact the release date, because If community allow to >>>>>> commit after release cut then we can migrate the changes to new release >>>>>> after that as well. I'm saying this because I have already move few >>>>>> components data to data model component like party, content and work >>>>>> effort. So for the release the data consistency should be there at least >>>>>> for seed and seed-initial data. >>>>>> >>>>>> If community not allowing to move data after release cut then I would say >>>>>> to hold for few days, so that we can make the data pattern consistent. >>>>> Also >>>>>> may be others may have more tickets/bugs with them. >>>>>> >>>>>> Kind Regards, >>>>>> >>>>>> -- >>>>>> Rishi Solanki >>>>>> Sr Manager, Enterprise Software Development >>>>>> HotWax Systems Pvt. Ltd. >>>>>> Direct: +91-9893287847 >>>>>> http://www.hotwaxsystems.com >>>>>> www.hotwax.co >>>>>> >>>>>> On Tue, Nov 28, 2017 at 9:12 PM, Jacopo Cappellato <jacopo.cappellato@ >>>>>> hotwaxsystems.com> wrote: >>>>>> >>>>>>> It's the end of November and we are close to the deadline for the >>>>> creation >>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>> branches in December and they will be named 17.12 >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Jacopo >>>>>>> >>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>> [hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Agree to create the release 17.11 with a separate products framework & >>>>>>>> plugins. >>>>>>>> >>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>> community days :) >>>>>>>> >>>>>>>> Nicolas >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>> create >>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>> time, >>>>>>> we >>>>>>>>> should probably create two branches: one for the framework and one >>>>> for >>>>>>> the >>>>>>>>> plugins. >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> In my opinion we could try to get all the changes we want to have in >>>>> the >>>>>>>>> trunk to be included in the branch by end of November: this means >>>>> that >>>>>>> the >>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>> If this is the case then the names could be: >>>>>>>>> release17.11-framework >>>>>>>>> release17.11-plugins >>>>>>>>> >>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>> releases. >>>>>>>>> We could decide at a later point if the actual releases will be >>>>> shipped >>>>>>> as >>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>> "Apache >>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>> 17.11.01"). >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> >>>>>>>>> Jacopo >>>>>>>>> >>>>>>>>> >>> >> |
Re: Planning for the creation of the new 17.xx branch(es)
|
Administrator
|
This is done, the default theme in trunk is now Rainbow Saphir, see OFBIZ-9990/9924
Jacques Le 01/12/2017 à 11:08, Jacques Le Roux a écrit : > Hi James, > > Le 30/11/2017 à 16:30, James Yong a écrit : >> +1 to using Flat Grey theme as the default for the upcoming release for the reason given by Jacques >> >> Was trying out on Visual Theme selection. >> Saw some rough edges on the OFBiz logo for Tomahawk & Flat Grey themes. >> Actual OFBiz logo seen in the application for Tomahawk & Flat Grey themes doesn't tally with the logos in the screenshots. > Yes I have opened https://issues.apache.org/jira/browse/OFBIZ-9990 for that I'll see if I can fix it before switching (Anyway we need to use the new > logo) > > I have also opened somehow related https://issues.apache.org/jira/browse/OFBIZ-9924 to "Make the general.SystemPropertyValue same than the related > property in general properties" > > BTW, I'll maybe before fix http://markmail.org/message/nvgzvs4twqlwdoep and then, use rather Rainbow Saphir > It's not totally clear in my mind at the moment, maybe those are not specific to Rainbow Saphir and we can use it as default > > WIP... > > Thanks > > Jacques > >> >> Regards, >> James Yong >> >> On 2017-11-30 23:02, Jacques Le Roux <[hidden email]> wrote: >>> Should we keep Tomahawk as the default in trunk or change before freezing for R17.12? >>> >>> We know Tomahawk does not support RTL languages and we have a such users base using demos (I see it every time I use demos). >>> >>> There is still work to do for Rainbow[1], so maybe the old Flat Grey? >>> >>> Jacques >>> [1] http://markmail.org/message/nvgzvs4twqlwdoep >>> >>> >>> Le 30/11/2017 à 08:39, Nicolas Malin a écrit : >>>> Nice, the end of the years will be hardest :) >>>> >>>> Nicolas >>>> >>>> >>>> Le 29/11/2017 à 11:06, Jacopo Cappellato a écrit : >>>>> Ok, thanks for all the feedback guys! >>>>> Let's plan to create the branches before the end of the year. >>>>> >>>>> Jacopo >>>>> >>>>> >>>>> >>>>> On Tue, Nov 28, 2017 at 7:54 PM, Taher Alkhateeb <[hidden email] >>>>>> wrote: >>>>>> I think Rishi makes a good point. OFBIZ-9501 is a big task but it >>>>>> would be nice to create the release after the majority of data is >>>>>> moved. Rishi is already progressing in this task I think it might be >>>>>> worth waiting a little bit to have a clean datamodel component. >>>>>> >>>>>> On Tue, Nov 28, 2017 at 7:20 PM, Rishi Solanki <[hidden email]> >>>>>> wrote: >>>>>>> Jacopo, >>>>>>> Thanks for heads-up, I have OFBIZ-9501 with me, and I think it should be >>>>>>> part of new release. As the data movement will impact on ease of >>>>>> debugging >>>>>>> and maintenance. I'm planning to move most seed and seed-initial data by >>>>>>> this weekend. >>>>>>> >>>>>>> This should not impact the release date, because If community allow to >>>>>>> commit after release cut then we can migrate the changes to new release >>>>>>> after that as well. I'm saying this because I have already move few >>>>>>> components data to data model component like party, content and work >>>>>>> effort. So for the release the data consistency should be there at least >>>>>>> for seed and seed-initial data. >>>>>>> >>>>>>> If community not allowing to move data after release cut then I would say >>>>>>> to hold for few days, so that we can make the data pattern consistent. >>>>>> Also >>>>>>> may be others may have more tickets/bugs with them. >>>>>>> >>>>>>> Kind Regards, >>>>>>> >>>>>>> -- >>>>>>> Rishi Solanki >>>>>>> Sr Manager, Enterprise Software Development >>>>>>> HotWax Systems Pvt. Ltd. >>>>>>> Direct: +91-9893287847 >>>>>>> http://www.hotwaxsystems.com >>>>>>> www.hotwax.co >>>>>>> >>>>>>> On Tue, Nov 28, 2017 at 9:12 PM, Jacopo Cappellato <jacopo.cappellato@ >>>>>>> hotwaxsystems.com> wrote: >>>>>>> >>>>>>>> It's the end of November and we are close to the deadline for the >>>>>> creation >>>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>>> branches in December and they will be named 17.12 >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Jacopo >>>>>>>> >>>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>> [hidden email]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Agree to create the release 17.11 with a separate products framework & >>>>>>>>> plugins. >>>>>>>>> >>>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>>> community days :) >>>>>>>>> >>>>>>>>> Nicolas >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>> create >>>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>> time, >>>>>>>> we >>>>>>>>>> should probably create two branches: one for the framework and one >>>>>> for >>>>>>>> the >>>>>>>>>> plugins. >>>>>>>>>> What do you think? >>>>>>>>>> >>>>>>>>>> In my opinion we could try to get all the changes we want to have in >>>>>> the >>>>>>>>>> trunk to be included in the branch by end of November: this means >>>>>> that >>>>>>>> the >>>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>>> If this is the case then the names could be: >>>>>>>>>> release17.11-framework >>>>>>>>>> release17.11-plugins >>>>>>>>>> >>>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>> releases. >>>>>>>>>> We could decide at a later point if the actual releases will be >>>>>> shipped >>>>>>>> as >>>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>> "Apache >>>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>>> 17.11.01"). >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> >>>>>>>>>> Jacopo >>>>>>>>>> >>>>>>>>>> >>>> >>> > > |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
In reply to this post by Michael Brohl-3
Hi Jacopo, all,
I've just finished committing all those FindBugs and refactoring issues so no more show stoppers from my side to create the next release branch :-) Thanks, Michael Am 28.11.17 um 17:03 schrieb Michael Brohl: > Hi Jacopo, > > I am planning to do a bunch of FindBugs/refactoring commits in the > coming days/weeks, hopefully all of the currently open issues. > > It would be great if we can move the release to December. > > @all: any help on the FindBugs/refactoring issues by fellow committers > are greatly appreciated ;-) > > Thanks and regards, > > Michael > > > Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >> It's the end of November and we are close to the deadline for the >> creation >> of the 17.11 branches: how do we feel about it? >> Let me know if you want me to proceed, otherwise we will create the >> branches in December and they will be named 17.12 >> >> Regards, >> >> Jacopo >> >> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin >> <[hidden email]> >> wrote: >> >>> Hi, >>> >>> Agree to create the release 17.11 with a separate products framework & >>> plugins. >>> >>> It's woulb be nice to create this release one week after the next >>> community days :) >>> >>> Nicolas >>> >>> >>> >>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>> >>>> Hi all, >>>> >>>> I think it is time to start thinking about if, when, how we should >>>> create >>>> the new release branch out of the trunk. Actually, for the first >>>> time, we >>>> should probably create two branches: one for the framework and one >>>> for the >>>> plugins. >>>> What do you think? >>>> >>>> In my opinion we could try to get all the changes we want to have >>>> in the >>>> trunk to be included in the branch by end of November: this means >>>> that the >>>> the creation of the branch could happen at the end of November. >>>> If this is the case then the names could be: >>>> release17.11-framework >>>> release17.11-plugins >>>> >>>> The above is for the release *branches* only, not for the actual >>>> releases. >>>> We could decide at a later point if the actual releases will be >>>> shipped as >>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>> "Apache >>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>> 17.11.01"). >>>> >>>> Best regards, >>>> >>>> Jacopo >>>> >>>> > > |
smime.p7s (5K)
Re: Planning for the creation of the new 17.xx branch(es)
|
Administrator
|
There are 3 tasks that I'd like to be completed/committed before we create the R17 branch (or maybe a R18 one)
1. Tomcat SSO: OFBIZ-10047 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: http://markmail.org/message/nd7grfiyobjkfwae 1. For jQuery it's just a matter of completing, most it done 2. Tomcat SSO is complete, but Michael is reluctant because it has not been tested with a cluster. 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before continuing the discussion So I ask for a lazy consensus about them, what are your opinions (please look at the Jiras and ML I don't want to rehash all here)? Also "I have" ideas for 2018, based on ideas from 2014, but that's another topic :) Thanks Jacques Le 18/12/2017 à 16:19, Michael Brohl a écrit : > Hi Jacopo, all, > > I've just finished committing all those FindBugs and refactoring issues so no more show stoppers from my side to create the next release branch :-) > > Thanks, > > Michael > > > Am 28.11.17 um 17:03 schrieb Michael Brohl: >> Hi Jacopo, >> >> I am planning to do a bunch of FindBugs/refactoring commits in the coming days/weeks, hopefully all of the currently open issues. >> >> It would be great if we can move the release to December. >> >> @all: any help on the FindBugs/refactoring issues by fellow committers are greatly appreciated ;-) >> >> Thanks and regards, >> >> Michael >> >> >> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>> It's the end of November and we are close to the deadline for the creation >>> of the 17.11 branches: how do we feel about it? >>> Let me know if you want me to proceed, otherwise we will create the >>> branches in December and they will be named 17.12 >>> >>> Regards, >>> >>> Jacopo >>> >>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin <[hidden email]> >>> wrote: >>> >>>> Hi, >>>> >>>> Agree to create the release 17.11 with a separate products framework & >>>> plugins. >>>> >>>> It's woulb be nice to create this release one week after the next >>>> community days :) >>>> >>>> Nicolas >>>> >>>> >>>> >>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>> >>>>> Hi all, >>>>> >>>>> I think it is time to start thinking about if, when, how we should create >>>>> the new release branch out of the trunk. Actually, for the first time, we >>>>> should probably create two branches: one for the framework and one for the >>>>> plugins. >>>>> What do you think? >>>>> >>>>> In my opinion we could try to get all the changes we want to have in the >>>>> trunk to be included in the branch by end of November: this means that the >>>>> the creation of the branch could happen at the end of November. >>>>> If this is the case then the names could be: >>>>> release17.11-framework >>>>> release17.11-plugins >>>>> >>>>> The above is for the release *branches* only, not for the actual releases. >>>>> We could decide at a later point if the actual releases will be shipped as >>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and "Apache >>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>> 17.11.01"). >>>>> >>>>> Best regards, >>>>> >>>>> Jacopo >>>>> >>>>> >> >> > > |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux <
[hidden email]> wrote: > There are 3 tasks that I'd like to be completed/committed before we create > the R17 branch (or maybe a R18 one) > > 1. Tomcat SSO: OFBIZ-10047 > 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 > 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: > http://markmail.org/message/nd7grfiyobjkfwae > > 1. For jQuery it's just a matter of completing, most it done > 2. Tomcat SSO is complete, but Michael is reluctant because it has not > been tested with a cluster. > 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before > continuing the discussion > > So I ask for a lazy consensus about them, Could you please better elaborate about what the lazy consensus would achieve in these 3 cases? For #3, I think we can create the branch and then figure it out before issuing the first release oout of it (it will take weeks if not months). Jacopo > what are your opinions (please look at the Jiras and ML I don't want to > rehash all here)? > > Also "I have" ideas for 2018, based on ideas from 2014, but that's another > topic :) > > Thanks > > Jacques > > > > Le 18/12/2017 à 16:19, Michael Brohl a écrit : > >> Hi Jacopo, all, >> >> I've just finished committing all those FindBugs and refactoring issues >> so no more show stoppers from my side to create the next release branch :-) >> >> Thanks, >> >> Michael >> >> >> Am 28.11.17 um 17:03 schrieb Michael Brohl: >> >>> Hi Jacopo, >>> >>> I am planning to do a bunch of FindBugs/refactoring commits in the >>> coming days/weeks, hopefully all of the currently open issues. >>> >>> It would be great if we can move the release to December. >>> >>> @all: any help on the FindBugs/refactoring issues by fellow committers >>> are greatly appreciated ;-) >>> >>> Thanks and regards, >>> >>> Michael >>> >>> >>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>> >>>> It's the end of November and we are close to the deadline for the >>>> creation >>>> of the 17.11 branches: how do we feel about it? >>>> Let me know if you want me to proceed, otherwise we will create the >>>> branches in December and they will be named 17.12 >>>> >>>> Regards, >>>> >>>> Jacopo >>>> >>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>> [hidden email]> >>>> wrote: >>>> >>>> Hi, >>>>> >>>>> Agree to create the release 17.11 with a separate products framework & >>>>> plugins. >>>>> >>>>> It's woulb be nice to create this release one week after the next >>>>> community days :) >>>>> >>>>> Nicolas >>>>> >>>>> >>>>> >>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>> >>>>> Hi all, >>>>>> >>>>>> I think it is time to start thinking about if, when, how we should >>>>>> create >>>>>> the new release branch out of the trunk. Actually, for the first >>>>>> time, we >>>>>> should probably create two branches: one for the framework and one >>>>>> for the >>>>>> plugins. >>>>>> What do you think? >>>>>> >>>>>> In my opinion we could try to get all the changes we want to have in >>>>>> the >>>>>> trunk to be included in the branch by end of November: this means >>>>>> that the >>>>>> the creation of the branch could happen at the end of November. >>>>>> If this is the case then the names could be: >>>>>> release17.11-framework >>>>>> release17.11-plugins >>>>>> >>>>>> The above is for the release *branches* only, not for the actual >>>>>> releases. >>>>>> We could decide at a later point if the actual releases will be >>>>>> shipped as >>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>> "Apache >>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>> 17.11.01"). >>>>>> >>>>>> Best regards, >>>>>> >>>>>> Jacopo >>>>>> >>>>>> >>>>>> >>> >>> >> >> > |
Re: Planning for the creation of the new 17.xx branch(es)
|
Administrator
|
Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit :
> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < > [hidden email]> wrote: > >> There are 3 tasks that I'd like to be completed/committed before we create >> the R17 branch (or maybe a R18 one) >> >> 1. Tomcat SSO: OFBIZ-10047 >> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >> http://markmail.org/message/nd7grfiyobjkfwae >> >> 1. For jQuery it's just a matter of completing, most it done >> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >> been tested with a cluster. >> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >> continuing the discussion >> >> So I ask for a lazy consensus about them, > > Could you please better elaborate about what the lazy consensus would > achieve in these 3 cases? > For #3, I think we can create the branch and then figure it out before > issuing the first release oout of it (it will take weeks if not months). > > Jacopo 1. Should we commit it to have it in R17? 2. Should we wait for this task to be complete before freezing R17? 3. Your proposition is OK with me Jacques > > >> what are your opinions (please look at the Jiras and ML I don't want to >> rehash all here)? >> >> Also "I have" ideas for 2018, based on ideas from 2014, but that's another >> topic :) >> >> Thanks >> >> Jacques >> >> >> >> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >> >>> Hi Jacopo, all, >>> >>> I've just finished committing all those FindBugs and refactoring issues >>> so no more show stoppers from my side to create the next release branch :-) >>> >>> Thanks, >>> >>> Michael >>> >>> >>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>> >>>> Hi Jacopo, >>>> >>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>> coming days/weeks, hopefully all of the currently open issues. >>>> >>>> It would be great if we can move the release to December. >>>> >>>> @all: any help on the FindBugs/refactoring issues by fellow committers >>>> are greatly appreciated ;-) >>>> >>>> Thanks and regards, >>>> >>>> Michael >>>> >>>> >>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>> >>>>> It's the end of November and we are close to the deadline for the >>>>> creation >>>>> of the 17.11 branches: how do we feel about it? >>>>> Let me know if you want me to proceed, otherwise we will create the >>>>> branches in December and they will be named 17.12 >>>>> >>>>> Regards, >>>>> >>>>> Jacopo >>>>> >>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>> [hidden email]> >>>>> wrote: >>>>> >>>>> Hi, >>>>>> Agree to create the release 17.11 with a separate products framework & >>>>>> plugins. >>>>>> >>>>>> It's woulb be nice to create this release one week after the next >>>>>> community days :) >>>>>> >>>>>> Nicolas >>>>>> >>>>>> >>>>>> >>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>> >>>>>> Hi all, >>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>> create >>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>> time, we >>>>>>> should probably create two branches: one for the framework and one >>>>>>> for the >>>>>>> plugins. >>>>>>> What do you think? >>>>>>> >>>>>>> In my opinion we could try to get all the changes we want to have in >>>>>>> the >>>>>>> trunk to be included in the branch by end of November: this means >>>>>>> that the >>>>>>> the creation of the branch could happen at the end of November. >>>>>>> If this is the case then the names could be: >>>>>>> release17.11-framework >>>>>>> release17.11-plugins >>>>>>> >>>>>>> The above is for the release *branches* only, not for the actual >>>>>>> releases. >>>>>>> We could decide at a later point if the actual releases will be >>>>>>> shipped as >>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>> "Apache >>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>> 17.11.01"). >>>>>>> >>>>>>> Best regards, >>>>>>> >>>>>>> Jacopo >>>>>>> >>>>>>> >>>>>>> >>>> >>> |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
My preference is to create the branch now and discuss on a case by case the
backporting of any additional feature. Jacopo On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < [hidden email]> wrote: > Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : > >> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >> [hidden email]> wrote: >> >> There are 3 tasks that I'd like to be completed/committed before we create >>> the R17 branch (or maybe a R18 one) >>> >>> 1. Tomcat SSO: OFBIZ-10047 >>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>> http://markmail.org/message/nd7grfiyobjkfwae >>> >>> 1. For jQuery it's just a matter of completing, most it done >>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>> been tested with a cluster. >>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>> continuing the discussion >>> >>> So I ask for a lazy consensus about them, >>> >> >> Could you please better elaborate about what the lazy consensus would >> achieve in these 3 cases? >> For #3, I think we can create the branch and then figure it out before >> issuing the first release oout of it (it will take weeks if not months). >> >> Jacopo >> > Mmm, I thought it was clear enough. Let me try to summarise then: > > 1. Should we commit it to have it in R17? > 2. Should we wait for this task to be complete before freezing R17? > 3. Your proposition is OK with me > > Jacques > > > >> >> what are your opinions (please look at the Jiras and ML I don't want to >>> rehash all here)? >>> >>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>> another >>> topic :) >>> >>> Thanks >>> >>> Jacques >>> >>> >>> >>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>> >>> Hi Jacopo, all, >>>> >>>> I've just finished committing all those FindBugs and refactoring issues >>>> so no more show stoppers from my side to create the next release branch >>>> :-) >>>> >>>> Thanks, >>>> >>>> Michael >>>> >>>> >>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>> >>>> Hi Jacopo, >>>>> >>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>> coming days/weeks, hopefully all of the currently open issues. >>>>> >>>>> It would be great if we can move the release to December. >>>>> >>>>> @all: any help on the FindBugs/refactoring issues by fellow committers >>>>> are greatly appreciated ;-) >>>>> >>>>> Thanks and regards, >>>>> >>>>> Michael >>>>> >>>>> >>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>> >>>>> It's the end of November and we are close to the deadline for the >>>>>> creation >>>>>> of the 17.11 branches: how do we feel about it? >>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>> branches in December and they will be named 17.12 >>>>>> >>>>>> Regards, >>>>>> >>>>>> Jacopo >>>>>> >>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>> [hidden email]> >>>>>> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>> & >>>>>>> plugins. >>>>>>> >>>>>>> It's woulb be nice to create this release one week after the next >>>>>>> community days :) >>>>>>> >>>>>>> Nicolas >>>>>>> >>>>>>> >>>>>>> >>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>> create >>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>> time, we >>>>>>>> should probably create two branches: one for the framework and one >>>>>>>> for the >>>>>>>> plugins. >>>>>>>> What do you think? >>>>>>>> >>>>>>>> In my opinion we could try to get all the changes we want to have in >>>>>>>> the >>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>> that the >>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>> If this is the case then the names could be: >>>>>>>> release17.11-framework >>>>>>>> release17.11-plugins >>>>>>>> >>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>> releases. >>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>> shipped as >>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>> "Apache >>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>> 17.11.01"). >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Jacopo >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>> >>>> > |
|
+1
On Dec 19, 2017 1:31 PM, "Jacopo Cappellato" < [hidden email]> wrote: My preference is to create the branch now and discuss on a case by case the backporting of any additional feature. Jacopo On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < [hidden email]> wrote: > Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : > >> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >> [hidden email]> wrote: >> >> There are 3 tasks that I'd like to be completed/committed before we create >>> the R17 branch (or maybe a R18 one) >>> >>> 1. Tomcat SSO: OFBIZ-10047 >>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>> http://markmail.org/message/nd7grfiyobjkfwae >>> >>> 1. For jQuery it's just a matter of completing, most it done >>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>> been tested with a cluster. >>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>> continuing the discussion >>> >>> So I ask for a lazy consensus about them, >>> >> >> Could you please better elaborate about what the lazy consensus would >> achieve in these 3 cases? >> For #3, I think we can create the branch and then figure it out before >> issuing the first release oout of it (it will take weeks if not months). >> >> Jacopo >> > Mmm, I thought it was clear enough. Let me try to summarise then: > > 1. Should we commit it to have it in R17? > 2. Should we wait for this task to be complete before freezing R17? > 3. Your proposition is OK with me > > Jacques > > > >> >> what are your opinions (please look at the Jiras and ML I don't want to >>> rehash all here)? >>> >>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>> another >>> topic :) >>> >>> Thanks >>> >>> Jacques >>> >>> >>> >>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>> >>> Hi Jacopo, all, >>>> >>>> I've just finished committing all those FindBugs and refactoring issues >>>> so no more show stoppers from my side to create the next release branch >>>> :-) >>>> >>>> Thanks, >>>> >>>> Michael >>>> >>>> >>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>> >>>> Hi Jacopo, >>>>> >>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>> coming days/weeks, hopefully all of the currently open issues. >>>>> >>>>> It would be great if we can move the release to December. >>>>> >>>>> @all: any help on the FindBugs/refactoring issues by fellow committers >>>>> are greatly appreciated ;-) >>>>> >>>>> Thanks and regards, >>>>> >>>>> Michael >>>>> >>>>> >>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>> >>>>> It's the end of November and we are close to the deadline for the >>>>>> creation >>>>>> of the 17.11 branches: how do we feel about it? >>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>> branches in December and they will be named 17.12 >>>>>> >>>>>> Regards, >>>>>> >>>>>> Jacopo >>>>>> >>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>> [hidden email]> >>>>>> wrote: >>>>>> >>>>>> Hi, >>>>>> >>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>> & >>>>>>> plugins. >>>>>>> >>>>>>> It's woulb be nice to create this release one week after the next >>>>>>> community days :) >>>>>>> >>>>>>> Nicolas >>>>>>> >>>>>>> >>>>>>> >>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>> create >>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>> time, we >>>>>>>> should probably create two branches: one for the framework and one >>>>>>>> for the >>>>>>>> plugins. >>>>>>>> What do you think? >>>>>>>> >>>>>>>> In my opinion we could try to get all the changes we want to have >>>>>>>> the >>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>> that the >>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>> If this is the case then the names could be: >>>>>>>> release17.11-framework >>>>>>>> release17.11-plugins >>>>>>>> >>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>> releases. >>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>> shipped as >>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>> "Apache >>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>> 17.11.01"). >>>>>>>> >>>>>>>> Best regards, >>>>>>>> >>>>>>>> Jacopo >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>> >>>> > |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
In reply to this post by Jacopo Cappellato-5
+1
Regards, Michael Am 19.12.17 um 11:31 schrieb Jacopo Cappellato: > My preference is to create the branch now and discuss on a case by case the > backporting of any additional feature. > > Jacopo > > On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < > [hidden email]> wrote: > >> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >> >>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>> There are 3 tasks that I'd like to be completed/committed before we create >>>> the R17 branch (or maybe a R18 one) >>>> >>>> 1. Tomcat SSO: OFBIZ-10047 >>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>> http://markmail.org/message/nd7grfiyobjkfwae >>>> >>>> 1. For jQuery it's just a matter of completing, most it done >>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>>> been tested with a cluster. >>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>> continuing the discussion >>>> >>>> So I ask for a lazy consensus about them, >>>> >>> Could you please better elaborate about what the lazy consensus would >>> achieve in these 3 cases? >>> For #3, I think we can create the branch and then figure it out before >>> issuing the first release oout of it (it will take weeks if not months). >>> >>> Jacopo >>> >> Mmm, I thought it was clear enough. Let me try to summarise then: >> >> 1. Should we commit it to have it in R17? >> 2. Should we wait for this task to be complete before freezing R17? >> 3. Your proposition is OK with me >> >> Jacques >> >> >> >>> what are your opinions (please look at the Jiras and ML I don't want to >>>> rehash all here)? >>>> >>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>> another >>>> topic :) >>>> >>>> Thanks >>>> >>>> Jacques >>>> >>>> >>>> >>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>> >>>> Hi Jacopo, all, >>>>> I've just finished committing all those FindBugs and refactoring issues >>>>> so no more show stoppers from my side to create the next release branch >>>>> :-) >>>>> >>>>> Thanks, >>>>> >>>>> Michael >>>>> >>>>> >>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>> >>>>> Hi Jacopo, >>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>> >>>>>> It would be great if we can move the release to December. >>>>>> >>>>>> @all: any help on the FindBugs/refactoring issues by fellow committers >>>>>> are greatly appreciated ;-) >>>>>> >>>>>> Thanks and regards, >>>>>> >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>> >>>>>> It's the end of November and we are close to the deadline for the >>>>>>> creation >>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>> branches in December and they will be named 17.12 >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Jacopo >>>>>>> >>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>> [hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>>> & >>>>>>>> plugins. >>>>>>>> >>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>> community days :) >>>>>>>> >>>>>>>> Nicolas >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>>> create >>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>> time, we >>>>>>>>> should probably create two branches: one for the framework and one >>>>>>>>> for the >>>>>>>>> plugins. >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> In my opinion we could try to get all the changes we want to have in >>>>>>>>> the >>>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>>> that the >>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>> If this is the case then the names could be: >>>>>>>>> release17.11-framework >>>>>>>>> release17.11-plugins >>>>>>>>> >>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>> releases. >>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>> shipped as >>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>>> "Apache >>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>> 17.11.01"). >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> >>>>>>>>> Jacopo >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
In reply to this post by Jacopo Cappellato-5
sound good +1
Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : > My preference is to create the branch now and discuss on a case by case the > backporting of any additional feature. > > Jacopo > > On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < > [hidden email]> wrote: > >> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >> >>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>> There are 3 tasks that I'd like to be completed/committed before we create >>>> the R17 branch (or maybe a R18 one) >>>> >>>> 1. Tomcat SSO: OFBIZ-10047 >>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>> http://markmail.org/message/nd7grfiyobjkfwae >>>> >>>> 1. For jQuery it's just a matter of completing, most it done >>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>>> been tested with a cluster. >>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>> continuing the discussion >>>> >>>> So I ask for a lazy consensus about them, >>>> >>> Could you please better elaborate about what the lazy consensus would >>> achieve in these 3 cases? >>> For #3, I think we can create the branch and then figure it out before >>> issuing the first release oout of it (it will take weeks if not months). >>> >>> Jacopo >>> >> Mmm, I thought it was clear enough. Let me try to summarise then: >> >> 1. Should we commit it to have it in R17? >> 2. Should we wait for this task to be complete before freezing R17? >> 3. Your proposition is OK with me >> >> Jacques >> >> >> >>> what are your opinions (please look at the Jiras and ML I don't want to >>>> rehash all here)? >>>> >>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>> another >>>> topic :) >>>> >>>> Thanks >>>> >>>> Jacques >>>> >>>> >>>> >>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>> >>>> Hi Jacopo, all, >>>>> I've just finished committing all those FindBugs and refactoring issues >>>>> so no more show stoppers from my side to create the next release branch >>>>> :-) >>>>> >>>>> Thanks, >>>>> >>>>> Michael >>>>> >>>>> >>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>> >>>>> Hi Jacopo, >>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>> >>>>>> It would be great if we can move the release to December. >>>>>> >>>>>> @all: any help on the FindBugs/refactoring issues by fellow committers >>>>>> are greatly appreciated ;-) >>>>>> >>>>>> Thanks and regards, >>>>>> >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>> >>>>>> It's the end of November and we are close to the deadline for the >>>>>>> creation >>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>> branches in December and they will be named 17.12 >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Jacopo >>>>>>> >>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>> [hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>>> & >>>>>>>> plugins. >>>>>>>> >>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>> community days :) >>>>>>>> >>>>>>>> Nicolas >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>>> create >>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>> time, we >>>>>>>>> should probably create two branches: one for the framework and one >>>>>>>>> for the >>>>>>>>> plugins. >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> In my opinion we could try to get all the changes we want to have in >>>>>>>>> the >>>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>>> that the >>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>> If this is the case then the names could be: >>>>>>>>> release17.11-framework >>>>>>>>> release17.11-plugins >>>>>>>>> >>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>> releases. >>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>> shipped as >>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>>> "Apache >>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>> 17.11.01"). >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> >>>>>>>>> Jacopo >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
+1
I would like to backport ecommerce UX improvement work and remaining jquery upgrade work. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Tue, Dec 19, 2017 at 4:12 PM, Nicolas Malin <[hidden email]> wrote: > sound good +1 > > > > Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : > >> My preference is to create the branch now and discuss on a case by case >> the >> backporting of any additional feature. >> >> Jacopo >> >> On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < >> [hidden email]> wrote: >> >> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >>> >>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>>> [hidden email]> wrote: >>>> >>>> There are 3 tasks that I'd like to be completed/committed before we >>>> create >>>> >>>>> the R17 branch (or maybe a R18 one) >>>>> >>>>> 1. Tomcat SSO: OFBIZ-10047 >>>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>>> http://markmail.org/message/nd7grfiyobjkfwae >>>>> >>>>> 1. For jQuery it's just a matter of completing, most it done >>>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>>>> been tested with a cluster. >>>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>>> continuing the discussion >>>>> >>>>> So I ask for a lazy consensus about them, >>>>> >>>>> Could you please better elaborate about what the lazy consensus would >>>> achieve in these 3 cases? >>>> For #3, I think we can create the branch and then figure it out before >>>> issuing the first release oout of it (it will take weeks if not months). >>>> >>>> Jacopo >>>> >>>> Mmm, I thought it was clear enough. Let me try to summarise then: >>> >>> 1. Should we commit it to have it in R17? >>> 2. Should we wait for this task to be complete before freezing R17? >>> 3. Your proposition is OK with me >>> >>> Jacques >>> >>> >>> >>> what are your opinions (please look at the Jiras and ML I don't want to >>>> >>>>> rehash all here)? >>>>> >>>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>>> another >>>>> topic :) >>>>> >>>>> Thanks >>>>> >>>>> Jacques >>>>> >>>>> >>>>> >>>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>>> >>>>> Hi Jacopo, all, >>>>> >>>>>> I've just finished committing all those FindBugs and refactoring >>>>>> issues >>>>>> so no more show stoppers from my side to create the next release >>>>>> branch >>>>>> :-) >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>>> >>>>>> Hi Jacopo, >>>>>> >>>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>>> >>>>>>> It would be great if we can move the release to December. >>>>>>> >>>>>>> @all: any help on the FindBugs/refactoring issues by fellow >>>>>>> committers >>>>>>> are greatly appreciated ;-) >>>>>>> >>>>>>> Thanks and regards, >>>>>>> >>>>>>> Michael >>>>>>> >>>>>>> >>>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>>> >>>>>>> It's the end of November and we are close to the deadline for the >>>>>>> >>>>>>>> creation >>>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>>> branches in December and they will be named 17.12 >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Jacopo >>>>>>>> >>>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>>> [hidden email]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>>>> & >>>>>>>>> plugins. >>>>>>>>> >>>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>>> community days :) >>>>>>>>> >>>>>>>>> Nicolas >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>>> >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>>>> create >>>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>>> time, we >>>>>>>>>> should probably create two branches: one for the framework and one >>>>>>>>>> for the >>>>>>>>>> plugins. >>>>>>>>>> What do you think? >>>>>>>>>> >>>>>>>>>> In my opinion we could try to get all the changes we want to have >>>>>>>>>> in >>>>>>>>>> the >>>>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>>>> that the >>>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>>> If this is the case then the names could be: >>>>>>>>>> release17.11-framework >>>>>>>>>> release17.11-plugins >>>>>>>>>> >>>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>>> releases. >>>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>>> shipped as >>>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>>>> "Apache >>>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>>> 17.11.01"). >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> >>>>>>>>>> Jacopo >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> > |
Re: Planning for the creation of the new 17.xx branch(es)
|
Administrator
|
+1
Jacques Le 19/12/2017 à 11:53, Deepak Dixit a écrit : > +1 > > I would like to backport ecommerce UX improvement work and remaining jquery > upgrade work. > > Thanks & Regards > -- > Deepak Dixit > www.hotwaxsystems.com > www.hotwax.co > > On Tue, Dec 19, 2017 at 4:12 PM, Nicolas Malin <[hidden email]> > wrote: > >> sound good +1 >> >> >> >> Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : >> >>> My preference is to create the branch now and discuss on a case by case >>> the >>> backporting of any additional feature. >>> >>> Jacopo >>> >>> On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >>>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>>>> [hidden email]> wrote: >>>>> >>>>> There are 3 tasks that I'd like to be completed/committed before we >>>>> create >>>>> >>>>>> the R17 branch (or maybe a R18 one) >>>>>> >>>>>> 1. Tomcat SSO: OFBIZ-10047 >>>>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>>>> http://markmail.org/message/nd7grfiyobjkfwae >>>>>> >>>>>> 1. For jQuery it's just a matter of completing, most it done >>>>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>>>>> been tested with a cluster. >>>>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>>>> continuing the discussion >>>>>> >>>>>> So I ask for a lazy consensus about them, >>>>>> >>>>>> Could you please better elaborate about what the lazy consensus would >>>>> achieve in these 3 cases? >>>>> For #3, I think we can create the branch and then figure it out before >>>>> issuing the first release oout of it (it will take weeks if not months). >>>>> >>>>> Jacopo >>>>> >>>>> Mmm, I thought it was clear enough. Let me try to summarise then: >>>> 1. Should we commit it to have it in R17? >>>> 2. Should we wait for this task to be complete before freezing R17? >>>> 3. Your proposition is OK with me >>>> >>>> Jacques >>>> >>>> >>>> >>>> what are your opinions (please look at the Jiras and ML I don't want to >>>>>> rehash all here)? >>>>>> >>>>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>>>> another >>>>>> topic :) >>>>>> >>>>>> Thanks >>>>>> >>>>>> Jacques >>>>>> >>>>>> >>>>>> >>>>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>>>> >>>>>> Hi Jacopo, all, >>>>>> >>>>>>> I've just finished committing all those FindBugs and refactoring >>>>>>> issues >>>>>>> so no more show stoppers from my side to create the next release >>>>>>> branch >>>>>>> :-) >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Michael >>>>>>> >>>>>>> >>>>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>>>> >>>>>>> Hi Jacopo, >>>>>>> >>>>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>>>> >>>>>>>> It would be great if we can move the release to December. >>>>>>>> >>>>>>>> @all: any help on the FindBugs/refactoring issues by fellow >>>>>>>> committers >>>>>>>> are greatly appreciated ;-) >>>>>>>> >>>>>>>> Thanks and regards, >>>>>>>> >>>>>>>> Michael >>>>>>>> >>>>>>>> >>>>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>>>> >>>>>>>> It's the end of November and we are close to the deadline for the >>>>>>>> >>>>>>>>> creation >>>>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>>>> branches in December and they will be named 17.12 >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Jacopo >>>>>>>>> >>>>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>>>> [hidden email]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>>>>> & >>>>>>>>>> plugins. >>>>>>>>>> >>>>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>>>> community days :) >>>>>>>>>> >>>>>>>>>> Nicolas >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>>>>> create >>>>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>>>> time, we >>>>>>>>>>> should probably create two branches: one for the framework and one >>>>>>>>>>> for the >>>>>>>>>>> plugins. >>>>>>>>>>> What do you think? >>>>>>>>>>> >>>>>>>>>>> In my opinion we could try to get all the changes we want to have >>>>>>>>>>> in >>>>>>>>>>> the >>>>>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>>>>> that the >>>>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>>>> If this is the case then the names could be: >>>>>>>>>>> release17.11-framework >>>>>>>>>>> release17.11-plugins >>>>>>>>>>> >>>>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>>>> releases. >>>>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>>>> shipped as >>>>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>>>>> "Apache >>>>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>>>> 17.11.01"). >>>>>>>>>>> >>>>>>>>>>> Best regards, >>>>>>>>>>> >>>>>>>>>>> Jacopo >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> |
Re: Planning for the creation of the new 17.xx branch(es)
|
Administrator
|
In reply to this post by Jacopo Cappellato-5
Now that we seems to agree about discussing each case, what about mine? :)
Jacques Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : > My preference is to create the branch now and discuss on a case by case the > backporting of any additional feature. > > Jacopo > > On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < > [hidden email]> wrote: > >> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >> >>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>> There are 3 tasks that I'd like to be completed/committed before we create >>>> the R17 branch (or maybe a R18 one) >>>> >>>> 1. Tomcat SSO: OFBIZ-10047 >>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>> http://markmail.org/message/nd7grfiyobjkfwae >>>> >>>> 1. For jQuery it's just a matter of completing, most it done >>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>>> been tested with a cluster. >>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>> continuing the discussion >>>> >>>> So I ask for a lazy consensus about them, >>>> >>> Could you please better elaborate about what the lazy consensus would >>> achieve in these 3 cases? >>> For #3, I think we can create the branch and then figure it out before >>> issuing the first release oout of it (it will take weeks if not months). >>> >>> Jacopo >>> >> Mmm, I thought it was clear enough. Let me try to summarise then: >> >> 1. Should we commit it to have it in R17? >> 2. Should we wait for this task to be complete before freezing R17? >> 3. Your proposition is OK with me >> >> Jacques >> >> >> >>> what are your opinions (please look at the Jiras and ML I don't want to >>>> rehash all here)? >>>> >>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>> another >>>> topic :) >>>> >>>> Thanks >>>> >>>> Jacques >>>> >>>> >>>> >>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>> >>>> Hi Jacopo, all, >>>>> I've just finished committing all those FindBugs and refactoring issues >>>>> so no more show stoppers from my side to create the next release branch >>>>> :-) >>>>> >>>>> Thanks, >>>>> >>>>> Michael >>>>> >>>>> >>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>> >>>>> Hi Jacopo, >>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>> >>>>>> It would be great if we can move the release to December. >>>>>> >>>>>> @all: any help on the FindBugs/refactoring issues by fellow committers >>>>>> are greatly appreciated ;-) >>>>>> >>>>>> Thanks and regards, >>>>>> >>>>>> Michael >>>>>> >>>>>> >>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>> >>>>>> It's the end of November and we are close to the deadline for the >>>>>>> creation >>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>> branches in December and they will be named 17.12 >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Jacopo >>>>>>> >>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>> [hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>>> & >>>>>>>> plugins. >>>>>>>> >>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>> community days :) >>>>>>>> >>>>>>>> Nicolas >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>>> create >>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>> time, we >>>>>>>>> should probably create two branches: one for the framework and one >>>>>>>>> for the >>>>>>>>> plugins. >>>>>>>>> What do you think? >>>>>>>>> >>>>>>>>> In my opinion we could try to get all the changes we want to have in >>>>>>>>> the >>>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>>> that the >>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>> If this is the case then the names could be: >>>>>>>>> release17.11-framework >>>>>>>>> release17.11-plugins >>>>>>>>> >>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>> releases. >>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>> shipped as >>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>>> "Apache >>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>> 17.11.01"). >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> >>>>>>>>> Jacopo >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
In reply to this post by Jacques Le Roux
As per the discussion on http://markmail.org/message/4mrffmp5j2mujv3w and
OFBIZ-9902. <https://issues.apache.org/jira/browse/OFBIZ-9902> We have prepared markdown file with the data model changes from OFBiz R9 to 17. It will help users/developers to identify data model changes that come with the release. I think this can be the part of our next release. Patch is available on the ticket, kindly have a look and let me know if any changes required. Thanks and Regards, *Aditya Sharma* | Enterprise Software Engineer HotWax Commerce <http://www.hotwax.co/> by HotWax Systems <http://www.hotwaxsystems.com/> <https://www.linkedin.com/in/aditya-sharma-78291810a/> On Tue, Dec 19, 2017 at 6:09 PM, Jacques Le Roux < [hidden email]> wrote: > +1 > > Jacques > > > > Le 19/12/2017 à 11:53, Deepak Dixit a écrit : > >> +1 >> >> I would like to backport ecommerce UX improvement work and remaining >> jquery >> upgrade work. >> >> Thanks & Regards >> -- >> Deepak Dixit >> www.hotwaxsystems.com >> www.hotwax.co >> >> On Tue, Dec 19, 2017 at 4:12 PM, Nicolas Malin <[hidden email]> >> wrote: >> >> sound good +1 >>> >>> >>> >>> Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : >>> >>> My preference is to create the branch now and discuss on a case by case >>>> the >>>> backporting of any additional feature. >>>> >>>> Jacopo >>>> >>>> On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < >>>> [hidden email]> wrote: >>>> >>>> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >>>> >>>>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>>>> >>>>>> [hidden email]> wrote: >>>>>> >>>>>> There are 3 tasks that I'd like to be completed/committed before we >>>>>> create >>>>>> >>>>>> the R17 branch (or maybe a R18 one) >>>>>>> >>>>>>> 1. Tomcat SSO: OFBIZ-10047 >>>>>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>>>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>>>>> http://markmail.org/message/nd7grfiyobjkfwae >>>>>>> >>>>>>> 1. For jQuery it's just a matter of completing, most it done >>>>>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has >>>>>>> not >>>>>>> been tested with a cluster. >>>>>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>>>>> continuing the discussion >>>>>>> >>>>>>> So I ask for a lazy consensus about them, >>>>>>> >>>>>>> Could you please better elaborate about what the lazy consensus would >>>>>>> >>>>>> achieve in these 3 cases? >>>>>> For #3, I think we can create the branch and then figure it out before >>>>>> issuing the first release oout of it (it will take weeks if not >>>>>> months). >>>>>> >>>>>> Jacopo >>>>>> >>>>>> Mmm, I thought it was clear enough. Let me try to summarise then: >>>>>> >>>>> 1. Should we commit it to have it in R17? >>>>> 2. Should we wait for this task to be complete before freezing R17? >>>>> 3. Your proposition is OK with me >>>>> >>>>> Jacques >>>>> >>>>> >>>>> >>>>> what are your opinions (please look at the Jiras and ML I don't want to >>>>> >>>>>> rehash all here)? >>>>>>> >>>>>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>>>>> another >>>>>>> topic :) >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Jacques >>>>>>> >>>>>>> >>>>>>> >>>>>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>>>>> >>>>>>> Hi Jacopo, all, >>>>>>> >>>>>>> I've just finished committing all those FindBugs and refactoring >>>>>>>> issues >>>>>>>> so no more show stoppers from my side to create the next release >>>>>>>> branch >>>>>>>> :-) >>>>>>>> >>>>>>>> Thanks, >>>>>>>> >>>>>>>> Michael >>>>>>>> >>>>>>>> >>>>>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>>>>> >>>>>>>> Hi Jacopo, >>>>>>>> >>>>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>>>>> >>>>>>>>> It would be great if we can move the release to December. >>>>>>>>> >>>>>>>>> @all: any help on the FindBugs/refactoring issues by fellow >>>>>>>>> committers >>>>>>>>> are greatly appreciated ;-) >>>>>>>>> >>>>>>>>> Thanks and regards, >>>>>>>>> >>>>>>>>> Michael >>>>>>>>> >>>>>>>>> >>>>>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>>>>> >>>>>>>>> It's the end of November and we are close to the deadline for the >>>>>>>>> >>>>>>>>> creation >>>>>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>>>>> Let me know if you want me to proceed, otherwise we will create >>>>>>>>>> the >>>>>>>>>> branches in December and they will be named 17.12 >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Jacopo >>>>>>>>>> >>>>>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>>>>> [hidden email]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Agree to create the release 17.11 with a separate products >>>>>>>>>> framework >>>>>>>>>> >>>>>>>>>>> & >>>>>>>>>>> plugins. >>>>>>>>>>> >>>>>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>>>>> community days :) >>>>>>>>>>> >>>>>>>>>>> Nicolas >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>>>>> >>>>>>>>>>> Hi all, >>>>>>>>>>> >>>>>>>>>>> I think it is time to start thinking about if, when, how we >>>>>>>>>>> should >>>>>>>>>>> >>>>>>>>>>>> create >>>>>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>>>>> time, we >>>>>>>>>>>> should probably create two branches: one for the framework and >>>>>>>>>>>> one >>>>>>>>>>>> for the >>>>>>>>>>>> plugins. >>>>>>>>>>>> What do you think? >>>>>>>>>>>> >>>>>>>>>>>> In my opinion we could try to get all the changes we want to >>>>>>>>>>>> have >>>>>>>>>>>> in >>>>>>>>>>>> the >>>>>>>>>>>> trunk to be included in the branch by end of November: this >>>>>>>>>>>> means >>>>>>>>>>>> that the >>>>>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>>>>> If this is the case then the names could be: >>>>>>>>>>>> release17.11-framework >>>>>>>>>>>> release17.11-plugins >>>>>>>>>>>> >>>>>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>>>>> releases. >>>>>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>>>>> shipped as >>>>>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" >>>>>>>>>>>> and >>>>>>>>>>>> "Apache >>>>>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>>>>> 17.11.01"). >>>>>>>>>>>> >>>>>>>>>>>> Best regards, >>>>>>>>>>>> >>>>>>>>>>>> Jacopo >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> > |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
In reply to this post by Jacques Le Roux
Hi All,
Can we commit the code for Tomcat SSO (OFBIZ-10047) but switch the feature off? Once the Cluster SSO is ready, we can backport to the 17.xx branch with Tomcat SSO turned on. Regards, James On 2017-12-19 20:43, Jacques Le Roux <[hidden email]> wrote: > Now that we seems to agree about discussing each case, what about mine? :) > > Jacques > > > Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : > > My preference is to create the branch now and discuss on a case by case the > > backporting of any additional feature. > > > > Jacopo > > > > On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < > > [hidden email]> wrote: > > > >> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : > >> > >>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < > >>> [hidden email]> wrote: > >>> > >>> There are 3 tasks that I'd like to be completed/committed before we create > >>>> the R17 branch (or maybe a R18 one) > >>>> > >>>> 1. Tomcat SSO: OFBIZ-10047 > >>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 > >>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: > >>>> http://markmail.org/message/nd7grfiyobjkfwae > >>>> > >>>> 1. For jQuery it's just a matter of completing, most it done > >>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not > >>>> been tested with a cluster. > >>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before > >>>> continuing the discussion > >>>> > >>>> So I ask for a lazy consensus about them, > >>>> > >>> Could you please better elaborate about what the lazy consensus would > >>> achieve in these 3 cases? > >>> For #3, I think we can create the branch and then figure it out before > >>> issuing the first release oout of it (it will take weeks if not months). > >>> > >>> Jacopo > >>> > >> Mmm, I thought it was clear enough. Let me try to summarise then: > >> > >> 1. Should we commit it to have it in R17? > >> 2. Should we wait for this task to be complete before freezing R17? > >> 3. Your proposition is OK with me > >> > >> Jacques > >> > >> > >> > >>> what are your opinions (please look at the Jiras and ML I don't want to > >>>> rehash all here)? > >>>> > >>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's > >>>> another > >>>> topic :) > >>>> > >>>> Thanks > >>>> > >>>> Jacques > >>>> > >>>> > >>>> > >>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : > >>>> > >>>> Hi Jacopo, all, > >>>>> I've just finished committing all those FindBugs and refactoring issues > >>>>> so no more show stoppers from my side to create the next release branch > >>>>> :-) > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Michael > >>>>> > >>>>> > >>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: > >>>>> > >>>>> Hi Jacopo, > >>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the > >>>>>> coming days/weeks, hopefully all of the currently open issues. > >>>>>> > >>>>>> It would be great if we can move the release to December. > >>>>>> > >>>>>> @all: any help on the FindBugs/refactoring issues by fellow committers > >>>>>> are greatly appreciated ;-) > >>>>>> > >>>>>> Thanks and regards, > >>>>>> > >>>>>> Michael > >>>>>> > >>>>>> > >>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: > >>>>>> > >>>>>> It's the end of November and we are close to the deadline for the > >>>>>>> creation > >>>>>>> of the 17.11 branches: how do we feel about it? > >>>>>>> Let me know if you want me to proceed, otherwise we will create the > >>>>>>> branches in December and they will be named 17.12 > >>>>>>> > >>>>>>> Regards, > >>>>>>> > >>>>>>> Jacopo > >>>>>>> > >>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < > >>>>>>> [hidden email]> > >>>>>>> wrote: > >>>>>>> > >>>>>>> Hi, > >>>>>>> > >>>>>>>> Agree to create the release 17.11 with a separate products framework > >>>>>>>> & > >>>>>>>> plugins. > >>>>>>>> > >>>>>>>> It's woulb be nice to create this release one week after the next > >>>>>>>> community days :) > >>>>>>>> > >>>>>>>> Nicolas > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : > >>>>>>>> > >>>>>>>> Hi all, > >>>>>>>> > >>>>>>>>> I think it is time to start thinking about if, when, how we should > >>>>>>>>> create > >>>>>>>>> the new release branch out of the trunk. Actually, for the first > >>>>>>>>> time, we > >>>>>>>>> should probably create two branches: one for the framework and one > >>>>>>>>> for the > >>>>>>>>> plugins. > >>>>>>>>> What do you think? > >>>>>>>>> > >>>>>>>>> In my opinion we could try to get all the changes we want to have in > >>>>>>>>> the > >>>>>>>>> trunk to be included in the branch by end of November: this means > >>>>>>>>> that the > >>>>>>>>> the creation of the branch could happen at the end of November. > >>>>>>>>> If this is the case then the names could be: > >>>>>>>>> release17.11-framework > >>>>>>>>> release17.11-plugins > >>>>>>>>> > >>>>>>>>> The above is for the release *branches* only, not for the actual > >>>>>>>>> releases. > >>>>>>>>> We could decide at a later point if the actual releases will be > >>>>>>>>> shipped as > >>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and > >>>>>>>>> "Apache > >>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz > >>>>>>>>> 17.11.01"). > >>>>>>>>> > >>>>>>>>> Best regards, > >>>>>>>>> > >>>>>>>>> Jacopo > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > > |
Re: Planning for the creation of the new 17.xx branch(es)
|
Administrator
|
That's a good idea James.
Will you handle the cluster implementation and test? BTW it's the only point among those I raised which remains after the suggestion of backporting features on case by case in R17 Jacques Le 20/12/2017 à 06:32, James Yong a écrit : > Hi All, > > Can we commit the code for Tomcat SSO (OFBIZ-10047) but switch the feature off? > Once the Cluster SSO is ready, we can backport to the 17.xx branch with Tomcat SSO turned on. > > Regards, > James > > > On 2017-12-19 20:43, Jacques Le Roux <[hidden email]> wrote: >> Now that we seems to agree about discussing each case, what about mine? :) >> >> Jacques >> >> >> Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : >>> My preference is to create the branch now and discuss on a case by case the >>> backporting of any additional feature. >>> >>> Jacopo >>> >>> On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < >>> [hidden email]> wrote: >>> >>>> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >>>> >>>>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>>>> [hidden email]> wrote: >>>>> >>>>> There are 3 tasks that I'd like to be completed/committed before we create >>>>>> the R17 branch (or maybe a R18 one) >>>>>> >>>>>> 1. Tomcat SSO: OFBIZ-10047 >>>>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>>>> http://markmail.org/message/nd7grfiyobjkfwae >>>>>> >>>>>> 1. For jQuery it's just a matter of completing, most it done >>>>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not >>>>>> been tested with a cluster. >>>>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>>>> continuing the discussion >>>>>> >>>>>> So I ask for a lazy consensus about them, >>>>>> >>>>> Could you please better elaborate about what the lazy consensus would >>>>> achieve in these 3 cases? >>>>> For #3, I think we can create the branch and then figure it out before >>>>> issuing the first release oout of it (it will take weeks if not months). >>>>> >>>>> Jacopo >>>>> >>>> Mmm, I thought it was clear enough. Let me try to summarise then: >>>> >>>> 1. Should we commit it to have it in R17? >>>> 2. Should we wait for this task to be complete before freezing R17? >>>> 3. Your proposition is OK with me >>>> >>>> Jacques >>>> >>>> >>>> >>>>> what are your opinions (please look at the Jiras and ML I don't want to >>>>>> rehash all here)? >>>>>> >>>>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>>>> another >>>>>> topic :) >>>>>> >>>>>> Thanks >>>>>> >>>>>> Jacques >>>>>> >>>>>> >>>>>> >>>>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>>>> >>>>>> Hi Jacopo, all, >>>>>>> I've just finished committing all those FindBugs and refactoring issues >>>>>>> so no more show stoppers from my side to create the next release branch >>>>>>> :-) >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> Michael >>>>>>> >>>>>>> >>>>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>>>> >>>>>>> Hi Jacopo, >>>>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>>>> >>>>>>>> It would be great if we can move the release to December. >>>>>>>> >>>>>>>> @all: any help on the FindBugs/refactoring issues by fellow committers >>>>>>>> are greatly appreciated ;-) >>>>>>>> >>>>>>>> Thanks and regards, >>>>>>>> >>>>>>>> Michael >>>>>>>> >>>>>>>> >>>>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>>>> >>>>>>>> It's the end of November and we are close to the deadline for the >>>>>>>>> creation >>>>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>>>> Let me know if you want me to proceed, otherwise we will create the >>>>>>>>> branches in December and they will be named 17.12 >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Jacopo >>>>>>>>> >>>>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>>>> [hidden email]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hi, >>>>>>>>> >>>>>>>>>> Agree to create the release 17.11 with a separate products framework >>>>>>>>>> & >>>>>>>>>> plugins. >>>>>>>>>> >>>>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>>>> community days :) >>>>>>>>>> >>>>>>>>>> Nicolas >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>>> I think it is time to start thinking about if, when, how we should >>>>>>>>>>> create >>>>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>>>> time, we >>>>>>>>>>> should probably create two branches: one for the framework and one >>>>>>>>>>> for the >>>>>>>>>>> plugins. >>>>>>>>>>> What do you think? >>>>>>>>>>> >>>>>>>>>>> In my opinion we could try to get all the changes we want to have in >>>>>>>>>>> the >>>>>>>>>>> trunk to be included in the branch by end of November: this means >>>>>>>>>>> that the >>>>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>>>> If this is the case then the names could be: >>>>>>>>>>> release17.11-framework >>>>>>>>>>> release17.11-plugins >>>>>>>>>>> >>>>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>>>> releases. >>>>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>>>> shipped as >>>>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and >>>>>>>>>>> "Apache >>>>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>>>> 17.11.01"). >>>>>>>>>>> >>>>>>>>>>> Best regards, >>>>>>>>>>> >>>>>>>>>>> Jacopo >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >> |
Re: Planning for the creation of the new 17.xx branch(es)
|
Administrator
|
In reply to this post by Aditya Sharma
Done
Jacques Le 19/12/2017 à 13:53, Aditya Sharma a écrit : > As per the discussion on http://markmail.org/message/4mrffmp5j2mujv3w and > OFBIZ-9902. <https://issues.apache.org/jira/browse/OFBIZ-9902> > We have prepared markdown file with the data model changes from OFBiz R9 to > 17. > It will help users/developers to identify data model changes that come with > the release. > > I think this can be the part of our next release. Patch is available on the > ticket, kindly have a look and let me know if any changes required. > > > > Thanks and Regards, > > *Aditya Sharma* | Enterprise Software Engineer > HotWax Commerce <http://www.hotwax.co/> by HotWax Systems > <http://www.hotwaxsystems.com/> > > <https://www.linkedin.com/in/aditya-sharma-78291810a/> > > On Tue, Dec 19, 2017 at 6:09 PM, Jacques Le Roux < > [hidden email]> wrote: > >> +1 >> >> Jacques >> >> >> >> Le 19/12/2017 à 11:53, Deepak Dixit a écrit : >> >>> +1 >>> >>> I would like to backport ecommerce UX improvement work and remaining >>> jquery >>> upgrade work. >>> >>> Thanks & Regards >>> -- >>> Deepak Dixit >>> www.hotwaxsystems.com >>> www.hotwax.co >>> >>> On Tue, Dec 19, 2017 at 4:12 PM, Nicolas Malin <[hidden email]> >>> wrote: >>> >>> sound good +1 >>>> >>>> >>>> Le 19/12/2017 à 11:31, Jacopo Cappellato a écrit : >>>> >>>> My preference is to create the branch now and discuss on a case by case >>>>> the >>>>> backporting of any additional feature. >>>>> >>>>> Jacopo >>>>> >>>>> On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < >>>>> [hidden email]> wrote: >>>>> >>>>> Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : >>>>> >>>>>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >>>>>> >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> There are 3 tasks that I'd like to be completed/committed before we >>>>>>> create >>>>>>> >>>>>>> the R17 branch (or maybe a R18 one) >>>>>>>> 1. Tomcat SSO: OFBIZ-10047 >>>>>>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 >>>>>>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: >>>>>>>> http://markmail.org/message/nd7grfiyobjkfwae >>>>>>>> >>>>>>>> 1. For jQuery it's just a matter of completing, most it done >>>>>>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has >>>>>>>> not >>>>>>>> been tested with a cluster. >>>>>>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before >>>>>>>> continuing the discussion >>>>>>>> >>>>>>>> So I ask for a lazy consensus about them, >>>>>>>> >>>>>>>> Could you please better elaborate about what the lazy consensus would >>>>>>>> >>>>>>> achieve in these 3 cases? >>>>>>> For #3, I think we can create the branch and then figure it out before >>>>>>> issuing the first release oout of it (it will take weeks if not >>>>>>> months). >>>>>>> >>>>>>> Jacopo >>>>>>> >>>>>>> Mmm, I thought it was clear enough. Let me try to summarise then: >>>>>>> >>>>>> 1. Should we commit it to have it in R17? >>>>>> 2. Should we wait for this task to be complete before freezing R17? >>>>>> 3. Your proposition is OK with me >>>>>> >>>>>> Jacques >>>>>> >>>>>> >>>>>> >>>>>> what are your opinions (please look at the Jiras and ML I don't want to >>>>>> >>>>>>> rehash all here)? >>>>>>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's >>>>>>>> another >>>>>>>> topic :) >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> Jacques >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le 18/12/2017 à 16:19, Michael Brohl a écrit : >>>>>>>> >>>>>>>> Hi Jacopo, all, >>>>>>>> >>>>>>>> I've just finished committing all those FindBugs and refactoring >>>>>>>>> issues >>>>>>>>> so no more show stoppers from my side to create the next release >>>>>>>>> branch >>>>>>>>> :-) >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> >>>>>>>>> Michael >>>>>>>>> >>>>>>>>> >>>>>>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: >>>>>>>>> >>>>>>>>> Hi Jacopo, >>>>>>>>> >>>>>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the >>>>>>>>>> coming days/weeks, hopefully all of the currently open issues. >>>>>>>>>> >>>>>>>>>> It would be great if we can move the release to December. >>>>>>>>>> >>>>>>>>>> @all: any help on the FindBugs/refactoring issues by fellow >>>>>>>>>> committers >>>>>>>>>> are greatly appreciated ;-) >>>>>>>>>> >>>>>>>>>> Thanks and regards, >>>>>>>>>> >>>>>>>>>> Michael >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: >>>>>>>>>> >>>>>>>>>> It's the end of November and we are close to the deadline for the >>>>>>>>>> >>>>>>>>>> creation >>>>>>>>>>> of the 17.11 branches: how do we feel about it? >>>>>>>>>>> Let me know if you want me to proceed, otherwise we will create >>>>>>>>>>> the >>>>>>>>>>> branches in December and they will be named 17.12 >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> Jacopo >>>>>>>>>>> >>>>>>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < >>>>>>>>>>> [hidden email]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> Agree to create the release 17.11 with a separate products >>>>>>>>>>> framework >>>>>>>>>>> >>>>>>>>>>>> & >>>>>>>>>>>> plugins. >>>>>>>>>>>> >>>>>>>>>>>> It's woulb be nice to create this release one week after the next >>>>>>>>>>>> community days :) >>>>>>>>>>>> >>>>>>>>>>>> Nicolas >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit : >>>>>>>>>>>> >>>>>>>>>>>> Hi all, >>>>>>>>>>>> >>>>>>>>>>>> I think it is time to start thinking about if, when, how we >>>>>>>>>>>> should >>>>>>>>>>>> >>>>>>>>>>>>> create >>>>>>>>>>>>> the new release branch out of the trunk. Actually, for the first >>>>>>>>>>>>> time, we >>>>>>>>>>>>> should probably create two branches: one for the framework and >>>>>>>>>>>>> one >>>>>>>>>>>>> for the >>>>>>>>>>>>> plugins. >>>>>>>>>>>>> What do you think? >>>>>>>>>>>>> >>>>>>>>>>>>> In my opinion we could try to get all the changes we want to >>>>>>>>>>>>> have >>>>>>>>>>>>> in >>>>>>>>>>>>> the >>>>>>>>>>>>> trunk to be included in the branch by end of November: this >>>>>>>>>>>>> means >>>>>>>>>>>>> that the >>>>>>>>>>>>> the creation of the branch could happen at the end of November. >>>>>>>>>>>>> If this is the case then the names could be: >>>>>>>>>>>>> release17.11-framework >>>>>>>>>>>>> release17.11-plugins >>>>>>>>>>>>> >>>>>>>>>>>>> The above is for the release *branches* only, not for the actual >>>>>>>>>>>>> releases. >>>>>>>>>>>>> We could decide at a later point if the actual releases will be >>>>>>>>>>>>> shipped as >>>>>>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" >>>>>>>>>>>>> and >>>>>>>>>>>>> "Apache >>>>>>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz >>>>>>>>>>>>> 17.11.01"). >>>>>>>>>>>>> >>>>>>>>>>>>> Best regards, >>>>>>>>>>>>> >>>>>>>>>>>>> Jacopo >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
In reply to this post by Jacques Le Roux
Hi Jacques,
I can help with the cluster implementation and test. Need to plan a time for it. Will be a new JIRA issue as you mentioned. Regards, James Yong On 2017-12-20 16:16, Jacques Le Roux <[hidden email]> wrote: > That's a good idea James. > > Will you handle the cluster implementation and test? > > BTW it's the only point among those I raised which remains after the suggestion of backporting features on case by case in R17 > > Jacques > > > Le 20/12/2017 à 06:32, James Yong a écrit : > > Hi All, > > > > Can we commit the code for Tomcat SSO (OFBIZ-10047) but switch the feature off? > > Once the Cluster SSO is ready, we can backport to the 17.xx branch with Tomcat SSO turned on. > > > > Regards, > > James > > > > > > On 2017-12-19 20:43, Jacques Le Roux <[hidden email]> wrote: > >> Now that we seems to agree about discussing each case, what about mine? :) > >> > >> Jacques > >> > >> > >> Le 19/12/2017 à11:31, Jacopo Cappellato a écrità: > >>> My preference is to create the branch now and discuss on a case by case the > >>> backporting of any additional feature. > >>> > >>> Jacopo > >>> > >>> On Tue, Dec 19, 2017 at 9:42 AM, Jacques Le Roux < > >>> [hidden email]> wrote: > >>> > >>>> Le 18/12/2017 à18:02, Jacopo Cappellato a écrit : > >>>> > >>>>> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < > >>>>> [hidden email]> wrote: > >>>>> > >>>>> There are 3 tasks that I'd like to be completed/committed before we create > >>>>>> the R17 branch (or maybe a R18 one) > >>>>>> > >>>>>> 1. Tomcat SSO: OFBIZ-10047 > >>>>>> 2. Upgrade jQuery 1.11.0 to jQuery 3.2.1: OFBIZ-9978 > >>>>>> 3. The thread "OFBiz & gradlew-wrapper.jar" in this ML: > >>>>>> http://markmail.org/message/nd7grfiyobjkfwae > >>>>>> > >>>>>> 1. For jQuery it's just a matter of completing, most it done > >>>>>> 2. Tomcat SSO is complete, but Michael is reluctant because it has not > >>>>>> been tested with a cluster. > >>>>>> 3. For OFBiz & gradlew-wrapper.jar please refer to LEGAL-288 before > >>>>>> continuing the discussion > >>>>>> > >>>>>> So I ask for a lazy consensus about them, > >>>>>> > >>>>> Could you please better elaborate about what the lazy consensus would > >>>>> achieve in these 3 cases? > >>>>> For #3, I think we can create the branch and then figure it out before > >>>>> issuing the first release oout of it (it will take weeks if not months). > >>>>> > >>>>> Jacopo > >>>>> > >>>> Mmm, I thought it was clear enough. Let me try to summarise then: > >>>> > >>>> 1. Should we commit it to have it in R17? > >>>> 2. Should we wait for this task to be complete before freezing R17? > >>>> 3. Your proposition is OK with me > >>>> > >>>> Jacques > >>>> > >>>> > >>>> > >>>>> what are your opinions (please look at the Jiras and ML I don't want to > >>>>>> rehash all here)? > >>>>>> > >>>>>> Also "I have" ideas for 2018, based on ideas from 2014, but that's > >>>>>> another > >>>>>> topic :) > >>>>>> > >>>>>> Thanks > >>>>>> > >>>>>> Jacques > >>>>>> > >>>>>> > >>>>>> > >>>>>> Le 18/12/2017 à16:19, Michael Brohl a écrit : > >>>>>> > >>>>>> Hi Jacopo, all, > >>>>>>> I've just finished committing all those FindBugs and refactoring issues > >>>>>>> so no more show stoppers from my side to create the next release branch > >>>>>>> :-) > >>>>>>> > >>>>>>> Thanks, > >>>>>>> > >>>>>>> Michael > >>>>>>> > >>>>>>> > >>>>>>> Am 28.11.17 um 17:03 schrieb Michael Brohl: > >>>>>>> > >>>>>>> Hi Jacopo, > >>>>>>>> I am planning to do a bunch of FindBugs/refactoring commits in the > >>>>>>>> coming days/weeks, hopefully all of the currently open issues. > >>>>>>>> > >>>>>>>> It would be great if we can move the release to December. > >>>>>>>> > >>>>>>>> @all: any help on the FindBugs/refactoring issues by fellow committers > >>>>>>>> are greatly appreciated ;-) > >>>>>>>> > >>>>>>>> Thanks and regards, > >>>>>>>> > >>>>>>>> Michael > >>>>>>>> > >>>>>>>> > >>>>>>>> Am 28.11.17 um 16:42 schrieb Jacopo Cappellato: > >>>>>>>> > >>>>>>>> It's the end of November and we are close to the deadline for the > >>>>>>>>> creation > >>>>>>>>> of the 17.11 branches: how do we feel about it? > >>>>>>>>> Let me know if you want me to proceed, otherwise we will create the > >>>>>>>>> branches in December and they will be named 17.12 > >>>>>>>>> > >>>>>>>>> Regards, > >>>>>>>>> > >>>>>>>>> Jacopo > >>>>>>>>> > >>>>>>>>> On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin < > >>>>>>>>> [hidden email]> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>>> Agree to create the release 17.11 with a separate products framework > >>>>>>>>>> & > >>>>>>>>>> plugins. > >>>>>>>>>> > >>>>>>>>>> It's woulb be nice to create this release one week after the next > >>>>>>>>>> community days :) > >>>>>>>>>> > >>>>>>>>>> Nicolas > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> Le 10/10/2017 à09:35, Jacopo Cappellato a écrit : > >>>>>>>>>> > >>>>>>>>>> Hi all, > >>>>>>>>>> > >>>>>>>>>>> I think it is time to start thinking about if, when, how we should > >>>>>>>>>>> create > >>>>>>>>>>> the new release branch out of the trunk. Actually, for the first > >>>>>>>>>>> time, we > >>>>>>>>>>> should probably create two branches: one for the framework and one > >>>>>>>>>>> for the > >>>>>>>>>>> plugins. > >>>>>>>>>>> What do you think? > >>>>>>>>>>> > >>>>>>>>>>> In my opinion we could try to get all the changes we want to have in > >>>>>>>>>>> the > >>>>>>>>>>> trunk to be included in the branch by end of November: this means > >>>>>>>>>>> that the > >>>>>>>>>>> the creation of the branch could happen at the end of November. > >>>>>>>>>>> If this is the case then the names could be: > >>>>>>>>>>> release17.11-framework > >>>>>>>>>>> release17.11-plugins > >>>>>>>>>>> > >>>>>>>>>>> The above is for the release *branches* only, not for the actual > >>>>>>>>>>> releases. > >>>>>>>>>>> We could decide at a later point if the actual releases will be > >>>>>>>>>>> shipped as > >>>>>>>>>>> two separate products (e.g. "Apache OFBiz Framework 17.11.01" and > >>>>>>>>>>> "Apache > >>>>>>>>>>> OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz > >>>>>>>>>>> 17.11.01"). > >>>>>>>>>>> > >>>>>>>>>>> Best regards, > >>>>>>>>>>> > >>>>>>>>>>> Jacopo > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> > >> > > |
Re: Planning for the creation of the new 17.xx branch(es)
|
|
We have now the release branches:
https://svn.apache.org/repos/asf/ofbiz/ofbiz-framework/branches/release17.12/ https://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/branches/release17.12/ Please review them and make any adjustments required; we should also update our website: https://ofbiz.apache.org/source-repositories.html ... the community has now a new toy to play with :-) Jacopo |
«
Return to OFBiz - Dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |