Francesco, now that we have a Mercurial repository (thanks Joern!)
what's your thought on how to manage it? Given the berlios.de site,
I could see a few ways of doing things:
- Keep on using hg.exit1.org as the main source repository, and ask Joern
to set up HTTP for anonymous read access.
- Keep on using hg.exit1.org as the main source repository, but set it up
to automatically push changes to berlios.de, and use the HTTP server
there for anonymous read access.
- Thank Joern profusely for providing a server for so long (: and shift
everything over to berlios.de.
As for the directory structure, currently we have something like:
(root)
+-- .hg (repository data)
+-- transcode
+-- branches
| +-- transcode_1_0
| +-- transcode_1_1
| +-- (etc.)
+-- tags
| +-- release_1_0_0
| +-- release_1_1_0
| +-- (etc.)
+-- trunk
+-- libtc
+-- src
+-- (etc.)
One downside of this structure is that it takes up tons of disk space. (:
So what I'm thinking would be useful is to:
(1) Move everything from transcode/trunk/ up to the root directory.
(2) Delete all the directories in tags/ and add a native Mercurial tag
for each one.
(3) Export all the changes for each branch in branches/, readd them on
native Mercurial branches(*) from the main source code, then
delete everything under the branches/ directory.
(*) For (3) above, we could also theoretically use multiple separate
repositories as the Mercurial manual suggests, but I'm not sure how
one would do that remotely.
How does this sound? If it's okay with you, I think it might be best to
just export everything and create a new repository from scratch with the
new layout, so people don't have to worry about files being in different
places depending on what version they're looking at. I can do that on
my end and then provide a copy of the new repository to Joern (or to you
for berlios, depending on where you want to put the final repository),
so just let me know your thoughts and I'll get started on it.
--Andrew Church
achu...@achurch.org
http://achurch.org/
