From kde-core-devel Sun Feb 20 21:19:01 2005 From: Thiago Macieira Date: Sun, 20 Feb 2005 21:19:01 +0000 To: kde-core-devel Subject: Re: Announcing test svn import Message-Id: <200502201819.01728.thiago () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=110893432025022 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2258045.MlItfix0Wu" --nextPart2258045.MlItfix0Wu Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cornelius Schumacher wrote: >- I would prefer /trunk/core over /trunk/KDE. KDE is more than the core >modules after all. Makes sense. Do you think /branches/KDE should be renamed /branches/core as well? The=20 sole reason I thought of /trunk/KDE was to keep the name in both areas. But, then again, since we won't have a /branches/extragear=20 or /branches/playground, it doesn't matter. >- I don't really see the need for a "work" directory, separating between >temporary and released branches seems to be a bit artificial. A >temporary branch will disappear when it isn't needed anymore in any >case, so it won't clutter the directory it's in, be it "branches" or >something else. Okay. As I said, "work" was an invention of mine. I don't know anyone who=20 uses that. I thought of it after taking a look at /branches before I started moving=20 things around. Granted, there were a lot of superfluous branches there,=20 but even listing the directory was slow. Take a look: https://svn.kde.org/viewcvs/branches/?rev=3D343811 >- Branches should probably include one or several subdirectories named >after the project. So it isn't needed to come up with super-creative >branch names. kwebdev/quanta/make-it-cool sounds fine to me. I don't like the idea of generic branch names for two reasons, but I won't= =20 intrude in other projects' decisions: 1) it tells nothing about what the branch is, except for those who agreed=20 to create it 2) reutilisation of the same name #1 isn't an issue if no-one but the maintainers is supposed to be using=20 that branch. #2 isn't really an issue in Subversion, since names can be reused again=20 and again. >- "tags" shouldn't be named "releases". There are lots of tags which >don't correspond to a release, but just identify some kind of snapshot. True, but not many people use tags. They just remember the last revision=20 they merged stuff. Since it's now a global value, it's much easier to=20 remember than to find out each individual file's revision. You can use properties for that too (that's how svnmerge works anyways). >A "releases" subdirectory in "tags" might make sense, though. /tags/releases/KDE/4.0 sounds a bit long for me. Same thing=20 for /trunk/playground/artwork/plastik2=20 or /trunk/extragear/multimedia/k3b/src. I'd much rather see people use "tags" inside /work than /releases. Out of curiosity, here's how the Samba Subversion repository is layed out=20 (http://websvn.samba.org/cgi-bin/viewcvs.cgi/): / branches/ SAMBA_2_2/ SAMBA_2_2_RELEASE/ SAMBA_3_0/ SAMBA_3_0_RELEASE/ SAMBA_3_1_RELEASE/ SAMBA_4_0/ tmp/ SAMBA_3_2_MERGE/ ... hooks/ tags/ ... release-2-2-10/ release-2-2-11/ release-2-2-12/ ... test/ trunk/ docs/ examples/ ... source/ ... Remember that's one repository for a single program. For KDE, we're=20 talking about lots of programs being released, from the same repository. =2D-=20 Thiago Macieira - thiago (AT) macieira (DOT) info PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 5. Swa he g=C3=A9anhwearf t=C3=B3 timbran, and hwonne he c=C3=B3m, l=C3=A1!= Unix cw=C3=A6=C3=B0 "Hello,=20 World". =C7=BCfre =C7=BDghwilc w=C3=A6s gl=C3=A6d and seo woruld w=C3=A6s f= r=C3=A9o. --nextPart2258045.MlItfix0Wu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBCGP7FM/XwBW70U1gRAoM0AJ9Uuat0DN6/oTLLBo0QO828naYswwCfSg3v WHY7zWC/i8D45uOa4r5j8Ho= =a6WA -----END PGP SIGNATURE----- --nextPart2258045.MlItfix0Wu--