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

[Jacopo Cappellato-5]

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

[Swapnil Mane]

+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 <jacopo.cappellato@
hotwaxsystems.com> 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
> 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
>

[Devanshu Vyas-2]

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

> +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 <jacopo.cappellato@
> hotwaxsystems.com> 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
> > 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
> >
>

[Jacques Le Roux]

+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 & Regards,
> Devanshu Vyas.
>
> On Tue, Oct 10, 2017 at 1:36 PM, Swapnil Mane <
> [hidden email]> wrote:
>
>> +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 <jacopo.cappellato@
>> hotwaxsystems.com> 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
>>> 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
>>>

[Deepak Dixit-3]

+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 <
[hidden email]> 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
> 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
>

[Suraj Khurana]

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

> +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 <
> [hidden email]> 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
> > 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
> >
>

[Sharan-F]

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

[Michael Brohl-3]

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 common theme work

There may be others, I need some silent minutes to think about it later.
November might be a bit too tight for these, maybe we could have a
December release?

What do you think?

Best regards,

Michael Brohl
ecomify GmbH
www.ecomify.de


Am 10.10.17 um 09:35 schrieb Jacopo Cappellato:

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

[taher]

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.

So now the question has come, how do we publish? I don't have a very
clear idea in mind, but here are some thoughts:

- We proceed exactly as you suggested for the release branches.
- For plugins I distinguish between release branches vs actual
releases as follows
  - A single release branch would contain _all_ plugins (as exists right now)
  - However, for actual plugin releases maybe we just create a tag in
version control and then publish individually and separately to maven.

This way, we encourage people to avoid thinking of plugins as things
that you download from a branch and place manually, and instead think
of them as extra functionality that OFBiz can provide for you with a
single command on the command line (or maybe even through the UI in
the future). On a side note, I think this is going to be a great
release. We've accomplished a lot and solved quite a few bugs thanks
to the great efforts from the community.

Oh and +1 :)

[1] https://issues.apache.org/jira/browse/OFBIZ-9832
[2] https://issues.apache.org/jira/browse/INFRA-13924
[3] http://markmail.org/message/bjvqu23ofwzuk57y

Cheers,

Taher Alkhateeb

On Tue, Oct 10, 2017 at 10:35 AM, Jacopo Cappellato
<[hidden email]> 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
> 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

[Arun Patidar-2]

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

> 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.
>
> So now the question has come, how do we publish? I don't have a very
> clear idea in mind, but here are some thoughts:
>
> - We proceed exactly as you suggested for the release branches.
> - For plugins I distinguish between release branches vs actual
> releases as follows
>   - A single release branch would contain _all_ plugins (as exists right
> now)
>   - However, for actual plugin releases maybe we just create a tag in
> version control and then publish individually and separately to maven.
>
> This way, we encourage people to avoid thinking of plugins as things
> that you download from a branch and place manually, and instead think
> of them as extra functionality that OFBiz can provide for you with a
> single command on the command line (or maybe even through the UI in
> the future). On a side note, I think this is going to be a great
> release. We've accomplished a lot and solved quite a few bugs thanks
> to the great efforts from the community.
>
> Oh and +1 :)
>
> [1] https://issues.apache.org/jira/browse/OFBIZ-9832
> [2] https://issues.apache.org/jira/browse/INFRA-13924
> [3] http://markmail.org/message/bjvqu23ofwzuk57y
>
> Cheers,
>
> Taher Alkhateeb
>
> On Tue, Oct 10, 2017 at 10:35 AM, Jacopo Cappellato
> <[hidden email]> 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
> > 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
>

[Jacques Le Roux]

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
> 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.
>
> So now the question has come, how do we publish? I don't have a very
> clear idea in mind, but here are some thoughts:
>
> - We proceed exactly as you suggested for the release branches.
> - For plugins I distinguish between release branches vs actual
> releases as follows
>    - A single release branch would contain _all_ plugins (as exists right now)
>    - However, for actual plugin releases maybe we just create a tag in
> version control and then publish individually and separately to maven.
>
> This way, we encourage people to avoid thinking of plugins as things
> that you download from a branch and place manually, and instead think
> of them as extra functionality that OFBiz can provide for you with a
> single command on the command line (or maybe even through the UI in
> the future). On a side note, I think this is going to be a great
> release. We've accomplished a lot and solved quite a few bugs thanks
> to the great efforts from the community.
>
> Oh and +1 :)
>
> [1] https://issues.apache.org/jira/browse/OFBIZ-9832
> [2] https://issues.apache.org/jira/browse/INFRA-13924
> [3] http://markmail.org/message/bjvqu23ofwzuk57y
>
> Cheers,
>
> Taher Alkhateeb
>
> On Tue, Oct 10, 2017 at 10:35 AM, Jacopo Cappellato
> <[hidden email]> 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
>> 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

[Nicolas Malin-2]

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
>

[Jacopo Cappellato-5]

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

[Jacques Le Roux]

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

[Michael Brohl-3]

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

[Rishi Solanki]

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: [phone]
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
> >>
> >>
> >
>

[taher]

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: [phone]
> 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
>> >>
>> >>
>> >
>>

[Jacopo Cappellato-5]

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: [phone]
> > 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
> >> >>
> >> >>
> >> >
> >>
>

[Nicolas Malin-2]

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: [phone]
>>> 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
>>>>>>
>>>>>>

[Jacques Le Roux]

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: [phone]
>>>> 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
>>>>>>>
>>>>>>>
>
>