Right JUST DO IT (my way:)
OK, so I believe that the 2.1 beta that is out is getting little pounding
because it is not on the main page. I will remedy that right now.
Once we have this out. I would encourage everyone to stop adding stuff
STARTING NEXT WEEK. Like a "feature freeze" at least long enough to get
people working on 2.1 BETA.
All new feature are to be moved to the new development branch. Fixes to the
2.1 beta to be put in both branches.
PROPOSAL:
SO STARTING NEXT MONDAY
2 branches
2.1 BETA
2.3
2.1 BETA is FEATURE FREEZED as we go to 2.1 FINAL = 2.2. If there are
really big feature we want to squeeze in do it now.
2.3 is the development branch, CVS downloadable as is today, even as
snapshot.
Does this make sense. Any voices against?
I am no cvs guru so clear instruction on how to do this would be very
welcome
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
|Sent: Wednesday, February 28, 2001 5:59 PM
|To: JBoss-Dev
|Subject: RE: [jBoss-Dev] RE: [jBoss-User] Distribution and fail over
|
|
|On Wed, 28 Feb 2001, marc fleury wrote:
|> Yes, I promised "tagged" releases and branches we would merge?
|>
|> But you are talking about a totally new tree?
|
| A branch would be fine. I think we'll have to make a lot of noise
|araound it, so people are aware that their changes will only apply to the
|branch or the head, and can decide what should go where. And ideally, we
|need to pick a stable point to branch before any new features roll in.
|It seems to me like there's still enough CVS activity that now is not
|necessarily a stable point. Shall we declare a date for the split and
|then try to organize some stableness leading up to it, or do you want to
|"just do it"?
|
|Aaron
|
|
