Comments below...
On 1/24/07, Allen Gilliland <[EMAIL PROTECTED]> wrote:
> 1. Stay the course. JPA continues as a second class citizen, remains in > the sandbox, and might not work, subject to feature development in the > main line. "Someone" will have to come along after a checkin to make > sure that the sandbox code continues to work. I think this has to be the path until it's been fully decided that JPA is going to be a fully supported backend for Roller.
It's time to make that decision.
> 2. Switch out Hibernate API and use JPA API as the one API that is > supported by Roller. Note that since Hibernate has a JPA implementation, > current users of Roller could continue to use Hibernate but with a > different API. > > 3. Support both JPA and Hibernate native APIs in Roller. New feature > development would have to test in both JPA and Hibernate modes before > checking in. Definitely -10 from me. I am not willing to officially endorse multiple backends for the project, no matter how easy it may seem. I think we definitely need to pick a single solution to endorse and that's it.
Same here. Been there, done that, burned the t-shirt. I don't want Roller developers to have to implement every feature in multiple back-ends.
I am a little surprised to hear that, but I guess it was miscommunication. From the very beginning I think that everyone was in agreement that we would only officially support a single backend, so if it was going to be something other than the current Hibernate impl then that meant replacement
Yeah, I thought that was the consensus too.
Just because it's working doesn't mean it's time to commit it to the main src tree and endorse it. Assuming that the community has properly discussed the issue and come to a decision (which hasn't happened yet) and assuming all the proper testing and verification has been done (which hasn't happened yet) then we can talk about how/when to commit it to the main src tree. IMO your suggestion that it's ready to go into the main src tree is a bit premature.
I disagree with Allen here. I'm OK with experimental code in trunk and under src as long as it is clearly marked and does not interfere with propduction code.
For one thing, can the JPA backend work on jdk 1.4? I haven't worked with any of the JPA stuff myself, but I am assuming that it requires Java 5 which means that we would be forcing all Roller users onto a new jdk version. So that's an important decision which will affect the timing.
It does work with Java 1.4.2 so that's not a major issue.
The second part of the timing issue just has to due with stability and good practices for releases. IMO swapping out the whole backend on a minor release such as 3.1 -> 3.2 is not something that mature products do. A change like this warrants a major release, so assuming it is ready it should be scheduled for the 4.0 release and not sooner. This then suggests that we should take all the current code in the trunk and make a 3.2 release out of it, which would still be premature considering that 3.1 hasn't even gone out.
Yes, I agree. A new back-end should not be introduced in a point release. I'm going to propose today a Roller 4.0 release with JPA so that we can have the discussion and hopefully make a decision. - Dave
