[X] Option 2: Put all things Derby into a single tree
( derby/{trunk,tags,branches}/{<code>,<pages>} )
> -----Original Message-----
> From: Daniel John Debrunner [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 20, 2004 9:52 AM
> To: derby-dev
> Subject: [VOTE] on repository layout
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The import of the derby code is looming; it would be nice to have a
> decision about the repository structure. So let's measure consensus
the
> Apache way and vote on it. :) I think that we can collate the results
> next Monday (8/23); our community is still small enough that we don't
> need to wait a long time to close the vote.
>
> [ ] Option 1: Keep the code and site pages in separately-versionable
> trees ( derby/site/{trunk,tags,branches}/<pages> and
> derby/code/{t,t,b}<code> )
>
> [ ] Option 2: Put all things Derby into a single tree
> ~ ( derby/{trunk,tags,branches}/{<code>,<pages>} )
>
>
> Dan.