[DISCUSS] Code freeze for 2.3?

Discussion:

Howard M. Lewis Ship

2003-01-04 13:11:58 UTC

I think we really need to put 2.3 to bed. I haven't been tracking what's going on in 2.3 (I've been busy with 2.4), but I think its in our best interests to push 2.3 to completion so we can concentrate on 2.4.

In addition, you may have noticied the discussion about moving the CVS repository to Jakarta.

Bascially, it will involve an interruption, where all code MUST BE CHECKED INTO CVS. We then have to wait at least 24 hours for SourceForge to generate a nightly snapshot. The nightly snapshot can then be sent to Jakarta. Once it is installed, we will have to connect to the new repository and check everthing back out.

This is a one time process; even though we're in Incubator, not Jakarta proper, there's just one shared CVS repository.

I think it would be best if everyone reports on their current status; that is, what code they have that is not yet checked in. We can then set a cutoff date.

I'm currently working on 2.4 documentation and tests; I believe all the important features are in place. At this instance, all my changes are committed to CVS, though I'm about to make another pass or two to clean up some of the examples and tutorials.

----
Howard Lewis Ship
hlship-***@public.gmane.org
http://tapestry.sf.net

Mindbridge

2003-01-04 18:55:08 UTC

Permalink

+1

Personally, I believe I am all set with the check-ins for 2.3.

Will the move affect the branches? They will be moved to Jakarta as well, I guess?

Also, I presume that the renaming will be done in 2.4?

Best regards,
-mb

----- Original Message -----
From: Howard M. Lewis Ship
To: Tapestry Contrib
Sent: Saturday, January 04, 2003 3:11 PM
Subject: [Tapestry-contrib] [DISCUSS] Code freeze for 2.3?

I think we really need to put 2.3 to bed. I haven't been tracking what's going on in 2.3 (I've been busy with 2.4), but I think its in our best interests to push 2.3 to completion so we can concentrate on 2.4.

In addition, you may have noticied the discussion about moving the CVS repository to Jakarta.

Bascially, it will involve an interruption, where all code MUST BE CHECKED INTO CVS. We then have to wait at least 24 hours for SourceForge to generate a nightly snapshot. The nightly snapshot can then be sent to Jakarta. Once it is installed, we will have to connect to the new repository and check everthing back out.

This is a one time process; even though we're in Incubator, not Jakarta proper, there's just one shared CVS repository.

I think it would be best if everyone reports on their current status; that is, what code they have that is not yet checked in. We can then set a cutoff date.

I'm currently working on 2.4 documentation and tests; I believe all the important features are in place. At this instance, all my changes are committed to CVS, though I'm about to make another pass or two to clean up some of the examples and tutorials.

----
Howard Lewis Ship
hlship-***@public.gmane.org
http://tapestry.sf.net

Howard M. Lewis Ship

2003-01-04 19:27:15 UTC

Permalink

Yes, I believe we'll end up just moving code over to Jakarta as-is. We should be able to reconnect to our existing branches after the move.

I'm waiting to hear from Malcolm at this point, he's the only one with any outstanding work, and he probably has nothing right now.

We then wait for a bit to ensure that we have a good snapshot that isn't missing anything.
----- Original Message -----
From: Mindbridge
To: Howard M. Lewis Ship ; Tapestry Contrib
Sent: Saturday, January 04, 2003 1:55 PM
Subject: Re: [Tapestry-contrib] [DISCUSS] Code freeze for 2.3?

+1

Personally, I believe I am all set with the check-ins for 2.3.

Will the move affect the branches? They will be moved to Jakarta as well, I guess?

Also, I presume that the renaming will be done in 2.4?

Best regards,
-mb

----- Original Message -----
From: Howard M. Lewis Ship
To: Tapestry Contrib
Sent: Saturday, January 04, 2003 3:11 PM
Subject: [Tapestry-contrib] [DISCUSS] Code freeze for 2.3?

I think we really need to put 2.3 to bed. I haven't been tracking what's going on in 2.3 (I've been busy with 2.4), but I think its in our best interests to push 2.3 to completion so we can concentrate on 2.4.

In addition, you may have noticied the discussion about moving the CVS repository to Jakarta.

Bascially, it will involve an interruption, where all code MUST BE CHECKED INTO CVS. We then have to wait at least 24 hours for SourceForge to generate a nightly snapshot. The nightly snapshot can then be sent to Jakarta. Once it is installed, we will have to connect to the new repository and check everthing back out.

This is a one time process; even though we're in Incubator, not Jakarta proper, there's just one shared CVS repository.

I think it would be best if everyone reports on their current status; that is, what code they have that is not yet checked in. We can then set a cutoff date.

I'm currently working on 2.4 documentation and tests; I believe all the important features are in place. At this instance, all my changes are committed to CVS, though I'm about to make another pass or two to clean up some of the examples and tutorials.

----
Howard Lewis Ship
hlship-***@public.gmane.org
http://tapestry.sf.net

Malcolm Edgar

2003-01-05 20:38:19 UTC

Permalink

Malcolm Edgar: +1

Post by Mindbridge
Subject: [Tapestry-contrib] [DISCUSS] Code freeze for 2.3?
Date: Sat, 4 Jan 2003 08:11:58 -0500
I think we really need to put 2.3 to bed. I haven't been tracking what's
going on in 2.3 (I've been busy with 2.4), but I think its in our best
interests to push 2.3 to completion so we can concentrate on 2.4.
In addition, you may have noticied the discussion about moving the CVS
repository to Jakarta.
Bascially, it will involve an interruption, where all code MUST BE CHECKED
INTO CVS. We then have to wait at least 24 hours for SourceForge to
generate a nightly snapshot. The nightly snapshot can then be sent to
Jakarta. Once it is installed, we will have to connect to the new
repository and check everthing back out.
This is a one time process; even though we're in Incubator, not Jakarta
proper, there's just one shared CVS repository.
I think it would be best if everyone reports on their current status; that
is, what code they have that is not yet checked in. We can then set a
cutoff date.
I'm currently working on 2.4 documentation and tests; I believe all the
important features are in place. At this instance, all my changes are
committed to CVS, though I'm about to make another pass or two to clean up
some of the examples and tutorials.
----
Howard Lewis Ship
http://tapestry.sf.net

Andrew C. Oliver

2003-01-05 23:45:46 UTC

Permalink

Hi all,

*** please send your requested apache account designations to me
(acoliver-1oDqGaOF3Lkdnm+***@public.gmane.org).

This will serve two purpose:

1. cvs login (until you make it not require you to)
2. unix user on cvs.apache.org and jakarta.apache.org (which are really
called other things icarus and daedalus)
3. @apache email address. (hence mine is acoliver)

*** also send the email address that you want the account password sent to.

I will aggregate these and send the request to root to have them created.

Thank you,

Andy

Post by Malcolm Edgar
Malcolm Edgar: +1

Post by Mindbridge
Subject: [Tapestry-contrib] [DISCUSS] Code freeze for 2.3?
Date: Sat, 4 Jan 2003 08:11:58 -0500
I think we really need to put 2.3 to bed. I haven't been tracking
what's going on in 2.3 (I've been busy with 2.4), but I think its in
our best interests to push 2.3 to completion so we can concentrate on
2.4.
In addition, you may have noticied the discussion about moving the CVS
repository to Jakarta.
Bascially, it will involve an interruption, where all code MUST BE
CHECKED INTO CVS. We then have to wait at least 24 hours for
SourceForge to generate a nightly snapshot. The nightly snapshot can
then be sent to Jakarta. Once it is installed, we will have to
connect to the new repository and check everthing back out.
This is a one time process; even though we're in Incubator, not
Jakarta proper, there's just one shared CVS repository.
I think it would be best if everyone reports on their current status;
that is, what code they have that is not yet checked in. We can then
set a cutoff date.
I'm currently working on 2.4 documentation and tests; I believe all
the important features are in place. At this instance, all my changes
are committed to CVS, though I'm about to make another pass or two to
clean up some of the examples and tutorials.
----
Howard Lewis Ship
http://tapestry.sf.net

_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-contrib mailing list
https://lists.sourceforge.net/lists/listinfo/tapestry-contrib

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf