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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
54 messages Options
123
Reply | Threaded
Open this post in threaded view
|

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

Rishi Solanki
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 <
[hidden email]> wrote:

> 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
>
Reply | Threaded
Open this post in threaded view
|

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

Michael Brohl-3
In reply to this post by Jacopo Cappellato-5
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 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
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

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

Michael Brohl-3
In reply to this post by Jacopo Cappellato-5
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:
>
> 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
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
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)

Jacques

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

Reply | Threaded
Open this post in threaded view
|

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

Jacopo Cappellato-5
On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
[hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
> version of the trunk (if I can say so)
>
>
But that page is not the download page, in which only official releases are
published; the page we are talking about is the ones that lists our source
repositories, including the trunk and so we should definitely add to it the
new branches.

Jacopo
Reply | Threaded
Open this post in threaded view
|

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

Deepak Dixit-3
In reply to this post by Michael Brohl-3
Hi Michael,


On Thu, Dec 28, 2017 at 5:39 PM, Michael Brohl <[hidden email]>
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 repository path is correct on website
http://svn.apache.org/repos/asf/ofbiz/branches/release16.11


Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co



>
>
> 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/branc
>> hes/release17.12/
>> https://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/branche
>> s/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
>>
>>
>
>
Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
In reply to this post by Jacopo Cappellato-5
Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :

> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>> version of the trunk (if I can say so)
>>
>>
> But that page is not the download page, in which only official releases are
> published; the page we are talking about is the ones that lists our source
> repositories, including the trunk and so we should definitely add to it the
> new branches.
>
> Jacopo
>
Right, and we need to add the plugins...

Jacques

Reply | Threaded
Open this post in threaded view
|

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

Deepak Dixit-3
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 <
[hidden email]> wrote:

> Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :
>
>> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
>> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>>> version of the trunk (if I can say so)
>>>
>>>
>>> But that page is not the download page, in which only official releases
>> are
>> published; the page we are talking about is the ones that lists our source
>> repositories, including the trunk and so we should definitely add to it
>> the
>> new branches.
>>
>> Jacopo
>>
>> Right, and we need to add the plugins...
>
> Jacques
>
>
Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
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 the Subversion config file in this page.

In other words, committers no longer need to worry about adding this file on their local machine.

They though can still refer to it for feature not set in the OFBiz repo branch.

Jacques
PS: this is a WIP and I'll maybe need to put back the specific client global-ignores, seems that, though inherited (I view them), setting .git .gradle
and build does not work:

C:\projectsASF\ofbiz>svn st
?       .gradle
?       build


Le 28/12/2017 à 19:06, Deepak Dixit a écrit :

> 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 <
> [hidden email]> wrote:
>
>> Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :
>>
>>> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
>>> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>>>> version of the trunk (if I can say so)
>>>>
>>>>
>>>> But that page is not the download page, in which only official releases
>>> are
>>> published; the page we are talking about is the ones that lists our source
>>> repositories, including the trunk and so we should definitely add to it
>>> the
>>> new branches.
>>>
>>> Jacopo
>>>
>>> Right, and we need to add the plugins...
>> Jacques
>>
>>

Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
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 OFBiz repo branch. So I just set it and will remove the section about the the Subversion config file in this page.
>
> In other words, committers no longer need to worry about adding this file on their local machine.
>
> They though can still refer to it for feature not set in the OFBiz repo branch.
>
> Jacques
> PS: this is a WIP and I'll maybe need to put back the specific client global-ignores, seems that, though inherited (I view them), setting .git
> .gradle and build does not work:
>
> C:\projectsASF\ofbiz>svn st
> ?       .gradle
> ?       build
>
>
> Le 28/12/2017 à 19:06, Deepak Dixit a écrit :
>> 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 <
>> [hidden email]> wrote:
>>
>>> Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :
>>>
>>>> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
>>>> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>>>>> version of the trunk (if I can say so)
>>>>>
>>>>>
>>>>> But that page is not the download page, in which only official releases
>>>> are
>>>> published; the page we are talking about is the ones that lists our source
>>>> repositories, including the trunk and so we should definitely add to it
>>>> the
>>>> new branches.
>>>>
>>>> Jacopo
>>>>
>>>> Right, and we need to add the plugins...
>>> Jacques
>>>
>>>
>
>

Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
In reply to this post by Deepak Dixit-3
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 http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/branches/release17.12 release17.12-plugins

That's it's only a convention and users can use what they want, but better to use a right convention from start ;)

