+1 On Dec 19, 2017 1:31 PM, "Jacopo Cappellato" < jacopo.cappell...@hotwaxsystems.com> 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 < jacques.le.r...@les7arts.com> wrote: > Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : > >> On Mon, Dec 18, 2017 at 5:28 PM, Jacques Le Roux < >> jacques.le.r...@les7arts.com> 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 < >>>>>> nicolas.ma...@nereide.fr> >>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>> >>>> >
