Re: [JBoss-dev] RabbitHole branch created

2001-06-13 Thread Scott M Stark

Right and Right. The cvs doc is being created right now. Its
release is imminent.

- Original Message - 
From: marc fleury [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, June 13, 2001 7:16 AM
Subject: RE: [JBoss-dev] RabbitHole branch created


 Right RABBITHOLE branch IS the MAIN branch
 
 (right?)
 
 so I just do the usual checkout
 
 (right?)
 
 (scott? can you turn on the light in this room... it is damp dark, and I am
 afraid that anywhere I put my arm it will be full of millions of swarming
 little bugs crawling all over my arm and thousands of rats climbing up my
 legs... scott?)
 
 marc
 
 



___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] RabbitHole branch created

2001-06-12 Thread Juha-P Lindfors


hi,

why a branch?  It's easier to work on the main trunk and since most
development effort is going into 3.0 let's just freeze 2.4, branch the 2.4,
release 2.4 BETA and fix 2.4 issues in the branch. Keep main
development in the trunk.

-- Juha


On Mon, 11 Jun 2001, Scott M Stark wrote:

 I created a RabbitHole branch off of the current main line for prototyping
 the 3.0 generation of JBoss. You can access the branch via the command
 line version of cvs using:

 cvs -d :ext:[EMAIL PROTECTED]:/cvsroot/jboss co -r 
RabbitHole jboss




 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-development



___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] RabbitHole branch created

2001-06-12 Thread Scott M Stark

Your right. Making a future branch will just mean a lot of
merging.

- Original Message - 
From: Juha-P Lindfors [EMAIL PROTECTED]
To: JBoss Dev [EMAIL PROTECTED]
Sent: Tuesday, June 12, 2001 9:43 AM
Subject: Re: [JBoss-dev] RabbitHole branch created


 
 hi,
 
 why a branch?  It's easier to work on the main trunk and since most
 development effort is going into 3.0 let's just freeze 2.4, branch the 2.4,
 release 2.4 BETA and fix 2.4 issues in the branch. Keep main
 development in the trunk.
 
 -- Juha
 
 
 On Mon, 11 Jun 2001, Scott M Stark wrote:
 
  I created a RabbitHole branch off of the current main line for prototyping
  the 3.0 generation of JBoss. You can access the branch via the command
  line version of cvs using:
 
  cvs -d :ext:[EMAIL PROTECTED]:/cvsroot/jboss co -r 
RabbitHole jboss
 
 
 
 
  ___
  Jboss-development mailing list
  [EMAIL PROTECTED]
  http://lists.sourceforge.net/lists/listinfo/jboss-development
 
 
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-development
 


___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] RabbitHole branch created

2001-06-12 Thread marc fleury

I am ok with this, but a bit unsure as to what I am supposed to be doing
with the branches then...

Juha you say main will be the 3.0 stuff?
so we
1- get rid of the new branch
2- keep the current base as a new new branch
3- let the main be the current branch

I can see that it will minimize the number of back ports... please let me
know what I should be doing when I start commiting if anything... I also
understand that we all will be working on that branch... I am ok with it

marcf


|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Tuesday, June 12, 2001 1:10 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] RabbitHole branch created
|
|
|Your right. Making a future branch will just mean a lot of
|merging.
|
|- Original Message -
|From: Juha-P Lindfors [EMAIL PROTECTED]
|To: JBoss Dev [EMAIL PROTECTED]
|Sent: Tuesday, June 12, 2001 9:43 AM
|Subject: Re: [JBoss-dev] RabbitHole branch created
|
|
|
| hi,
|
| why a branch?  It's easier to work on the main trunk and since most
| development effort is going into 3.0 let's just freeze 2.4,
|branch the 2.4,
| release 2.4 BETA and fix 2.4 issues in the branch. Keep main
| development in the trunk.
|
| -- Juha
|
|
| On Mon, 11 Jun 2001, Scott M Stark wrote:
|
|  I created a RabbitHole branch off of the current main line for
|prototyping
|  the 3.0 generation of JBoss. You can access the branch via the command
|  line version of cvs using:
| 
|  cvs -d
|:ext:[EMAIL PROTECTED]:/cvsroot/jboss
|co -r RabbitHole jboss
| 
| 
| 
| 
|  ___
|  Jboss-development mailing list
|  [EMAIL PROTECTED]
|  http://lists.sourceforge.net/lists/listinfo/jboss-development
| 
|
|
| ___
| Jboss-development mailing list
| [EMAIL PROTECTED]
| http://lists.sourceforge.net/lists/listinfo/jboss-development
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development



