Creating a new release branch before the end of the year ("release14.12")

[Jacopo Cappellato-4]

Hi all,

the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12" (14=2014 and 12=December).
In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.

Any objections?

Jacopo

[Jacques Le Roux]

I totally agree, this is the best way to get out of this trap for now

Jacques

Le 18/12/2014 09:53, Jacopo Cappellato a écrit :

> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12" (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>
>
>

[Ron Wheeler]

How many meetings/votes would it take to settle the specialpurpose question.
Is there a summary of the issue?
- what modules have a consensus for inclusion
- what modules are definitely out
- what modules are still under consideration for inclusion.

Ron


On 18/12/2014 3:53 AM, Jacopo Cappellato wrote:

> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12" (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>
>

--
Ron Wheeler
President
Artifact Software Inc
email: [hidden email]
skype: ronaldmwheeler
phone: [phone], ext 102

[Adrian Crum-3]

+1

I have a big commit queued up that makes form widget models thread-safe.
If the branch is created before this commit, then I would like to
backport it to R14.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 12/18/2014 8:53 AM, Jacopo Cappellato wrote:

> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12" (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>

[Jacques Le Roux]

Ha and BTW I will maybe get a chance to merge the SEO branch soon, but maybe not before we create this branch, so I'd ask for the same than Adrian for
that

Jacques

Le 18/12/2014 16:06, Adrian Crum a écrit :

> +1
>
> I have a big commit queued up that makes form widget models thread-safe. If the branch is created before this commit, then I would like to backport
> it to R14.
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 12/18/2014 8:53 AM, Jacopo Cappellato wrote:
>> Hi all,
>>
>> the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12"
>> (14=2014 and 12=December).
>> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
>> Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively
>> etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.
>>
>> Any objections?
>>
>> Jacopo
>>
>

[mandeepmavi]

Keeping specialpurpose components, will make Ofbiz 14.12 great. Specially POS and WEBPOS.
There might lots of peoples like me how spent lots of time to learn OfBIZ, and trying to use it.

So keep them in 14.12
Regards

Mandeep  

[Mridul Pathak-2]

+1. It will be nice to have a stable release before end of this year.

--
Regards,
Mridul Pathak
http://www.hotwaxmedia.com

> On Dec 18, 2014, at 2:23 PM, Jacopo Cappellato <[hidden email]> wrote:
>
> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12" (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>

[Ashish Vijaywargiya-5]

+1

--
Kind Regards
Ashish Vijaywargiya
HotWax Media - est. 1997

On Thu, Dec 18, 2014 at 2:23 PM, Jacopo Cappellato <
[hidden email]> wrote:

>
> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new
> release branch created before it ends: its name will be "release14.12"
> (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all
> apart from ecommerce as we did in 13.07, include some of them selectively
> etc...) I would temporarily include them all, and when we will have a clear
> plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>
>

[Pranay Pandey-2]

+1

Makes perfect sense.

Thanks,

Pranay Pandey
Senior Manager, Enterprise Software Development
HotWax Media
www.hotwaxmedia.com

On Thu, Dec 18, 2014 at 2:23 PM, Jacopo Cappellato <
[hidden email]> wrote:

>
> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new
> release branch created before it ends: its name will be "release14.12"
> (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all
> apart from ecommerce as we did in 13.07, include some of them selectively
> etc...) I would temporarily include them all, and when we will have a clear
> plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>
>

[Pierre Smits]

Hi Mridul,

Please be aware that creating a new branch is not the same as making a
release from that branch available to the public.

Best regards,

Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Fri, Dec 19, 2014 at 10:42 AM, Mridul Pathak <
[hidden email]> wrote:

>
> +1. It will be nice to have a stable release before end of this year.
>
> --
> Regards,
> Mridul Pathak
> http://www.hotwaxmedia.com
>
> > On Dec 18, 2014, at 2:23 PM, Jacopo Cappellato <
> [hidden email]> wrote:
> >
> > Hi all,
> >
> > the end of 2014 is getting closer and it would be nice to have a new
> release branch created before it ends: its name will be "release14.12"
> (14=2014 and 12=December).
> > In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> > Pending the discussion on specialpurpose components (exclude them all
> apart from ecommerce as we did in 13.07, include some of them selectively
> etc...) I would temporarily include them all, and when we will have a clear
> plan of action we will adjust the branch accordingly.
> >
> > Any objections?
> >
> > Jacopo
> >
>
>

[Anil Patel-3]