What do you think?

Jacques


Le 28/12/2017 à 19:06, Deepak Dixit a écrit :

> 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 <
> [hidden email]> wrote:
>
>> Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :
>>
>>> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
>>> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>>>> version of the trunk (if I can say so)
>>>>
>>>>
>>>> But that page is not the download page, in which only official releases
>>> are
>>> published; the page we are talking about is the ones that lists our source
>>> repositories, including the trunk and so we should definitely add to it
>>> the
>>> new branches.
>>>
>>> Jacopo
>>>
>>> Right, and we need to add the plugins...
>> Jacques
>>
>>

Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
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 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 http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/branches/release17.12 release17.12-plugins
>
> That's it's only a convention and users can use what they want, but better to use a right convention from start ;)
>
> What do you think?
>
> Jacques
>
>
> Le 28/12/2017 à 19:06, Deepak Dixit a écrit :
>> 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 <
>> [hidden email]> wrote:
>>
>>> Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :
>>>
>>>> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
>>>> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>>>>> version of the trunk (if I can say so)
>>>>>
>>>>>
>>>>> But that page is not the download page, in which only official releases
>>>> are
>>>> published; the page we are talking about is the ones that lists our source
>>>> repositories, including the trunk and so we should definitely add to it
>>>> the
>>>> new branches.
>>>>
>>>> Jacopo
>>>>
>>>> Right, and we need to add the plugins...
>>> Jacques
>>>
>>>
>
>

Reply | Threaded
Open this post in threaded view
|

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

Deepak Dixit-3
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 <
[hidden email]> wrote:

> 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 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 http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/branches
>> /release17.12 release17.12-plugins
>>
>> That's it's only a convention and users can use what they want, but
>> better to use a right convention from start ;)
>>
>> What do you think?
>>
>> Jacques
>>
>>
>> Le 28/12/2017 à 19:06, Deepak Dixit a écrit :
>>
>>> 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 <
>>> [hidden email]> wrote:
>>>
>>> Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :
>>>>
>>>> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
>>>>> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>>>>>> version of the trunk (if I can say so)
>>>>>>
>>>>>>
>>>>>> But that page is not the download page, in which only official
>>>>>> releases
>>>>>>
>>>>> are
>>>>> published; the page we are talking about is the ones that lists our
>>>>> source
>>>>> repositories, including the trunk and so we should definitely add to it
>>>>> the
>>>>> new branches.
>>>>>
>>>>> Jacopo
>>>>>
>>>>> Right, and we need to add the plugins...
>>>>>
>>>> Jacques
>>>>
>>>>
>>>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

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

Jacques Le Roux
Administrator
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 <
> [hidden email]> wrote:
>
>> 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 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 http://svn.apache.org/repos/asf/ofbiz/ofbiz-plugins/branches
>>> /release17.12 release17.12-plugins
>>>
>>> That's it's only a convention and users can use what they want, but
>>> better to use a right convention from start ;)
>>>
>>> What do you think?
>>>
>>> Jacques
>>>
>>>
>>> Le 28/12/2017 à 19:06, Deepak Dixit a écrit :
>>>
>>>> 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 <
>>>> [hidden email]> wrote:
>>>>
>>>> Le 28/12/2017 à 18:23, Jacopo Cappellato a écrit :
>>>>> On Thu, Dec 28, 2017 at 5:47 PM, Jacques Le Roux <
>>>>>> [hidden email]> 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, because 17.12 does not exist yet for users, it's only a freezed
>>>>>>> version of the trunk (if I can say so)
>>>>>>>
>>>>>>>
>>>>>>> But that page is not the download page, in which only official
>>>>>>> releases
>>>>>>>
>>>>>> are
>>>>>> published; the page we are talking about is the ones that lists our
>>>>>> source
>>>>>> repositories, including the trunk and so we should definitely add to it
>>>>>> the
>>>>>> new branches.
>>>>>>
>>>>>> Jacopo
>>>>>>
>>>>>> Right, and we need to add the plugins...
>>>>>>
>>>>> Jacques
>>>>>
>>>>>
>>>>>
>>>

123