One clarification - there are two issues here - (1) using Apache vs.
SourceForge download servers and (2) using Apache vs. Sourceforge
repository. I guess my concern is mainly about (1) ... for (2) we can
go either way.
Andrus
On Apr 7, 2006, at 5:53 PM, Andrus Adamchik wrote:
From the purely practical standpoint, when 1.2 goes final, I wonder
if we should keep the maintenance branch on SourceForge. This way
we'll have a clean cutoff point.
I think releasing org.objectstyle.cayenne.* stuff from Apache is
confusing (if not legally wrong). I know other incubating projects
are doing that (roller), but at some point we will graduate from
the Incubator... and will still want to maintain 1.2.x branch at
that time.
So once we get setup @apache, I suggest to initially only migrate
the new stuff (i.e. JPA), and move the core framework when we are
ready to change the package names.
Does it make sense? I think we are pretty close to the 1.2 RC when
the total code freeze starts, and then we can actually branch it out.
Andrus
