This is a great tool. The problem with the tool and the approach in
general to this sort of release management is that it assumes top-down
management of a project.
In the Release Plan document it starts out by explaining the nature of
OFBiz and the community that drives it. Most ASF projects, and many
other open source projects, are community driven but are also more
limited in scope and have either an existing specification to work
toward, or have a sufficiently limited scope that the definition of
targets for a release is not overly burdensome.
With OFBiz it's not just the size of the scope, but the fact that the
scope depends on what different contributors to OFBiz need over time,
for themselves or their clients/customers. If we had a budget for
driving OFBiz top-down that could result in the same volume of
progress it would have to be around $5-10M per year (my own estimate
of course, no Gartner or the like has deigned to look into this).
In short there is a reason why OFBiz is the only real community driven
open source enterprise automation project out there. The closest
alternative is probably Adempiere, but that is more of a community
driven effort to replace a bad vendor that has mostly stepped out of
the picture.
So, until someone comes along with a sufficient budget to drive things
in a more "traditional" way, we have to stick with what works
according to what people are willing and able to contribute.
-David
On Apr 14, 2008, at 7:45 AM, Bruno Busco wrote:
Jacques,
what I was speaking about was the release management functionality
in JIRA
that I will try to resume here:
- The jira project administrator defines one or more versions (say
OFBIZ
4.1, OFBIZ 4.2, OFBIZ 5.0) using the "adminster project" link and
then the
"versions manage" link.
- The release manager then can schedule all the open issues to be
resolved
in one of the future versions setting the "Fix version" field of
each issue.
By doing this when looking at the "road map" all programmed future
versions
are listed and for each version the list of issue that must be
resolved to
release the version are listed (with the status fixed, open etc.)
- When all the issue that were scheduled for a version are resolved
the
version can be released using the the "adminster project" link and
then the
"versions manage" link.
- When a version is released it does not appear any more in the
"road map"
page but in the "change log" page. Here there will always be
available the
list of all the version released with the list of all the issues
resolved in
each.
When defining future versions an estimated (or desired) date can
also be
specified and so a clear road map is evident to everybody.
Everyone will see when next version will be released and above all
what
issues is going to resolve and what issues are not going to be
resolved
becouse are scheduled for a successive release or not scheduled at
all.
-Bruno
2008/4/14, Jacques Le Roux <[EMAIL PROTECTED]>:
Hi Bruno,
Could you tell us more about this ? (leasy request to avoid to read
the
documentation, you may reply by a RTFM if you like ;o)
Thanks
Jacques
From: "Bruno Busco" <[EMAIL PROTECTED]>
Thank you David,
so, if I well understand, having release 4.0 been released about
an year
ago, we should have next release soon!
BTW I think that using JIRA release management features (roadmap,
change
log
and issue fix version) will be of great help to the community.
Take this
as
just a suggestion from a JIRA fun ;-).
-Bruno
2008/4/10, David E Jones <[EMAIL PROTECTED]>:
http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
-David
On Apr 10, 2008, at 11:32 AM, Bruno Busco wrote:
Hi,
i would like to ask if there is a roadmap to the next Ofbiz
release
(or
release candidate).
When (based on time or based on task/functionality to be
implemented) is
it
planned?
I do not see the JIRA roadmap feature used here but I think it
would
be
great.
Thanks,
- Bruno
