Hi,
Reminder that this is about 90 minutes from now ;)
Yoav
--- Yoav Shapira [EMAIL PROTECTED] wrote:
Hi,
I'm fine with this WE, or the end of this week. I mean, the previous
build was decent already.
I just looked at the changelog for 5.5.12, it's a nice collection of stuff.
Is
Yoav Shapira wrote:
Hi,
Reminder that this is about 90 minutes from now ;)
All done ?
If so, the migration is now ready :)
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
Not done yet -- tagging in a couple of minutes, then a few more to do the
checkout/download/build... ;) But almost there.
Yoav
--- Remy Maucherat [EMAIL PROTECTED] wrote:
Yoav Shapira wrote:
Hi,
Reminder that this is about 90 minutes from now ;)
All done ?
If so, the migration
Hi,
OK, the release is tagged, cut, and uploaded. Formal announcements coming in a
few hours..
Yoav
--- Remy Maucherat [EMAIL PROTECTED] wrote:
Yoav Shapira wrote:
Hi,
Reminder that this is about 90 minutes from now ;)
All done ?
If so, the migration is now ready :)
Rémy
Yoav Shapira wrote:
Hi,
I'm fine with this WE, or the end of this week. I mean, the previous
build was decent already.
I just looked at the changelog for 5.5.12, it's a nice collection of stuff.
Is Friday OK with everyone? If not, I can do Saturday, but I'd prefer Friday
to keep my
Mark Thomas wrote:
All,
The plan for the last phase is slightly different since these
repositories are in pretty much constant use.
I know there is a plan to do a JK release this week. If there is a
timing clash, JK takes priority. Just shout and I'll delay giving infra
the go-ahead to do
Mark Thomas wrote:
Yoav Shapira wrote:
If possible, it'd be nice to establish a quiet window, say 24 hours,
during
which we shall not commit anything, and infra will do the real
repository move.
That will help eliminate the possibility of lost/clashed commits and
related
wasted time.
Hi,
Do we do a new Tomcat 5.0.12 build (which will be voted on this time)
before the migration ? We'll have to change build scripts after that,
Yes, I'd like to do a new 5.5.12. That's one of the reasons I asked for
timings, once they're known, so we can work with nice margins.
Yoav Shapira wrote:
Hi,
Do we do a new Tomcat 5.0.12 build (which will be voted on this time)
before the migration ? We'll have to change build scripts after that,
Yes, I'd like to do a new 5.5.12. That's one of the reasons I asked for
timings, once they're known, so we can work with nice
Hi,
I'm fine with this WE, or the end of this week. I mean, the previous
build was decent already.
I just looked at the changelog for 5.5.12, it's a nice collection of stuff.
Is Friday OK with everyone? If not, I can do Saturday, but I'd prefer Friday
to keep my weekend more free. How
Remy Maucherat wrote:
Do we do a new Tomcat 5.0.12 build (which will be voted on this time)
before the migration ? We'll have to change build scripts after that,
and I also would have to change the way I work with the repository,
which could introduce problems.
Based on experience with
Mladen Turk wrote:
Mark Thomas wrote:
I know there is a plan to do a JK release this week. If there is a
timing clash, JK takes priority. Just shout and I'll delay giving
infra the go-ahead to do the final migration.
Please don't get limited with that fact.
We can easily release from SVN,
the live migration
- Shortly after this, CVS will be locked, the live SVN migration will
take place (including the restructuring script) and the migration to
SVN will be complete
I know there is a plan to do a JK release this week. If there is a
timing clash, JK takes priority. Just shout
the go ahead to infrastructure to do the live migration
- Shortly after this, CVS will be locked, the live SVN migration will
take place (including the restructuring script) and the migration to
SVN will be complete
I know there is a plan to do a JK release this week. If there is a
timing
to infrastructure to do the live migration
- Shortly after this, CVS will be locked, the live SVN migration will
take place (including the restructuring script) and the migration to SVN
will be complete
I know there is a plan to do a JK release this week. If there is a
timing clash, JK takes
Remy Maucherat wrote:
Good. The SVN structure you chose to use seems good (although it's not
detailed in this email).
I left it out for the sake of brevity. It is pretty much as per
http://marc.theaimsgroup.com/?l=tomcat-devm=112250656230577w=2 apart
from a few naming changes and better
Yoav Shapira wrote:
If possible, it'd be nice to establish a quiet window, say 24 hours, during
which we shall not commit anything, and infra will do the real repository move.
That will help eliminate the possibility of lost/clashed commits and related
wasted time.
Good idea. Weekends are
It is now the turn of the servletapi repositories.
Given the previously expressed views on how these might be better
named and my experience of the migration process so far I have
modified my plan for servletapi part of the repository. The new
version is at the end of this mail.
Changes
On Feb 5, 2005, at 1:57 PM, Henri Yandell wrote:
1) Eclipse support (nobody has mentioned a different IDE yet)
http://subclipse.tigris.org/
--
===
Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/
There 10
On Fri, 04 Feb 2005 19:16:03 -0800, Costin Manolache
[EMAIL PROTECTED] wrote:
I like SVN a lot - and for a new project probably I would choose it if
there is a choice - sf.net or other places are cvs only. But I don't
think all the pain for switching tomcat is justified, and switching few
Just noticed an email on commons-dev.
Subclipse doesn't support the synchonize feature yet.
Hen
On Fri, 4 Feb 2005 02:57:35 -0500, Henri Yandell [EMAIL PROTECTED] wrote:
Tool-wise, Subclipse is an Eclipse plugin that seems to work fine for
standard development (checkout, update, diff,
On Fri, 4 Feb 2005, Henri Yandell wrote:
I've not heard anything about it being mandatory yet, but the numbers
speak for themselves.
It is not mandatory at this time. And won't be anytime soon.
So I assume at some point there'll be pressure to turn off the CVS server.
There is that - as
[mailto:[EMAIL PROTECTED]
Sent: Friday, February 04, 2005 3:25 AM
To: Tomcat Developers List; Henri Yandell
Subject: Re: SVN migration?
On Fri, 4 Feb 2005, Henri Yandell wrote:
I've not heard anything about it being mandatory yet, but the numbers
speak for themselves.
It is not mandatory
:[EMAIL PROTECTED]
Sent: Friday, February 04, 2005 3:25 AM
To: Tomcat Developers List; Henri Yandell
Subject: Re: SVN migration?
On Fri, 4 Feb 2005, Henri Yandell wrote:
I've not heard anything about it being mandatory yet, but the numbers
speak for themselves.
It is not mandatory
Henri Gomez wrote:
Well I'm using Eclipse and if the SVN support is not 100% supported,
I'm a little worry about switch tomcat / jasper /
jakarta-tomcat-connectors on SVN.
Yes, I'm also using Eclipse :( Whatever productivity is gained are over
CVS will probably get eaten up by less efficient tool
On Feb 4, 2005, at 10:29 AM, Remy Maucherat wrote:
Whatever productivity is gained are over CVS will probably get eaten
up by less efficient tool integration for me.
Right, Ant doesn't have a svn task yet. Isn't that reason enough not to
jump ship yet?
--
Sandy McArthur
He who dares not offend
The last time I looked at the Eclipse SVN plugin it just called out to
the native svn binary to do the real work-- I wonder how well anything
but basic operations can be integrated until it is using a java svn
client. Then again, maybe that has been written since I looked at it
last. I'd be
Sandy McArthur wrote:
On Feb 4, 2005, at 10:29 AM, Remy Maucherat wrote:
Whatever productivity is gained are over CVS will probably get eaten
up by less efficient tool integration for me.
Right, Ant doesn't have a svn task yet. Isn't that reason enough not to
jump ship yet?
I do all my CVS stuff
Well, numbers are statistics do speak for themself - but may tell
different things. Apache may have most projects in SVN, but the world
has most projects in cvs. And most tools (finally) have some good, first
class built-in support for CVS, most people are (finally) familiar
enough with using
Just wondering if the Tomcat community have any thoughts on a
migration to Subversion?
The process seems pretty easy, though Tomcat may be more complicated
than the usual CVS module. Infra have the process documented at:
http://www.apache.org/dev/cvs2svn.html
The Jakarta status is in the wiki
Just to add, as far as I know the following are the Tomcat modules:
jakarta-servletapi/
jakarta-servletapi-4/
jakarta-servletapi-5/
jakarta-tomcat/
jakarta-tomcat-4.0/
Is this mandatory ? I suspect there'll be a lot of build
script/doc/habits/tool changes involved. CVS is working reasonably well
at the moment, and a lot of tools have (finally) very good support for it.
Costin
Henri Yandell wrote:
Just wondering if the Tomcat community have any thoughts on a
I've not heard anything about it being mandatory yet, but the numbers
speak for themselves.
The www.apache.org site has 24 coding projects. There are 22 projects
listed on the svn.apache.org/viewcvs.cgi page. 2 of those are dead, so
20 out of 24 ASF projects have an svn presence of some kind.
33 matches
Mail list logo
