Hi all, I haven't heard any screaming so I'm going to go ahead and create the branch later today (read this is your last chance).
-mike On Wed, Oct 1, 2008 at 3:08 PM, Michael Dick <[EMAIL PROTECTED]>wrote: > Hi, > > +1 to creating a new branch for 1.x work. I don't anticipate a 1.3.0 > release in the near future, but it will be nice to have the branch in the > mean time. > > WRT timing, I'd be happy with the middle or the end of October. I don't > have any major work items in in a half-baked state that I'd want in 1.3 and > trunk (waiting to hear from others though). > > -mike > > > On Tue, Sep 30, 2008 at 11:33 AM, Craig L Russell <[EMAIL PROTECTED]>wrote: > >> Hi Kevin, >> >> Good idea to branch and distinguish JPA 1.0 from JPA 2.0 specification >> level. >> >> I'd also like to hear from the user community about both the strategy and >> the timing of branching. >> >> Craig >> >> >> On Sep 30, 2008, at 9:10 AM, Kevin Sutter wrote: >> >> Due to the upcoming JPA 2.0 development activities, the OpenJPA svn >>> repository needs to make a few changes. Since the JPA 2.0 changes could >>> be >>> disruptive to current JPA 1.0 processing (at least during initial >>> development), I would like to create a 1.3.x service branch. This 1.3.x >>> branch would indicate the end of new development based on the JPA 1.0 >>> specification. This 1.3.x branch could be used for any necessary support >>> activities (or even a potential release, if necessary), but the mainline >>> trunk would now become the basis for JPA 2.0 development >>> (2.0.0-SNAPSHOT). >>> >>> All new development activity would continue in trunk, just like the past. >>> But, we would also have the ability to start experimenting with some of >>> the >>> new features that have been identified in the early drafts of the JPA 2.0 >>> specification. Granted, we only have the single Early Draft Review >>> version >>> of the JPA 2.0 spec, but it's at least a start. Even if we have to >>> modify a >>> few things along the way, at least we're getting experience with the new >>> specification. And, we can initiate a roadmap for the new features and >>> hopefully encourage new participation by the diverse OpenJPA community. >>> >>> We need to determine the "best date" for this cutover. Since I'm not >>> sure >>> on the current development activities of the OpenJPA developers, let's >>> use >>> this thread for the discussion. Since the end of Sept is fast >>> approaching, >>> let's shoot for Friday, Oct 31 as the cutover date. >>> >>> Comments or suggestions are welcome! >>> >>> Kevin >>> >> >> Craig L Russell >> Architect, Sun Java Enterprise System http://db.apache.org/jdo >> 408 276-5638 mailto:[EMAIL PROTECTED] >> P.S. A good JDO? O, Gasp! >> >> >
