Re: Planning for the creation of the new 17.xx branch(es)

Thanks for feedback Deepak, Done Jacques Le 02/01/2018 à 05:30, Deepak Dixit a écrit : Thanks Jacques, looks good to me. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Sat, Dec 30, 2017 at 7:07 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: BTW I

Re: Planning for the creation of the new 17.xx branch(es)

Thanks Jacques, looks good to me. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Sat, Dec 30, 2017 at 7:07 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > BTW I notice that so fat we used ofbiz.16.11 so maybe we could continue to > follow this convention

Re: Planning for the creation of the new 17.xx branch(es)

BTW I notice that so fat we used ofbiz.16.11 so maybe we could continue to follow this convention and have ofbiz.17.12 and ofbiz.17.12-plugins If nobody is against I'll do so in few days Jacques Le 30/12/2017 à 12:29, Jacques Le Roux a écrit : Hi Deepak, All, It seems to me that $ svn co

Re: Planning for the creation of the new 17.xx branch(es)

Hi Deepak, All, It seems to me that $ svn co http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/branches/release17.12 ofbiz-plugins is maybe not the best name we could use. Because when the next branch will be created we will have to rename. So I propose $ svn co

Re: Planning for the creation of the new 17.xx branch(es)

Done :) Jacques Le 29/12/2017 à 12:26, Jacques Le Roux a écrit : Thanks Deepak, I noticed we miss a link to the Subversion config file in this page. But we were actually only missing global-ignores = *.o *.lo *.la #*# .*.orig *.orig .*.rej *.rej .*~ *~ .#* *.bak *.class .DS_Store in

Re: Planning for the creation of the new 17.xx branch(es)

Thanks Deepak, I noticed we miss a link to the Subversion config file in this page. But we were actually only missing global-ignores = *.o *.lo *.la #*# .*.orig *.orig .*.rej *.rej .*~ *~ .#* *.bak *.class .DS_Store in OFBiz repo branch. So I just set it and will remove the section about the

Re: Planning for the creation of the new 17.xx branch(es)

Added release17.12 in source repositories page at r#1819433. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Thu, Dec 28, 2017 at 11:23 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit : > >> On Thu, Dec 28,

Re: Planning for the creation of the new 17.xx branch(es)

Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit : On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: Le 28/12/2017 à 13:09, Michael Brohl a écrit : Regarding the website: 1. do we keep the 16.11 listed there as the stable release branch Yes, until we

Re: Planning for the creation of the new 17.xx branch(es)

Hi Michael, On Thu, Dec 28, 2017 at 5:39 PM, Michael Brohl wrote: > Regarding the website: > > 1. do we keep the 16.11 listed there as the stable release branch and add > 17.12? > > 2. the repository path for 16.11 is wrong on the current website release16.11

Re: Planning for the creation of the new 17.xx branch(es)

On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Le 28/12/2017 à 13:09, Michael Brohl a écrit : > >> Regarding the website: >> >> 1. do we keep the 16.11 listed there as the stable release branch >> > Yes, until we release 17.12 > > and add 17.12? >> > No,

Re: Planning for the creation of the new 17.xx branch(es)

Le 28/12/2017 à 13:09, Michael Brohl a écrit : Regarding the website: 1. do we keep the 16.11 listed there as the stable release branch Yes, until we release 17.12 and add 17.12? No, because 17.12 does not exist yet for users, it's only a freezed version of the trunk (if I can say so)

Re: Planning for the creation of the new 17.xx branch(es)

Regarding the website: 1. do we keep the 16.11 listed there as the stable release branch and add 17.12? 2. the repository path for 16.11 is wrong on the current website Regards, Michael Am 28.12.17 um 12:11 schrieb Jacopo Cappellato: We have now the release branches:

Re: Planning for the creation of the new 17.xx branch(es)

Great, thank you, Jacopo! Regards, Michael Am 28.12.17 um 12:11 schrieb Jacopo Cappellato: 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

Re: Planning for the creation of the new 17.xx branch(es)

Thanks Jacopo and all who participated in this release. Rishi Solanki Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com www.hotwax.co On Thu, Dec 28, 2017 at 4:41 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com>

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:

Re: Planning for the creation of the new 17.xx branch(es)

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 wrote: > That's a good idea James. > > Will you handle the cluster

Re: Planning for the creation of the new 17.xx branch(es)

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. We have prepared markdown file with the data model changes from OFBiz R9 to 17. It will help

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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 wrote: > Now that we seems

Re: Planning for the creation of the new 17.xx branch(es)

As per the discussion on http://markmail.org/message/4mrffmp5j2mujv3w and 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

Re: Planning for the creation of the new 17.xx branch(es)

+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

Re: Planning for the creation of the new 17.xx branch(es)

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,

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 wrote: > sound good +1 > > > > Le 19/12/2017 à 11:31,