+1

Thanks and Regards
Anil Patel
COO
Hotwax Media Inc
http://www.hotwaxmedia.com/
ApacheCon US 2014 Silver Sponsor
http://na.apachecon.com/sponsor/our-sponsors

> On Dec 18, 2014, at 3:53 AM, Jacopo Cappellato <[hidden email]> wrote:
>
> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12" (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>

[Gil Portenseigne]

Thanks Pierre for the details, in that way I totally agree in creating
the branch !

+1

Gil

Le 19/12/2014 13:31, Pierre Smits a écrit :

> Hi Mridul,
>
> Please be aware that creating a new branch is not the same as making a
> release from that branch available to the public.
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Fri, Dec 19, 2014 at 10:42 AM, Mridul Pathak <
> [hidden email]> wrote:
>> +1. It will be nice to have a stable release before end of this year.
>>
>> --
>> Regards,
>> Mridul Pathak
>> http://www.hotwaxmedia.com
>>
>>> On Dec 18, 2014, at 2:23 PM, Jacopo Cappellato <
>> [hidden email]> wrote:
>>> Hi all,
>>>
>>> the end of 2014 is getting closer and it would be nice to have a new
>> release branch created before it ends: its name will be "release14.12"
>> (14=2014 and 12=December).
>>> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
>>> Pending the discussion on specialpurpose components (exclude them all
>> apart from ecommerce as we did in 13.07, include some of them selectively
>> etc...) I would temporarily include them all, and when we will have a clear
>> plan of action we will adjust the branch accordingly.
>>> Any objections?
>>>
>>> Jacopo
>>>
>>

[Jacques Le Roux]

Yes,  we don't put the trunk in a package and call it a release. We allow around 1 year of stablisation before...

Jacques

Le 19/12/2014 17:14, gil portenseigne a écrit :

> Thanks Pierre for the details, in that way I totally agree in creating the branch !
>
> +1
>
> Gil
>
> Le 19/12/2014 13:31, Pierre Smits a écrit :
>> Hi Mridul,
>>
>> Please be aware that creating a new branch is not the same as making a
>> release from that branch available to the public.
>>
>> Best regards,
>>
>> Pierre Smits
>>
>> *ORRTIZ.COM <http://www.orrtiz.com>*
>> Services & Solutions for Cloud-
>> Based Manufacturing, Professional
>> Services and Retail & Trade
>> http://www.orrtiz.com
>>
>> On Fri, Dec 19, 2014 at 10:42 AM, Mridul Pathak <
>> [hidden email]> wrote:
>>> +1. It will be nice to have a stable release before end of this year.
>>>
>>> --
>>> Regards,
>>> Mridul Pathak
>>> http://www.hotwaxmedia.com
>>>
>>>> On Dec 18, 2014, at 2:23 PM, Jacopo Cappellato <
>>> [hidden email]> wrote:
>>>> Hi all,
>>>>
>>>> the end of 2014 is getting closer and it would be nice to have a new
>>> release branch created before it ends: its name will be "release14.12"
>>> (14=2014 and 12=December).
>>>> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
>>>> Pending the discussion on specialpurpose components (exclude them all
>>> apart from ecommerce as we did in 13.07, include some of them selectively
>>> etc...) I would temporarily include them all, and when we will have a clear
>>> plan of action we will adjust the branch accordingly.
>>>> Any objections?
>>>>
>>>> Jacopo
>>>>
>>>
>
>

[Nicolas Malin-2]

+0

I'm neutral, I prefer planed the branch creation like 15.04 instead of
create stable release branch with many synchronize at the begin (so more
work) because some technology swap are in process and enable (and it's
good ! :)).

Nicolas

Le 18/12/2014 09:53, Jacopo Cappellato a écrit :

> Hi all,
>
> the end of 2014 is getting closer and it would be nice to have a new release branch created before it ends: its name will be "release14.12" (14=2014 and 12=December).
> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
> Pending the discussion on specialpurpose components (exclude them all apart from ecommerce as we did in 13.07, include some of them selectively etc...) I would temporarily include them all, and when we will have a clear plan of action we will adjust the branch accordingly.
>
> Any objections?
>
> Jacopo
>

[Pierre Smits]

Next year release branch 14 can also be created as it follows release
branch 13. This policy of having the branch number (and subsequent major
release number) *always* match the last two digits of the year it is
created in - and thus avoidance of gaps, is limiting us.

