[hibernate-dev] Hibernate Planning

[Steve Ebersole]

1) If commons-annotations *does not* rely on hibernate-core in any way
then I'm fine to break it it back out if that makes sense.  However
y'all need to be *extremely* careful about this and making sure about
compatibility.  The whole idea about moving these things back together
was to make the compatibility "matrix" more manageable.  Making
incompatible changes in dependency common to core/annotations/em and
search effectively makes those things incompatible as well.  Same for
integrating it into annotations.

2) From now on we will be doing "full" releases.  Starting with 3.5,
that "major release" moniker will apply across all of the modules now
bundled into core (annotations, em, envers) meaning that there will be
no API incompatibilities introduced *within* a major rev across all
those modules.  JPA2 development will be 3.5.  The initial 3.5 releases
(alphas, betas, crs) will revolve around JPA2 support.

3) Depends what you mean by "handling".  If you mean deciding what
features, when and such (aka planning) then that's something we will all
need to do together.  If you mean actually performing releases I totally
understand that you want to do them and will graciously step aside for
you to fulfill that dream :)  For real, we will probably all be doing
some.

4) Yes, the basic planning is done from the core side of things, minus a
few minor features.

I am always on IRC, so we can chat whenever y'all want; y'all are the
ones that seem IRC-averse ;)


-  

Steve Ebersole
Project Lead
http://hibernate.org
steve at hibernate.org

Principal Software Engineer
JBoss, a division of Red Hat
http://jboss.com
http://redhat.com
steve.ebersole at jboss.com
steve.ebersole at redhat.com


On Mon, 2009-03-23 at 11:10 +0100, Hardy Ferentschik wrote:
> Hi there,
> 
> I would like to start a discussion around a few 'management' questions.
> 
> 1. What shall we do with commons-annotations? commons-annotations became a
>     module of Core (core/trunk/commons-annotations) when we moved  
> Annotations
>     and EntityManager into Core. Emmanuel, raised the question whether it  
> should
>     be really in Core or whether we should keep it seperate as independed  
> library.
>     I could also imagine to just move it back into Annotations itself. I  
> don't
>     think any other project really denpends on it (any project using  
> commons-annotations
>     uses also annotations). This would mean one less module/project to  
> manage.
> 
> 2. Some changes to Hibernate Search require also changes to  
> Annotations/EntityManager.
>     This raises the question on how we handle releases now that these  
> modules are part
>     of the Core. Will we still do separate releases for these modules or  
> are we from now on
>     just doing 'full' Hibernate releases (meaning we always release Core  
> with all its modules)?
>     This question is especially interesting since we soon will start with  
> JPA 2 development.
> 
> 3. Who is handling releases? So far Steve was basically driving the Core  
> releases, whereas Emmanuel
>     and I where looking after EntityManager, Annotations and Search. How  
> shall we do it now?
> 
> 4. What is the current status on Hibernate 3.5? Is there already a  
> (interim) release planned?
> 
> It would be great to get some feedback and maybe we should at some stage  
> have a chat.
> 
> --Hardy
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev