-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rodent of Unusual Size wrote:
| Daniel John Debrunner wrote:
|
|>derby/code/{trunk,tags,branches}
|>derby/site/{trunk,tags,branches}
|>
|>I believe this is a good setup because it would seem to me that
|>branching of the code would typically be independent of branching
|>of the site. Though I'm not sure what it would mean to branch the
|>site, would that ever occur?
|
|
| maybe. something like that happened for the http server, for instance;
| both 1.3 and 2.0 are supported and deployed, and the docco is distinctly
| different. separate modules were created for them, but they use cvs
| rather than svn. branching is simpler/easier in svn, i believe.
I can see the documentation branching, but there would still be a single
web-site that has N versions of the documentation. Maybe in that case
only a sub-set of the site files would be branched, the documentation.
Or maybe it's all branched and the pages in the trunk are changed to
add additional links to the branched files that make sense to have on
the web-site.
Just to be clear can we define the expected contents of these sections as
derby/code
derby code
derby tests (in the future)
derby/site
web site pages
derby documentation
derby techincal papers
Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBJLUKIv0S4qsbfuQRAkB8AKDTd2jUEzs0Rx5Sc3PvpE7hXyJJ1wCgiPbM
eH/RwCqd91LmkfJqCdG5Xvs=
=ezq1
-----END PGP SIGNATURE-----
