> -----Message d'origine----- > De : Ted Husted > Envoyé : dimanche 16 janvier 2005 13:21 > À : ibatis-dev@incubator.apache.org > Objet : SVN Recap (was RE: ASF TODO [short] (was ASF TODO [long])) > > Just to recap, > > * I'd suggest that the SVN structure represent the subproject/release > structure, where the subprojects are > > ** java/mapper > ** java/dao > ** java/docs > ** java/jpetshore > > ** cs/mapper > ** cs/dao > ** cs/docs > ** cs/npetshop > ** cs/tutorial > > ** site > > If we later change the release structure, we can change the SVN > structure to match, since moving things around in Subversion is cheap. > > * I'd suggest that we tag each subproject release before it is rolled. > Ideally, the tag should identify exactly what goes into a given subproject > release. > > * Obviously, I don't care if we keep the tags in subdirectories or in a > master directory at the top. My only concern is that it is easy to tag > only the resources that pertain to a given release. +1 > * I haven't done any SVN tagging myself, but someone who does said it was > easier to create the tags if we we used a > > /$subproject > ./tag > ./trunk > > structure. Of course, it might be just as easy to keep them all at the > root. I haven't had a chance to try yet. I have done a tag for the last .NET release and it's very easy you can put your tag in any directory (root ou sub).
> * If someone wants to forward this post to a SVN guru, that would work for > me :) > > It will be a couple of days before the repos are rolled over, and we don't > have to start shuffling things around right away, so time is not of the > essence. > > -Ted. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.12 - Release Date: 14/01/2005