Re: Planning for the creation of the new 17.xx branch(es)

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 < jacques.le.r...@les7arts.com> wrote: Le 18/12/2017 à

Re: Planning for the creation of the new 17.xx branch(es)

+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 < jacques.le.r...@les7arts.com> wrote: Le

Re: Planning for the creation of the new 17.xx branch(es)

+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 <

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 < jacques.le.r...@les7arts.com> wrote: > Le 18/12/2017 à 18:02, Jacopo Cappellato a écrit : > >> On Mon, Dec 18, 2017 at

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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

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

Re: Planning for the creation of the new 17.xx branch(es)

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]

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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 wrote: > I think Rishi makes a good point. OFBIZ-9501 is a big task but it > would be nice to create the

Re: Planning for the creation of the new 17.xx branch(es)

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,

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

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

Re: Planning for the creation of the new 17.xx branch(es)

Hi Jacopo, If nobody minds I'd prefer to wait a month more (or a bit less) I have several actions pending and my mind is in a mess because of that. So 15+ days more would help Thanks Jacques Le 28/11/2017 à 16:42, Jacopo Cappellato a écrit : It's the end of November and we are close to

Re: Planning for the creation of the new 17.xx branch(es)

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,

Re: Planning for the creation of the new 17.xx branch(es)

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,

Re: Planning for the creation of the new 17.xx branch(es)

Hi Taher, At 1s glance, I can't see any problems with individual plugins releases: +1 Jacques Le 10/10/2017 à 18:33, Taher Alkhateeb a écrit : Hi Jacopo, I recently created a JIRA [1] to finalize the implementation of of gradle to utilize a maven repository provided by Infra [2]. The

Re: Planning for the creation of the new 17.xx branch(es)

+1, good idea and good timing. -- Thanks & Regards --- Arun Patidar Manager, Enterprise Software Development HotWax Systems Pvt Ltd. www.hotwaxsystems.com On Tue, Oct 10, 2017 at 10:03 PM, Taher Alkhateeb < slidingfilame...@gmail.com> wrote: > Hi Jacopo, > > I recently created a JIRA [1] to

Re: Planning for the creation of the new 17.xx branch(es)

Hi Jacopo, I recently created a JIRA [1] to finalize the implementation of of gradle to utilize a maven repository provided by Infra [2]. The purpose of this maven repository as you may recall from our old discussion [3] is to be able to publish OFBiz plugins as ZIP archives in the repository.

Re: Planning for the creation of the new 17.xx branch(es)

Hi Jacopo, all, yes, we should definitely plan the next release. Only thinking briefly about it, I would like to have the following things completed before the release: - FindBugs and refactoring tasks (at least most of it, needs two or three rounds of review-and-commit sessions) - the

Re: Planning for the creation of the new 17.xx branch(es)

+1,  good idea! And yes it is about the right time to start focussing on this. Thanks Sharan On 10/10/17 09:35, Jacopo Cappellato wrote: 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

Re: Planning for the creation of the new 17.xx branch(es)

+1. Sounds good to me. -- Thanks and Regards, *Suraj Khurana* | Sr. Enterprise Software Engineer *HotWax Commerce* by *HotWax Systems* Plot no. 80, Scheme no. 78, Vijay Nagar, Indore, M.P. India 452010 On Tue, Oct 10, 2017 at 2:11 PM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > +1

Re: Planning for the creation of the new 17.xx branch(es)

+1 perfect make sense. release17.11 looks good to me, We have around more then 1.5 month to complete things. Thanks & Regards -- Deepak Dixit www.hotwaxsystems.com www.hotwax.co On Tue, Oct 10, 2017 at 1:05 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > Hi all, > > I

Re: Planning for the creation of the new 17.xx branch(es)

+1, that sounds indeed like the right time Jacques Le 10/10/2017 à 10:15, Devanshu Vyas a écrit : +1 Jacopo, I couldn't agree with you more. This is the right time to start planning and this way we can get all things merged in the Trunk so they can be available in the new branch. Thanks &

Re: Planning for the creation of the new 17.xx branch(es)

+1 Jacopo, I couldn't agree with you more. This is the right time to start planning and this way we can get all things merged in the Trunk so they can be available in the new branch. Thanks & Regards, Devanshu Vyas. On Tue, Oct 10, 2017 at 1:36 PM, Swapnil Mane < swapnil.m...@hotwaxsystems.com>

Re: Planning for the creation of the new 17.xx branch(es)

+1 Jacopo. We have done really good process from last OFBiz 16.11 release. And yes I think, it's a right time to start planning for next release. - Best Regards, Swapnil M Mane On Tue, Oct 10, 2017 at 1:05 PM, Jacopo Cappellato wrote: > Hi all, > > I

Planning for the creation of the new 17.xx branch(es)

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