Re: Final phase of SVN migration - the plan
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 Friday OK with everyone? If not, I can do Saturday, but I'd prefer Friday to keep my weekend more free. How about Friday, September 23rd, 2005, at 9am my time (EDT), which is 1300h UTC? (http://www.timeanddate.com/worldclock/converted.html?month=9day=23year=2005hour=9min=0sec=0p1=43p2=0) That should give people a couple of days for scratching any last-minute itches. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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]
Re: Final phase of SVN migration - the plan
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 is now ready :) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 weekend more free. How about Friday, September 23rd, 2005, at 9am my time (EDT), which is 1300h UTC? (http://www.timeanddate.com/worldclock/converted.html?month=9day=23year=2005hour=9min=0sec=0p1=43p2=0) That should give people a couple of days for scratching any last-minute itches. No problem with that. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 the final migration. Please don't get limited with that fact. We can easily release from SVN, because when moved to SVN I'll have to change jkrelease.sh script to reflect the changes, so it might be as well a good opportunity for implementing that, cause consecutive release will be coming from SVN repository. Regards, Mladen. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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. Good idea. Weekends are usually quiet but it depends on the availability of infrastructure to do the migration. I'll keep the list informed of timings as they become clear. 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. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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. Alternatively, we can just cut 5.5.12 this weekend. I was also thinking of cutting out a 5.0.31 release before the migration. Even if we do no coding, maybe just a couple of dependency updates, and release something that can be voted as stable, I'll be happy. I don't like having the last release on that branch remain as beta ;) Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 margins. Alternatively, we can just cut 5.5.12 this weekend. I'm fine with this WE, or the end of this week. I mean, the previous build was decent already. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 about Friday, September 23rd, 2005, at 9am my time (EDT), which is 1300h UTC? (http://www.timeanddate.com/worldclock/converted.html?month=9day=23year=2005hour=9min=0sec=0p1=43p2=0) That should give people a couple of days for scratching any last-minute itches. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 Tomcat 4, this isn't anywhere near as painful as I first feared. A careful checkout from svn where you use the same directory names as you got with CVS should allow you to do a build without changing any of the scripts. Of course, you will need to manually update each module until we fix the build script to checkout from SVN. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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, because when moved to SVN I'll have to change jkrelease.sh script to reflect the changes, so it might be as well a good opportunity for implementing that, cause consecutive release will be coming from SVN repository. Thanks. My current best guess is that the migration will happen this weekend / early next week. I'll post timings when I have them. On the subject of a JK release, could you have a look at http://issues.apache.org/bugzilla/show_bug.cgi?id=35862 and if appropriate include the suggested patch it in the next release. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Final phase of SVN migration - the plan
All, The plan for the last phase is slightly different since these repositories are in pretty much constant use. The CVS repos that will be migrated are: jakarta-tomcat-connectors jakarta-tomcat-catalina jakarta-tomcat-5 jakarta-tomcat-jasper The plan is: - Submit migration request to infrastructure - Once the test migration has been done, I'll write a script to do the necessary restructuring - Run the script on the test repo - Announce that the test repo is ready for review - 48 hours later, assuming that there have been no objections I'll give 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 clash, JK takes priority. Just shout and I'll delay giving infra the go-ahead to do the final migration. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
Hi, 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. Plan looks good. Yoav --- Mark Thomas [EMAIL PROTECTED] wrote: All, The plan for the last phase is slightly different since these repositories are in pretty much constant use. The CVS repos that will be migrated are: jakarta-tomcat-connectors jakarta-tomcat-catalina jakarta-tomcat-5 jakarta-tomcat-jasper The plan is: - Submit migration request to infrastructure - Once the test migration has been done, I'll write a script to do the necessary restructuring - Run the script on the test repo - Announce that the test repo is ready for review - 48 hours later, assuming that there have been no objections I'll give 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 clash, JK takes priority. Just shout and I'll delay giving infra the go-ahead to do the final migration. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
Mark Thomas wrote: All, The plan for the last phase is slightly different since these repositories are in pretty much constant use. The CVS repos that will be migrated are: jakarta-tomcat-connectors jakarta-tomcat-catalina jakarta-tomcat-5 jakarta-tomcat-jasper The plan is: - Submit migration request to infrastructure - Once the test migration has been done, I'll write a script to do the necessary restructuring - Run the script on the test repo - Announce that the test repo is ready for review - 48 hours later, assuming that there have been no objections I'll give 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 clash, JK takes priority. Just shout and I'll delay giving infra the go-ahead to do the final migration. Good. The SVN structure you chose to use seems good (although it's not detailed in this email). Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 separation of branches/tags for each major version. To get an idea, browse svn for the modules already migrated at http://svn.apache.org/repos/asf/tomcat/ Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Final phase of SVN migration - the plan
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 usually quiet but it depends on the availability of infrastructure to do the migration. I'll keep the list informed of timings as they become clear. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SVN migration Phase 3
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 are: - Restructured the 'other' dirs so tags and branches remained separate - Used combination of spec and Tomcat version for dir names - Renamed 'trunk' using the same naming convention I will be placing this request with infra shortly but there is time to modify this structure if needs be. Mark Directory CVS Module(s) CVS Branch/Tag -- -- /tomcat/ /servletapi/ /servlet2.4-jsp2.0-tc5.x/ j-servletapi-5 HEAD /branches/ /servlet2.2-jsp1.1-tc3.x/ j-servletapi HEAD /servlet2.3-jsp1.2-tc4.x/ j-servletapi-4 HEAD /other/ /servlet2.2-jsp1.1-tc3.x/ j-servletapi All other branches /servlet2.3-jsp1.2-tc4.x/ j-servletapi-4 All other branches /servlet2.4-jsp2.0-tc5.x/ j-servletapi-5 All other branches /tags/ /servlet2.2-jsp1.1-tc3.x/ j-servletapi All 4.x tags /servlet2.3-jsp1.2-tc4.x/ j-servletapi-4 All 3.x tags /servlet2.4-jsp2.0-tc5.x/ j-servletapi-5 All 5.x tags /other/ /servlet2.2-jsp1.1-tc3.x/ j-servletapi All other tags /servlet2.3-jsp1.2-tc4.x/ j-servletapi-4 All other tags /servlet2.4-jsp2.0-tc5.x/ j-servletapi-5 All other tags - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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 types of people: those who read binary and everyone else. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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 repositories but not others is even worse. +1. Definite disservice to the subcommunity if you are straddling two source control systems. Unless we're going to do major reorganization of the code ( move directories around ) or we start some complex branches, or we have any other need where SVN is much better than CVS - I would say it's better for everyone to stick with the stable environment. I'll start to maintain a list of Want to stay in CVS for the near future, and I'll add Tomcat/ServletAPI/Watchdog to that, as I think those are the groups that this list represents :) Reasons: 1) Eclipse support (nobody has mentioned a different IDE yet) 2) A lot to do when there's no driving need to migrate. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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, commit). I'm unsure whether you can create tags/branches using it as I always do that on the command line, be it cvs or svn. IntelliJ has a plugin and the next version will have it built in. TortoiseSvn is spoken well of, and I can vouch for svn on linux/OS X, I've had no problems in the last year of use. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 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 this is a volunteer ran service - and warm bodies are always in short supply. But then again - as long as there are volunteers from communities using CVS expect the kettle to not come to a boil. Ultimately -each- project needs to make their own deceisions as to what tools and techniques they use; the ASF is merely a supprint and legal backbone and container. However SVN is a bit more modern than CVS - so you may also have some internal reasons to move to SVN at some point - see the usual cvs v.s. svn google pages. Dw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SVN migration?
Hi, We build files would need to be updated, but I suppose we could try moving one module at a time. For example, Jakarta-tomcat-site is by itself as far as dependencies. The servletapi modules would be a decent thing to move before the main Tomcat stuff, because the dependency on them is fairly clear, and we could use that move to test out our required build file changes. It's a significant effort, I'm +0 on the whole thing. I know SVN has significant advantages, but they're not significant to me ;) I'm fine with CVS... Yoav -Original Message- From: Dirk-Willem van Gulik [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 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 this is a volunteer ran service - and warm bodies are always in short supply. But then again - as long as there are volunteers from communities using CVS expect the kettle to not come to a boil. Ultimately -each- project needs to make their own deceisions as to what tools and techniques they use; the ASF is merely a supprint and legal backbone and container. However SVN is a bit more modern than CVS - so you may also have some internal reasons to move to SVN at some point - see the usual cvs v.s. svn google pages. Dw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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. So in my case it will be between -0 and -1 (-0.5) On Fri, 4 Feb 2005 08:23:35 -0500, Yoav Shapira [EMAIL PROTECTED] wrote: Hi, We build files would need to be updated, but I suppose we could try moving one module at a time. For example, Jakarta-tomcat-site is by itself as far as dependencies. The servletapi modules would be a decent thing to move before the main Tomcat stuff, because the dependency on them is fairly clear, and we could use that move to test out our required build file changes. It's a significant effort, I'm +0 on the whole thing. I know SVN has significant advantages, but they're not significant to me ;) I'm fine with CVS... Yoav -Original Message- From: Dirk-Willem van Gulik [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 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 this is a volunteer ran service - and warm bodies are always in short supply. But then again - as long as there are volunteers from communities using CVS expect the kettle to not come to a boil. Ultimately -each- project needs to make their own deceisions as to what tools and techniques they use; the ASF is merely a supprint and legal backbone and container. However SVN is a bit more modern than CVS - so you may also have some internal reasons to move to SVN at some point - see the usual cvs v.s. svn google pages. Dw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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 integration for me. So in my case it will be between -0 and -1 (-0.5) I'm -0.0. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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 cannot be honest. - Thomas Paine smime.p7s Description: S/MIME cryptographic signature
Re: SVN migration?
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 -0 for the move until Eclipse has some robust support for svn. Keith Henri Yandell wrote: 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, commit). I'm unsure whether you can create tags/branches using it as I always do that on the command line, be it cvs or svn. IntelliJ has a plugin and the next version will have it built in. TortoiseSvn is spoken well of, and I can vouch for svn on linux/OS X, I've had no problems in the last year of use. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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 from the command line so TortoiseCVS or TortoiseSVN - either works for me. Whilst there is no Ant integration and I am -1 on migration for TC5. When we do start the migration process I would be happy to test the migration of the following as the first batch jakarta-tomcat-4.0 jakarta-servletapi-4 jakarta-watchdog-4.0 (I still use it for testing releases) Running CVS and SVN side by side for a few weeks for Jasper and the connectors isn't too much of a pain. Assuming TC4 all works well, we could then migrate the remaining modules. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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 cvs. There are some plugins for svn ( and other version control tools ) - but not at the same level. 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 repositories but not others is even worse. Unless we're going to do major reorganization of the code ( move directories around ) or we start some complex branches, or we have any other need where SVN is much better than CVS - I would say it's better for everyone to stick with the stable environment. Costin Henri Yandell wrote: 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. The people still left with readable CVS modules are: mod_perl ant 2/3rds of jakarta possibly gump (though they have an svn module too) apache conference most of xml logging half of web services So I assume at some point there'll be pressure to turn off the CVS server. On the command line, svn is pretty much the same as cvs. Some bits are faster, some slower. There are various improved features (http://subversion.tigris.org/ lists them) that people have been asking for for ages with CVS. Habit-wise, the only differences I've hit are: 1) you checkout from a url, not from a cvs-root and a path. 2) tagging/branching is done by copying a directory revision (really creating a symlink-style thing in the database) and isn't applied to every file individually. Tool-wise, Subclipse is an Eclipse plugin that seems to work fine for standard development (checkout, update, diff, commit). I'm unsure whether you can create tags/branches using it as I always do that on the command line, be it cvs or svn. IntelliJ has a plugin and the next version will have it built in. TortoiseSvn is spoken well of, and I can vouch for svn on linux/OS X, I've had no problems in the last year of use. Docs are docs :) Yep, they'll need updating. Build scripts. Do you have scripts that check modules out of cvs? If so I imagine the ant support for svn might be a big deal. Unsure what it's like. Hen On Thu, 03 Feb 2005 21:32:41 -0800, Costin Manolache [EMAIL PROTECTED] wrote: 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 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 at: http://wiki.apache.org/jakarta/Migrating_20to_20Subversion The aim would be for all the tomcat modules to migrate into asf/repos/jakarta/tomcat/ so that we can have a cleaner top-level structure to the system, within that though the Tomcat community are free to choose whatever strategy fits. I've intentionally left Tomcat until last to nudge about this so as to build up some experience within Jakarta of dealing with SVN as users and as a migration. Some of you are probably already getting to grips with svn following the Commons migration. Just to provide the context for this, the Infra group are looking to move from CVS to SVN in the long term and Jakarta were far and away the main laggards in this. In the last month or so, a third of Jakarta has moved over, so that's now improving. Another question is whether the Tomcat community have any svn expertise in terms of planning svn strategies, or whether we should try to find some other committers to offer opinions. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SVN migration?
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 at: http://wiki.apache.org/jakarta/Migrating_20to_20Subversion The aim would be for all the tomcat modules to migrate into asf/repos/jakarta/tomcat/ so that we can have a cleaner top-level structure to the system, within that though the Tomcat community are free to choose whatever strategy fits. I've intentionally left Tomcat until last to nudge about this so as to build up some experience within Jakarta of dealing with SVN as users and as a migration. Some of you are probably already getting to grips with svn following the Commons migration. Just to provide the context for this, the Infra group are looking to move from CVS to SVN in the long term and Jakarta were far and away the main laggards in this. In the last month or so, a third of Jakarta has moved over, so that's now improving. Another question is whether the Tomcat community have any svn expertise in terms of planning svn strategies, or whether we should try to find some other committers to offer opinions. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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/ jakarta-tomcat-5/ jakarta-tomcat-catalina/ jakarta-tomcat-connectors/ jakarta-tomcat-jasper/ jakarta-tomcat-service/ jakarta-tomcat-site/ jakarta-tools/ I suspect you'll want to have: repos/asf/jakarta/servletapi/ and repos/asf/jakarta/tomcat/ I'm not sure if jakarta-tools is in anyway alive. The times on the files look very old. Hen On Thu, 3 Feb 2005 23:27:43 -0500, Henri Yandell [EMAIL PROTECTED] wrote: 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 at: http://wiki.apache.org/jakarta/Migrating_20to_20Subversion The aim would be for all the tomcat modules to migrate into asf/repos/jakarta/tomcat/ so that we can have a cleaner top-level structure to the system, within that though the Tomcat community are free to choose whatever strategy fits. I've intentionally left Tomcat until last to nudge about this so as to build up some experience within Jakarta of dealing with SVN as users and as a migration. Some of you are probably already getting to grips with svn following the Commons migration. Just to provide the context for this, the Infra group are looking to move from CVS to SVN in the long term and Jakarta were far and away the main laggards in this. In the last month or so, a third of Jakarta has moved over, so that's now improving. Another question is whether the Tomcat community have any svn expertise in terms of planning svn strategies, or whether we should try to find some other committers to offer opinions. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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 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 at: http://wiki.apache.org/jakarta/Migrating_20to_20Subversion The aim would be for all the tomcat modules to migrate into asf/repos/jakarta/tomcat/ so that we can have a cleaner top-level structure to the system, within that though the Tomcat community are free to choose whatever strategy fits. I've intentionally left Tomcat until last to nudge about this so as to build up some experience within Jakarta of dealing with SVN as users and as a migration. Some of you are probably already getting to grips with svn following the Commons migration. Just to provide the context for this, the Infra group are looking to move from CVS to SVN in the long term and Jakarta were far and away the main laggards in this. In the last month or so, a third of Jakarta has moved over, so that's now improving. Another question is whether the Tomcat community have any svn expertise in terms of planning svn strategies, or whether we should try to find some other committers to offer opinions. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN migration?
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. The people still left with readable CVS modules are: mod_perl ant 2/3rds of jakarta possibly gump (though they have an svn module too) apache conference most of xml logging half of web services So I assume at some point there'll be pressure to turn off the CVS server. On the command line, svn is pretty much the same as cvs. Some bits are faster, some slower. There are various improved features (http://subversion.tigris.org/ lists them) that people have been asking for for ages with CVS. Habit-wise, the only differences I've hit are: 1) you checkout from a url, not from a cvs-root and a path. 2) tagging/branching is done by copying a directory revision (really creating a symlink-style thing in the database) and isn't applied to every file individually. Tool-wise, Subclipse is an Eclipse plugin that seems to work fine for standard development (checkout, update, diff, commit). I'm unsure whether you can create tags/branches using it as I always do that on the command line, be it cvs or svn. IntelliJ has a plugin and the next version will have it built in. TortoiseSvn is spoken well of, and I can vouch for svn on linux/OS X, I've had no problems in the last year of use. Docs are docs :) Yep, they'll need updating. Build scripts. Do you have scripts that check modules out of cvs? If so I imagine the ant support for svn might be a big deal. Unsure what it's like. Hen On Thu, 03 Feb 2005 21:32:41 -0800, Costin Manolache [EMAIL PROTECTED] wrote: 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 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 at: http://wiki.apache.org/jakarta/Migrating_20to_20Subversion The aim would be for all the tomcat modules to migrate into asf/repos/jakarta/tomcat/ so that we can have a cleaner top-level structure to the system, within that though the Tomcat community are free to choose whatever strategy fits. I've intentionally left Tomcat until last to nudge about this so as to build up some experience within Jakarta of dealing with SVN as users and as a migration. Some of you are probably already getting to grips with svn following the Commons migration. Just to provide the context for this, the Infra group are looking to move from CVS to SVN in the long term and Jakarta were far and away the main laggards in this. In the last month or so, a third of Jakarta has moved over, so that's now improving. Another question is whether the Tomcat community have any svn expertise in terms of planning svn strategies, or whether we should try to find some other committers to offer opinions. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
