Re: release?

[David E. Jones]

So, maybe we need a thread for a RFC on the Release Plan first?



-David


On Apr 17, 2007, at 11:58 AM, BJ Freeman wrote:

I'm just concerned because most of the discussion seems to be related to things that are already in the Release Plan. The big point of the release plan that everyone seems to agree on is, let's just do the branch! The point of the plan is to handle it not being perfect on day 1, etc.

I have read the release plan, however it has been there for a while and

we can't seem to get to the next step of implementing.
I am guessing everyone is saying lets get a move on.
Action

David E. Jones sent the following on 4/17/2007 8:55 AM:

This is a very relevant topic, but it might be helpful to in terms of
the existing Release Plan:

http://docs.ofbiz.org/display/OFBADMIN/Release+Plan


is the plan, but maybe we should do it X way because of Y". Is that

not worth reading?

But yeah, these things are addressed in the Release Plan.

-David


On Apr 17, 2007, at 10:05 AM, Jonathon -- Improov wrote:

I don't see people referring to this much or talking in terms of "this because the Release Plan is just total crap, or maybe it's too long and

What about simply forking a release branch now, and then we work on
stabilizing and debugging THAT branch?


from the trunk, but only fixes to bring the branch towards stability
for final release. I'd recommend using Release Candidates.


basing my work on that branch rather than the trunk, anyway.

If no one else is familiar with this branching strategy, I may be
willing to take on the admin work for this. Just let me know when my
deadlines and what my deliverables will be.

Jonathon

Si Chen wrote:

As and when new fixes go into the trunk, we can merge those fixes into the branch. Ideally, the release branch will not take in new features I'd be the first one to offer to test the release branch in the effort to bring it to release status. If there _is_ a release branch, I'll be

The SVN right now is in reasonably good shape in my opinion -- it's
been more stable in the past, but there's also been a lot of times

a stable point and resolve any critical applications bugs, and then
it should be a pretty good release.
Having said that, is it better to create a release branch now, or
wait a little bit?  This would depend on everybody's development
plans.  I notice David and Andy are doing a lot of things in the
framework and base methods and that there have been some bugs that
are being fixed.  Could the next few days, week, or two weeks be

being committed?  If so, then it'd be better to wait until then.

new but not necessarily critical features or refactorings arrive.
Shi Yusen wrote:

when it's a lot less stable. I think we need to get the framework to spent primarily addressing these issues without a lot of new features Otherwise, let's just make the release branch before a whole bunch of

+1 for creating a release branch.

Also, without responses the branch will basically just include
whatever it includes.

As an training course, I have arranged a man to test current HEAD in

different enviroments.

I think the release branch can be created now.

Regards,

Shi Yusen/Beijing Langhua Ltd.

------------------------------------------------------------------- -----

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 269.5.0/763 - Release Date:
4/16/2007 5:53 PM

smime.p7s
Description: S/MIME cryptographic signature