We refer to svn in various places. Main web site, docs, BUILDING.txt etc. The issue is when do we update the various docs. The main website we can update whenever, but the version specific docs normally only get updated when we do a release.
My suggested solution is to do the migration and once we are happy that the git repo is correct and we formally make it the master then we: - update the main web site ASAP - [ANNOUNCE] email to the community - Release 9.0.x, 8.5.x and 7.0.x ASAP with updated docs that refer to git rather than svn. An added benefit is going through the release process soon after the migration should highlight any issues (I'm not expecting any) quickly. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
