On 05/02/2015 9:49 AM, Adrian Crum wrote:
All of this is already stated on the OFBiz web site, so I don't
understand the point of this reply.
Reference?
My plans are no different than many other branch backports that have
been done in the past.
Jacques seemed to find that not to be true.
I thought that I was supporting your plan but you comment has me a bit
baffled.
Ron
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 2/5/2015 6:41 AM, Ron Wheeler wrote:
Releases are stable.
Things that are not released are mutable.
The use of unconventional conventions should be stopped as soon as
possible.
If a branch has reached a state where no more changes except bug fixes
are expected then prioritize and clean up the JIRA issues that are
sufficiently important and likely to get fixed in the short term and
release it and start the development branch or trunk on the way to the
next minor release.
If there are a lot of required issues, then make it a community project
to release it and get it done.
If it is not clear about the state of a release branch, then have a
meeting and make a decision.
Either it is
a) still under development and unstable or
b) it is a release candidate and only a defined and agreed upon set of
bugs will be fixed before it is released and other low priority bugs and
backports will get done in the next minor release. If a new critical bug
is found after it is declared a RC, then the team gets to decide if it
is included and adds it to the priority list or defers it.
If it is deferred, add a note in the release notes that an important bug
is not fixed in the release but is or will be available as a patch to
the version in the trunk or development branch.
This is not rocket science and if it done properly, in an organized way,
it will be clear to Adrian and everyone how any backporting or bug
fixing should be done.
"Sort of" stable branches is not really acceptable as a management
policy for a production quality software product.
Ron
On 05/02/2015 3:26 AM, Jacques Le Roux wrote:
I would though wait that all the possibly related opened Jiras will be
fixed. Some projects are based on the R14.12 branch and people expect
this branch to be stable even if not yet released.
Jacques
Le 04/02/2015 06:34, Jacopo Cappellato a écrit :
On Jan 17, 2015, at 11:16 PM, Adrian Crum
<adrian.c...@sandglass-software.com> wrote:
After all of this work is completed, I would like to backport it to
the R14 branch.
Hi Adrian,
I just wanted to mention that I agree that we should backport all
this work to the 14.12 branch, which is pretty new and still needs to
undergo to the stabilization process: in this way it will be easier
to maintain it (by backporting the fixes) in the future years.
Jacopo
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
