I don't see why we need a new "policy." In the past, only bug fixes were
applied to release branches, and any other changes were discussed on a
case-by-case basis. That process seems to have worked well so far.
-Adrian
--- On Sat, 5/1/10, Anil Patel <anil.pa...@hotwaxmedia.com> wrote:
> From: Anil Patel <anil.pa...@hotwaxmedia.com>
> Subject: Re: New branch is now available for upcoming releases of 10.04 series
> To: dev@ofbiz.apache.org
> Cc: "Anil Patel" <anil.pa...@hotwaxmedia.com>
> Date: Saturday, May 1, 2010, 7:47 AM
> Keep asking, If there are enough
> reason, we may come up with some policy that allows for it.
>
>
> Or
> may be we create one more release branch as soon as in next
> two months and kill this branch in its alpha stage itself.
>
> Thanks and Regards
> Anil Patel
> HotWax Media Inc
> Find us on the web at www.hotwaxmedia.com or Google Keyword
> "ofbiz"
>
> On May 1, 2010, at 5:16 AM, chris snow wrote:
>
> > It would be good if we could backport the field
> tooltip messages too.
> >
> > Many thanks, chris
> >
> > On 1 May 2010 09:59, "Vikas Mayur" <vikasma...@gmail.com>
> wrote:
> >
> > Thanks Jacopo for all of your hard work to make it
> happen.
> >
> > Btw I am not sure if this is a good question to you
> (and others of course)
> > about commit policy to the release branch.
> >
> > We all know that the main idea behind the release
> branch is to provide a
> > more stable version of OFBiz.
> >
> > I was just wondering if we could also change the
> commit policy to back port
> > unit test besides bug fixes.
> >
> > This way there would be more code coverage with the
> additional unit tests
> > resulted by backporting to the release branch.
> >
> > I am sorry if this has been already discussed in
> past.
> >
> > Regards
> > Vikas
> >
> >
> >
> >
> > On Sat, May 1, 2010 at 1:28 PM, Jacopo Cappellato
> <
> > jacopo.cappell...@hotwaxmedia.com>
> wrote:
> >
> >> ...
>
>
