I agree with Jacopo, KISS please, we have already enough work...
Jacques
From: "Jacopo Cappellato" <jacopo.cappell...@hotwaxmedia.com>
Hi Pierre,
I understand what you propose and it makes sense; I am onlya bit worried about
the confusion of having tom many versions in Jira.
For example, if a bug fix is provided for the 10.04 series, then it should be most likely planned to be included in the upcoming
release 10.04.02; I don't see a benefit of having also 10.04.03, 10.04.04, 10.04.05 in Jira.
We could instead create 10.04.03 when 10.04.02 is released.
But I don't have a strong opinion on this; but before creating new versions in Jira I would like to get also the point of view of
others.
Thanks,
Jacopo
On Apr 8, 2012, at 10:56 AM, Pierre Smits wrote:
Hi Jacopo,
Currently following releases are identified on the web page (with their
respective target dates):
- April 2012 - Apache OFBiz 10.04.02
- October 2012 - Apache OFBiz 10.04.03
- April 2013 - Apache OFBiz 10.04.04 (last release of the 10.04 series)
Tentative release schedule for the 11.04 series:
- May 2012 - Apache OFBiz 11.04.01
- September 2012 - Apache OFBiz 11.04.02
- March 2013 - Apache OFBiz 11.04.03
- September 2013 - Apache OFBiz 11.04.04
- April 2014 - Apache OFBiz 11.04.05 (last release of the 11.04 series)
Tentative release schedule for the 12.04 series:
- April 2012 - creation of the release branch for 12.04 (this is not a
release yet)
- February 2013 - Apache OFBiz 12.04.01
- August 2013 - Apache OFBiz 12.04.02
- March 2014 - Apache OFBiz 12.04.03
- September 2014 - Apache OFBiz 12.04.04
- April 2015 - Apache OFBiz 12.04.05 (last release of the 12.04 series)
So I would say that all intended releases with a future date should be
registered in JIRA (with the date set). That will help us ddevelopers (and
committers) to focus on delivering the best release possible each time. And
it will help use generate a more detailed 'end-of-month report. It helps
with timing the issue, and thus communication.
But developers and committers should be aware of the fact that it doesn't
make sense to allocate JIRA issues tot more than 1 version/release,
meaning, that setting the fix version of an issue to e.g. 12.04.01 also
implies that it is applicable to 12.04.02.
Thus, when the first release date of a version draws near, we can release
that version when no blockers or other critical issues are present and
others (still not fixed issues) can move to the next release.
Regards,
Pierre
Op 8 april 2012 08:01 schreef Jacopo Cappellato <
jacopo.cappell...@hotwaxmedia.com> het volgende:
Hi Pierre,
now that we have a tentative release plan:
http://ofbiz.apache.org/download.html
it would be easy to setup in Jira versions for upcoming releases (with a
release date); at the moment we could add:
10.04.02 with release date 2012-04-30
11.04.01 with release date 2012-05-31
Does it sound good?
Jacopo
On Apr 7, 2012, at 11:19 AM, Pierre Smits wrote:
Hi Jacopo,
May I suggest to set a target date for this and the other releases
intended
for the near future (ie 09.04.02, 10.04.02, 11.x, 12.x). This will help
us
to better identify issues which we intend to address per release. But it
also helps us communicate to the communty, than repeat over and over in
the
mailing lists.
Regards,
Pierre
Op 5 april 2012 21:23 schreef Erwan de FERRIERES <
erwan.de-ferrie...@nereide.fr> het volgende:
Le 05/04/2012 10:26, Jacopo Cappellato a écrit :
Yeah, I think it is now time to start the process, thank you Erwan.
I have created the new version with name "SlimDown" (if a better name
will be suggested we will change it); now we can create the tasks for
the
agreed upon decisions so far and use the "Fix Version/s" field to
associate
them to the roadmap.
Jacopo
Thanks Jacopo, now let's work !
On Apr 5, 2012, at 10:00 AM, Erwan de FERRIERES wrote:
Hi Jacopo,
do we have a better name for the Jira version than slimdown ? And
would it be possible to create the jira version, so we can start on
creating the tasks ?
Cheers,
--
Erwan de FERRIERES
--
Erwan de FERRIERES
www.nereide.biz