___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] RabbitHole branch created

2001-06-12 Thread Scott M Stark

The cvs trunk or main branch is just the development branch. Any
future development goes there. When we want to make a release we
create a release branch to draw a line in the feature set that will
appear in the release. Any releases will be made from that branch
be they alpha, beta, or final.

I'm writing up the cvs management procedure that has only appeared
in mail form with some changes that clarify usage from my perspective.
It will be on the web site tonight.

 I am ok with this, but a bit unsure as to what I am supposed to be doing
 with the branches then...
 
 Juha you say main will be the 3.0 stuff?
 so we
 1- get rid of the new branch
 2- keep the current base as a new new branch
 3- let the main be the current branch
 
 I can see that it will minimize the number of back ports... please let me
 know what I should be doing when I start commiting if anything... I also
 understand that we all will be working on that branch... I am ok with it
 
 marcf
 
 
 |-Original Message-
 |From: [EMAIL PROTECTED]
 |[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
 |M Stark
 |Sent: Tuesday, June 12, 2001 1:10 PM
 |To: [EMAIL PROTECTED]
 |Subject: Re: [JBoss-dev] RabbitHole branch created
 |
 |
 |Your right. Making a future branch will just mean a lot of
 |merging.
 |



___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] RabbitHole branch created

2001-06-12 Thread Ole Husgaard

Hi,

I agree, and think that having _two_ unstable branches
is a pain in whatever comes to mind.
And when these branches differ more and more, merging
patches will become more and more painful.

I would suggest:

a) Calling out a code freeze on the current 2.3 series.
b) When the main branch is stable after a few days of
   freeze, that becomes 2.4.0. Bugs still present there
   can be fixed in 2.4.1, 2.4.2
c) New, unstable (MAIN branbch) 2.5 series is used
   instead of the RabbitHole branch, working towards
   the 3.0 release.


Best Regards,

Ole Husgaard.

___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



Re: [JBoss-dev] RabbitHole branch created

2001-06-12 Thread Scott M Stark

Agreed. Let's make it so. How about trying for a code freeze as of next
Monday (June 18 2001).

- Original Message - 
From: Ole Husgaard [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, June 12, 2001 1:31 PM
Subject: Re: [JBoss-dev] RabbitHole branch created


 Hi,
 
 I agree, and think that having _two_ unstable branches
 is a pain in whatever comes to mind.
 And when these branches differ more and more, merging
 patches will become more and more painful.
 
 I would suggest:
 
 a) Calling out a code freeze on the current 2.3 series.
 b) When the main branch is stable after a few days of
freeze, that becomes 2.4.0. Bugs still present there
can be fixed in 2.4.1, 2.4.2
 c) New, unstable (MAIN branbch) 2.5 series is used
instead of the RabbitHole branch, working towards
the 3.0 release.
 
 
 Best Regards,
 
 Ole Husgaard.
 
 ___
 Jboss-development mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-development
 


___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



[JBoss-dev] RabbitHole branch created

2001-06-11 Thread Scott M Stark

I created a RabbitHole branch off of the current main line for prototyping
the 3.0 generation of JBoss. You can access the branch via the command
line version of cvs using:

cvs -d :ext:[EMAIL PROTECTED]:/cvsroot/jboss co -r 
RabbitHole jboss




___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development



RE: [JBoss-dev] RabbitHole branch created

2001-06-11 Thread marc fleury



|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Scott
|M Stark
|Sent: Monday, June 11, 2001 1:38 PM
|To: JBoss Dev
|Subject: [JBoss-dev] RabbitHole branch created
|
|
|I created a RabbitHole branch off of the current main line for prototyping
|the 3.0 generation of JBoss. You can access the branch via the command
|line version of cvs using:
|
|cvs -d 
|:ext:[EMAIL PROTECTED]:/cvsroot/jboss 
|co -r RabbitHole jboss

mutex.unlock()

watch for those race conditions down the rabbit hole...

marcf
|
|
|
|
|___
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development


___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development