You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Ron Wheeler <rw...@artifact-software.com> on 2014/09/19 15:49:27 UTC
13.07 release plan
I am new here but since I started to get active Release 13.07 has missed
2 published release dates.
I have also found out that some people are already using it in
production environment and are starting to worry about changes to 13.07
data structures and functionality that are being suggested as part of
"bug fixes" to 13.07 as part of the release.
Beta, RC1, RC2 planned?
Is there a list of tasks that need to be done to release the first 13.07
release which is currently scheduled for next week?
Have they been assigned and accepted?
When will they be completed?
There seems to be a lot of spare energy in the group at the moment and
it would be good to channel it into getting the release done.
Are there documentation or other non-coding tasks that need to be finished?
I understand that this is an open source project with volunteers but
there still needs to be some commitment to dates.
They may slip but it should be absolutely clear why they slipped and a
commitment from the PMC to see that the revised dates are met once the
PMC has published the new dates.
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Re: 13.07 release plan
Posted by Adrian Crum <ad...@sandglass-software.com>.
Personally, I always recommend deploying from the latest release branch.
Binary releases based on a branch are infrequent, while bug fix commits
in the branch are frequent.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 9/19/2014 6:26 PM, Ron Wheeler wrote:
> If there are no dates and no list of tickets to resolve, how do you know
> when you are done?
>
> Shouldn't there at least be a list of blocking tickets so people know
> what needs to be done?
> How do committers actually know which bugs are in need of fixing now and
> which ones can wait?
>
> Does the community get any visibility into the project progress?
>
> It would seem to important to know what bugs are going to be fixed in
> the 13.07.01 and which ones are deferred to the next maintenance release
> and which ones are only going to be added in the 2014 or 2015 major
> release.
>
> I would be interested in hearing from the community how people who are
> making a living with OfBiz or are using it to run their business, deal
> with this process.
> Does it actually cause any anxiety or am I just concerned about
> something that makes no difference.
>
> Ron
>
> On 19/09/2014 10:29 AM, Jacopo Cappellato wrote:
>> There is no commitment on dates, the dates on the website are just
>> tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a
>> predefined list of planned tickets to be resolved.
>>
>> However I think it is good time to prepare for the publication of the
>> new release, since the stabilization phase has been pretty long already.
>>
>> What other think? I can prepare the release artifacts and start a vote
>> in a few days if we are all ok.
>>
>> Jacopo
>>
>>
>> On Sep 19, 2014, at 3:49 PM, Ron Wheeler
>> <rw...@artifact-software.com> wrote:
>>
>>> I am new here but since I started to get active Release 13.07 has
>>> missed 2 published release dates.
>>> I have also found out that some people are already using it in
>>> production environment and are starting to worry about changes to
>>> 13.07 data structures and functionality that are being suggested as
>>> part of "bug fixes" to 13.07 as part of the release.
>>>
>>> Beta, RC1, RC2 planned?
>>> Is there a list of tasks that need to be done to release the first
>>> 13.07 release which is currently scheduled for next week?
>>> Have they been assigned and accepted?
>>> When will they be completed?
>>> There seems to be a lot of spare energy in the group at the moment
>>> and it would be good to channel it into getting the release done.
>>>
>>> Are there documentation or other non-coding tasks that need to be
>>> finished?
>>>
>>> I understand that this is an open source project with volunteers but
>>> there still needs to be some commitment to dates.
>>> They may slip but it should be absolutely clear why they slipped and
>>> a commitment from the PMC to see that the revised dates are met once
>>> the PMC has published the new dates.
>>>
>>>
>>> --
>>>
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>
>
>
Re: 13.07 release plan
Posted by Jacopo Cappellato <ja...@gmail.com>.
We have been following a rather informal process that worked quite well so far for the OFBiz community (see for example one of my recent post about the same subject).
Recently we have improved the way we manage the "version" information in Jira and we will be able to provide more precise "release notes" in the future.
Jacopo
On Sep 19, 2014, at 7:26 PM, Ron Wheeler <rw...@artifact-software.com> wrote:
> If there are no dates and no list of tickets to resolve, how do you know when you are done?
>
> Shouldn't there at least be a list of blocking tickets so people know what needs to be done?
> How do committers actually know which bugs are in need of fixing now and which ones can wait?
>
> Does the community get any visibility into the project progress?
>
> It would seem to important to know what bugs are going to be fixed in the 13.07.01 and which ones are deferred to the next maintenance release and which ones are only going to be added in the 2014 or 2015 major release.
>
> I would be interested in hearing from the community how people who are making a living with OfBiz or are using it to run their business, deal with this process.
> Does it actually cause any anxiety or am I just concerned about something that makes no difference.
>
> Ron
>
> On 19/09/2014 10:29 AM, Jacopo Cappellato wrote:
>> There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved.
>>
>> However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already.
>>
>> What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok.
>>
>> Jacopo
>>
>>
>> On Sep 19, 2014, at 3:49 PM, Ron Wheeler <rw...@artifact-software.com> wrote:
>>
>>> I am new here but since I started to get active Release 13.07 has missed 2 published release dates.
>>> I have also found out that some people are already using it in production environment and are starting to worry about changes to 13.07 data structures and functionality that are being suggested as part of "bug fixes" to 13.07 as part of the release.
>>>
>>> Beta, RC1, RC2 planned?
>>> Is there a list of tasks that need to be done to release the first 13.07 release which is currently scheduled for next week?
>>> Have they been assigned and accepted?
>>> When will they be completed?
>>> There seems to be a lot of spare energy in the group at the moment and it would be good to channel it into getting the release done.
>>>
>>> Are there documentation or other non-coding tasks that need to be finished?
>>>
>>> I understand that this is an open source project with volunteers but there still needs to be some commitment to dates.
>>> They may slip but it should be absolutely clear why they slipped and a commitment from the PMC to see that the revised dates are met once the PMC has published the new dates.
>>>
>>>
>>> --
>>>
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>
>
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
Re: 13.07 release plan
Posted by Ron Wheeler <rw...@artifact-software.com>.
If there are no dates and no list of tickets to resolve, how do you know
when you are done?
Shouldn't there at least be a list of blocking tickets so people know
what needs to be done?
How do committers actually know which bugs are in need of fixing now and
which ones can wait?
Does the community get any visibility into the project progress?
It would seem to important to know what bugs are going to be fixed in
the 13.07.01 and which ones are deferred to the next maintenance release
and which ones are only going to be added in the 2014 or 2015 major release.
I would be interested in hearing from the community how people who are
making a living with OfBiz or are using it to run their business, deal
with this process.
Does it actually cause any anxiety or am I just concerned about
something that makes no difference.
Ron
On 19/09/2014 10:29 AM, Jacopo Cappellato wrote:
> There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved.
>
> However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already.
>
> What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok.
>
> Jacopo
>
>
> On Sep 19, 2014, at 3:49 PM, Ron Wheeler <rw...@artifact-software.com> wrote:
>
>> I am new here but since I started to get active Release 13.07 has missed 2 published release dates.
>> I have also found out that some people are already using it in production environment and are starting to worry about changes to 13.07 data structures and functionality that are being suggested as part of "bug fixes" to 13.07 as part of the release.
>>
>> Beta, RC1, RC2 planned?
>> Is there a list of tasks that need to be done to release the first 13.07 release which is currently scheduled for next week?
>> Have they been assigned and accepted?
>> When will they be completed?
>> There seems to be a lot of spare energy in the group at the moment and it would be good to channel it into getting the release done.
>>
>> Are there documentation or other non-coding tasks that need to be finished?
>>
>> I understand that this is an open source project with volunteers but there still needs to be some commitment to dates.
>> They may slip but it should be absolutely clear why they slipped and a commitment from the PMC to see that the revised dates are met once the PMC has published the new dates.
>>
>>
>> --
>>
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: rwheeler@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Re: 13.07 release plan
Posted by Jacopo Cappellato <ja...@hotwaxmedia.com>.
I am going to prepare the candidate release artifacts and then start a vote.
Regards,
Jacopo
On Sep 19, 2014, at 5:17 PM, Adrian Crum <ad...@sandglass-software.com> wrote:
> I would like to see some recent trunk fixes backported to the R13 branch - like the Jacopo's EE sequencer fix, and Adam's EE encryption fix.
>
> I may have time to work on one or more of those this weekend. But don't let that be a blocker - we can still create a binary release now, and then another one after those are backported.
>
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 9/19/2014 3:29 PM, Jacopo Cappellato wrote:
>> There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved.
>>
>> However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already.
>>
>> What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok.
>>
>> Jacopo
>>
>>
>> On Sep 19, 2014, at 3:49 PM, Ron Wheeler <rw...@artifact-software.com> wrote:
>>
>>> I am new here but since I started to get active Release 13.07 has missed 2 published release dates.
>>> I have also found out that some people are already using it in production environment and are starting to worry about changes to 13.07 data structures and functionality that are being suggested as part of "bug fixes" to 13.07 as part of the release.
>>>
>>> Beta, RC1, RC2 planned?
>>> Is there a list of tasks that need to be done to release the first 13.07 release which is currently scheduled for next week?
>>> Have they been assigned and accepted?
>>> When will they be completed?
>>> There seems to be a lot of spare energy in the group at the moment and it would be good to channel it into getting the release done.
>>>
>>> Are there documentation or other non-coding tasks that need to be finished?
>>>
>>> I understand that this is an open source project with volunteers but there still needs to be some commitment to dates.
>>> They may slip but it should be absolutely clear why they slipped and a commitment from the PMC to see that the revised dates are met once the PMC has published the new dates.
>>>
>>>
>>> --
>>>
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>
Re: 13.07 release plan
Posted by Ron Wheeler <rw...@artifact-software.com>.
Would the backporting be done as part of the 13.07.02 release?
Ron
On 19/09/2014 11:17 AM, Adrian Crum wrote:
> I would like to see some recent trunk fixes backported to the R13
> branch - like the Jacopo's EE sequencer fix, and Adam's EE encryption
> fix.
>
> I may have time to work on one or more of those this weekend. But
> don't let that be a blocker - we can still create a binary release
> now, and then another one after those are backported.
>
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 9/19/2014 3:29 PM, Jacopo Cappellato wrote:
>> There is no commitment on dates, the dates on the website are just
>> tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a
>> predefined list of planned tickets to be resolved.
>>
>> However I think it is good time to prepare for the publication of the
>> new release, since the stabilization phase has been pretty long already.
>>
>> What other think? I can prepare the release artifacts and start a
>> vote in a few days if we are all ok.
>>
>> Jacopo
>>
>>
>> On Sep 19, 2014, at 3:49 PM, Ron Wheeler
>> <rw...@artifact-software.com> wrote:
>>
>>> I am new here but since I started to get active Release 13.07 has
>>> missed 2 published release dates.
>>> I have also found out that some people are already using it in
>>> production environment and are starting to worry about changes to
>>> 13.07 data structures and functionality that are being suggested as
>>> part of "bug fixes" to 13.07 as part of the release.
>>>
>>> Beta, RC1, RC2 planned?
>>> Is there a list of tasks that need to be done to release the first
>>> 13.07 release which is currently scheduled for next week?
>>> Have they been assigned and accepted?
>>> When will they be completed?
>>> There seems to be a lot of spare energy in the group at the moment
>>> and it would be good to channel it into getting the release done.
>>>
>>> Are there documentation or other non-coding tasks that need to be
>>> finished?
>>>
>>> I understand that this is an open source project with volunteers but
>>> there still needs to be some commitment to dates.
>>> They may slip but it should be absolutely clear why they slipped and
>>> a commitment from the PMC to see that the revised dates are met once
>>> the PMC has published the new dates.
>>>
>>>
>>> --
>>>
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>
>
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
Re: 13.07 release plan
Posted by Jacopo Cappellato <ja...@gmail.com>.
Adrian,
no rush on my side; we could start the process sometimes in the second part of the next week.
Regards,
Jacopo
On Sep 19, 2014, at 5:17 PM, Adrian Crum <ad...@sandglass-software.com> wrote:
> I would like to see some recent trunk fixes backported to the R13 branch - like the Jacopo's EE sequencer fix, and Adam's EE encryption fix.
>
> I may have time to work on one or more of those this weekend. But don't let that be a blocker - we can still create a binary release now, and then another one after those are backported.
>
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 9/19/2014 3:29 PM, Jacopo Cappellato wrote:
>> There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved.
>>
>> However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already.
>>
>> What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok.
>>
>> Jacopo
>>
>>
>> On Sep 19, 2014, at 3:49 PM, Ron Wheeler <rw...@artifact-software.com> wrote:
>>
>>> I am new here but since I started to get active Release 13.07 has missed 2 published release dates.
>>> I have also found out that some people are already using it in production environment and are starting to worry about changes to 13.07 data structures and functionality that are being suggested as part of "bug fixes" to 13.07 as part of the release.
>>>
>>> Beta, RC1, RC2 planned?
>>> Is there a list of tasks that need to be done to release the first 13.07 release which is currently scheduled for next week?
>>> Have they been assigned and accepted?
>>> When will they be completed?
>>> There seems to be a lot of spare energy in the group at the moment and it would be good to channel it into getting the release done.
>>>
>>> Are there documentation or other non-coding tasks that need to be finished?
>>>
>>> I understand that this is an open source project with volunteers but there still needs to be some commitment to dates.
>>> They may slip but it should be absolutely clear why they slipped and a commitment from the PMC to see that the revised dates are met once the PMC has published the new dates.
>>>
>>>
>>> --
>>>
>>> Ron Wheeler
>>> President
>>> Artifact Software Inc
>>> email: rwheeler@artifact-software.com
>>> skype: ronaldmwheeler
>>> phone: 866-970-2435, ext 102
>>>
>>
Re: 13.07 release plan
Posted by Adrian Crum <ad...@sandglass-software.com>.
I would like to see some recent trunk fixes backported to the R13 branch
- like the Jacopo's EE sequencer fix, and Adam's EE encryption fix.
I may have time to work on one or more of those this weekend. But don't
let that be a blocker - we can still create a binary release now, and
then another one after those are backported.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 9/19/2014 3:29 PM, Jacopo Cappellato wrote:
> There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved.
>
> However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already.
>
> What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok.
>
> Jacopo
>
>
> On Sep 19, 2014, at 3:49 PM, Ron Wheeler <rw...@artifact-software.com> wrote:
>
>> I am new here but since I started to get active Release 13.07 has missed 2 published release dates.
>> I have also found out that some people are already using it in production environment and are starting to worry about changes to 13.07 data structures and functionality that are being suggested as part of "bug fixes" to 13.07 as part of the release.
>>
>> Beta, RC1, RC2 planned?
>> Is there a list of tasks that need to be done to release the first 13.07 release which is currently scheduled for next week?
>> Have they been assigned and accepted?
>> When will they be completed?
>> There seems to be a lot of spare energy in the group at the moment and it would be good to channel it into getting the release done.
>>
>> Are there documentation or other non-coding tasks that need to be finished?
>>
>> I understand that this is an open source project with volunteers but there still needs to be some commitment to dates.
>> They may slip but it should be absolutely clear why they slipped and a commitment from the PMC to see that the revised dates are met once the PMC has published the new dates.
>>
>>
>> --
>>
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: rwheeler@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>
Re: 13.07 release plan
Posted by Jacopo Cappellato <ja...@gmail.com>.
There is no commitment on dates, the dates on the website are just tentative dates. We do not follow a Beta/RC1/RC2 cycle, nor we have a predefined list of planned tickets to be resolved.
However I think it is good time to prepare for the publication of the new release, since the stabilization phase has been pretty long already.
What other think? I can prepare the release artifacts and start a vote in a few days if we are all ok.
Jacopo
On Sep 19, 2014, at 3:49 PM, Ron Wheeler <rw...@artifact-software.com> wrote:
> I am new here but since I started to get active Release 13.07 has missed 2 published release dates.
> I have also found out that some people are already using it in production environment and are starting to worry about changes to 13.07 data structures and functionality that are being suggested as part of "bug fixes" to 13.07 as part of the release.
>
> Beta, RC1, RC2 planned?
> Is there a list of tasks that need to be done to release the first 13.07 release which is currently scheduled for next week?
> Have they been assigned and accepted?
> When will they be completed?
> There seems to be a lot of spare energy in the group at the moment and it would be good to channel it into getting the release done.
>
> Are there documentation or other non-coding tasks that need to be finished?
>
> I understand that this is an open source project with volunteers but there still needs to be some commitment to dates.
> They may slip but it should be absolutely clear why they slipped and a commitment from the PMC to see that the revised dates are met once the PMC has published the new dates.
>
>
> --
>
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>