If we create a new branch now in order to meet adherence to that policy, it
means that we are going to exclude the 60 patches available on the JIRA
issues marked as improvement in the upcoming release. Are we sure this is
what we want?

Creating branches should meet a higher project purpose than just such a
policy.


Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Fri, Dec 19, 2014 at 7:01 PM, Nicolas Malin <[hidden email]>
wrote:

> +0
>
> I'm neutral, I prefer planed the branch creation like 15.04 instead of
> create stable release branch with many synchronize at the begin (so more
> work) because some technology swap are in process and enable (and it's good
> ! :)).
>
> Nicolas
>
> Le 18/12/2014 09:53, Jacopo Cappellato a écrit :
>
>> Hi all,
>>
>>
>> the end of 2014 is getting closer and it would be nice to have a new
>> release branch created before it ends: its name will be "release14.12"
>> (14=2014 and 12=December).
>> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
>> Pending the discussion on specialpurpose components (exclude them all
>> apart from ecommerce as we did in 13.07, include some of them selectively
>> etc...) I would temporarily include them all, and when we will have a clear
>> plan of action we will adjust the branch accordingly.
>>
>> Any objections?
>>
>> Jacopo
>>
>>
>

[Jacques Le Roux]

Le 20/12/2014 13:02, Pierre Smits a écrit :
> Next year release branch 14 can also be created as it follows release
> branch 13. This policy of having the branch number (and subsequent major
> release number) *always* match the last two digits of the year it is
> created in - and thus avoidance of gaps, is limiting us.

Nothing prevent us to not create a relase branch in 2014 and only create on in 2015 when ready.
Actually, due to Adrian's and my request, I believe we should rather go that way

> If we create a new branch now in order to meet adherence to that policy, it
> means that we are going to exclude the 60 patches available on the JIRA
> issues marked as improvement in the upcoming release. Are we sure this is
> what we want?

This is as well a good argument to delay the branch creation, even if we can expect to have all patches reviewed each time we need to create a
branch... but 60... !

>
> Creating branches should meet a higher project purpose than just such a
> policy.

As I said above you invented this policy, we are free to skip a year

Jacques

>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Fri, Dec 19, 2014 at 7:01 PM, Nicolas Malin <[hidden email]>
> wrote:
>
>> +0
>>
>> I'm neutral, I prefer planed the branch creation like 15.04 instead of
>> create stable release branch with many synchronize at the begin (so more
>> work) because some technology swap are in process and enable (and it's good
>> ! :)).
>>
>> Nicolas
>>
>> Le 18/12/2014 09:53, Jacopo Cappellato a écrit :
>>
>>> Hi all,
>>>
>>>
>>> the end of 2014 is getting closer and it would be nice to have a new
>>> release branch created before it ends: its name will be "release14.12"
>>> (14=2014 and 12=December).
>>> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
>>> Pending the discussion on specialpurpose components (exclude them all
>>> apart from ecommerce as we did in 13.07, include some of them selectively
>>> etc...) I would temporarily include them all, and when we will have a clear
>>> plan of action we will adjust the branch accordingly.
>>>
>>> Any objections?
>>>
>>> Jacopo
>>>
>>>

[Jacques Le Roux]

Le 21/12/2014 11:07, Jacques Le Roux a écrit :

>
> Le 20/12/2014 13:02, Pierre Smits a écrit :
>> Next year release branch 14 can also be created as it follows release
>> branch 13. This policy of having the branch number (and subsequent major
>> release number) *always* match the last two digits of the year it is
>> created in - and thus avoidance of gaps, is limiting us.
>
> Nothing prevent us to not create a relase branch in 2014 and only create on in 2015 when ready.
> Actually, due to Adrian's and my request, I believe we should rather go that way
>
>> If we create a new branch now in order to meet adherence to that policy, it
>> means that we are going to exclude the 60 patches available on the JIRA
>> issues marked as improvement in the upcoming release. Are we sure this is
>> what we want?
>
> This is as well a good argument to delay the branch creation, even if we can expect to have all patches reviewed each time we need to create a
> branch... but 60... !

can't

