Hi Andy,
On Jun 28, 2010, at 1:37 AM, Andy Jefferson wrote:
I'd like to simplify the jdo repository that now contains lots of
projects that are no longer being used or maintained.
+1
The only projects in trunk that have active development are api and
tck. There are a few files that we need to keep, such as LICENSE and
JDO3.MF, but most of the rest can be moved elsewhere.
I propose we svn move the legacy projects and files to jdo/legacy or
some other name from trunk, and in trunk keep just the api and tck
projects and associated files.
Isn't this what "branches" is for ?
1. when we release 3.0 then we create a "branches/3.0" and this
contains all
files that are there currently, so if anyone really wanted to see
those other
projects then they could do in that branch.
Actually, when we create a branches/3.0 we remove the files that we're
not releasing. Take a look at the branches/2.2 for example.
2. once we have a branches/3.0 then we delete the unneeded files
from trunk, so
it comes down to just "api" and "tck" and a few build files.
That is what we want, but just need a place to put the files that are
no longer being actively developed.
Craig
3. when we release 3.1 then we create a branches/3.1 (and can delete
any files
that are not needed after that point from trunk).
...
Regards
--
Andy
DataNucleus (http://www.datanucleus.org)
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
