On Apr 6, 2007, at 10:48 AM, Adrian Crum wrote:
David E. Jones wrote:This strays quite a bit from what is described in the Release Plan.Are you saying that before we even begin this discussion we should work on some changes to the Release Plan?The subject of this thread is "What to get in before release?" I answered that question. No, I'm not suggesting that we change the release plan.
I guess what I mean is that according to the release plan the point is not so much to make sure bugs are fixed before the branch. Though obviously that's better, it's not required _before_ the branch, that is the point of stabilizing the branch after it is setup (ie the first 2-3 months of the branch's life).
Also, we are not trying to approach a certain feature set as is traditionally done with packaged software. In other words, we'll do the branch when the code is in a decent state and choose not to have regrets about the fact that such and such feature didn't make it in. The fact of the matter is that there are always hundreds of features floating in people's minds and most of these won't make it in right away, some may not even make it in before next year's branch... ;)
Still, there are certain things that are messy or clearly broken that we should take care of before the branch, partially as an opportunity to shine for those looking into OFBiz for the first time, and that is the point of this thread.
That said, sorry to interrupt the brainstorming! Please comment and don't worry about what I think, I just wanted to point everyone to the Release Plan. Please read it, or read it again, as you consider items for the upcoming release branch.
http://docs.ofbiz.org/display/OFBADMIN/Release+Plan -David
smime.p7s
Description: S/MIME cryptographic signature