>
>>
>> Creating branches should meet a higher project purpose than just such a
>> policy.
>
> As I said above you invented this policy, we are free to skip a year
>
> Jacques
>
>>
>> Pierre Smits
>>
>> *ORRTIZ.COM <http://www.orrtiz.com>*
>> Services & Solutions for Cloud-
>> Based Manufacturing, Professional
>> Services and Retail & Trade
>> http://www.orrtiz.com
>>
>> On Fri, Dec 19, 2014 at 7:01 PM, Nicolas Malin <[hidden email]>
>> wrote:
>>
>>> +0
>>>
>>> I'm neutral, I prefer planed the branch creation like 15.04 instead of
>>> create stable release branch with many synchronize at the begin (so more
>>> work) because some technology swap are in process and enable (and it's good
>>> ! :)).
>>>
>>> Nicolas
>>>
>>> Le 18/12/2014 09:53, Jacopo Cappellato a écrit :
>>>
>>>> Hi all,
>>>>
>>>>
>>>> the end of 2014 is getting closer and it would be nice to have a new
>>>> release branch created before it ends: its name will be "release14.12"
>>>> (14=2014 and 12=December).
>>>> In this way we will have a sequential numbering: 10, 11, 12, 13, 14.
>>>> Pending the discussion on specialpurpose components (exclude them all
>>>> apart from ecommerce as we did in 13.07, include some of them selectively
>>>> etc...) I would temporarily include them all, and when we will have a clear
>>>> plan of action we will adjust the branch accordingly.
>>>>
>>>> Any objections?
>>>>
>>>> Jacopo
>>>>
>>>>
>

[Pierre Smits]

Did you get your wires crossed?


Pierre Smits

*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Sun, Dec 21, 2014 at 11:07 AM, Jacques Le Roux <
[hidden email]> wrote:

>
>
> Nothing prevent us to not create a relase branch in 2014 and only create
> on in 2015 when ready.
> Actually, due to Adrian's and my request, I believe we should rather go
> that way
>
> This is as well a good argument to delay the branch creation, even if we
> can expect to have all patches reviewed each time we need to create a
> branch... but 60... !
>
> As I said above you invented this policy, we are free to skip a year
>

[Jacques Le Roux]

Just as a reminder http://markmail.org/message/2wwueeciltqxon4r

Jacques

Le 21/12/2014 14:32, Pierre Smits a écrit :

> Did you get your wires crossed?
>
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Sun, Dec 21, 2014 at 11:07 AM, Jacques Le Roux <
> [hidden email]> wrote:
>>
>> Nothing prevent us to not create a relase branch in 2014 and only create
>> on in 2015 when ready.
>> Actually, due to Adrian's and my request, I believe we should rather go
>> that way
>>
>> This is as well a good argument to delay the branch creation, even if we
>> can expect to have all patches reviewed each time we need to create a
>> branch... but 60... !
>>
>> As I said above you invented this policy, we are free to skip a year
>>

[taher]

Hi Jacques and everyone,

I think we agree to a large degree with your proposition in the below archived thread Jacques. We see little advantage in upgrading our systems to newer versions of OFBiz because the new features do not seem to be that major!

I would prefer slowing down the release cycle and to focus on accumulation of enough features to warrant a release. Right now, both branches and releases seem to be simply snapshots in time for the project, but I see no substantial reward in upgrading nor do I see enough features to wet my appetite to play around with the new releases.

For example, here are some milestones that would highly encourage me personally to upgrade:

- Major overhaul of the UI (the bootstrap theme project for example)
- Addition of builtin documentation and completing the contextual help system
- Integration of third party systems (pentaho, CMSs, jackrabbit, etc ...)
- Substantial improvements to existing components (too much form/field clutter in current design)
- Translations and internationalization improvement
- Change / upgrade of infrastructure (logging framework, transaction management, build systems like gradle, JVM, etc ...)

My 2 cents

Taher Alkhateeb

----- Original Message -----

From: "Jacques Le Roux" <[hidden email]>
To: [hidden email]
Sent: Sunday, 21 December, 2014 5:26:40 PM
Subject: Re: Creating a new release branch before the end of the year ("release14.12")

Just as a reminder http://markmail.org/message/2wwueeciltqxon4r 

Jacques

Le 21/12/2014 14:32, Pierre Smits a écrit :

> Did you get your wires crossed?
>
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com 
>
> On Sun, Dec 21, 2014 at 11:07 AM, Jacques Le Roux <
> [hidden email]> wrote:
>>
>> Nothing prevent us to not create a relase branch in 2014 and only create
>> on in 2015 when ready.
>> Actually, due to Adrian's and my request, I believe we should rather go
>> that way
>>
>> This is as well a good argument to delay the branch creation, even if we
>> can expect to have all patches reviewed each time we need to create a
>> branch... but 60... !
>>
>> As I said above you invented this policy, we are free to skip a year
>>