On 1/24/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
> Anybody have other objections to moving JPA/JDO code out of the sandbox?
Yes, I know it's a little annoying, but I am against moving that code
into the main src tree. If working out of the sandbox is causing
problems then I think the other option is a branch, but moving the code
into the main src tree, both for Weblogger and Planet does not seem like
the best idea to me.
Granted that there are concerns from a technical point of view around
having to change the build process and making sure that code doesn't go
into normal builds/releases, but to a larger degree I think it's just
not a practice we should endorse. We can't set a precedence of allowing
experimental code to go into the main src tree just to make it easier on
the people working on that code, that's specifically why we have a
sandbox and can provide different branches in the repository.
I believe I have sufficiently addressed your specific concerns and I
don't have any problem with allowing experimental code under the src
directory as long as it is clearly marked and does not affect
production code, but...
That said, I do not object to doing the remaining JPA work in a branch
and it sounds like now might be a good time to create that branch. So,
I propose that we create a roller_jpa branch and within that branch
move JPA from sandbox to src and apps/planet/src. Once JPA is solid
and supportable, we'll merge back. Any objections to that plan?
- Dave
