hi,
I'm starting to use JIRA for metadata and the available versions are the one of the Hibernate Core, which is not really suitable unless we stick the versions to the core.
Even worse, I'm not sure that EJB3 annotation should keep the same timeframe and versioning as let's say the Hibernate Console.
Any opinion?
For the hibernate-ext the versioning "scheme" is to link
the major.minor number to the core - and use the "patchlevel" or micro number to
allow a different life cycle.
so - hibernate-ext 2.1.3 is "linked" to hibernate 2.1.x
When we release hibernate-ext for hibernate 3.0.x in this schema hibernate-ext will be hibernate-ext 3.0.<release number here>
But we can get in a situatation where e.g. hibernate 3.0.1 cannot be used with hibernate-ext 3.0.3 because it requires an updated hibernate-core.
This could suggest we should just keep the versioning totally different, but the "linked' version gives a "natural visual link" which I find nice.
but no matter what we do we should provide a "hibernate-ext to hibernate-core compability 'matrix'" on our webpage - so that
people can see what works together with what...(or maybe even consider bundling the hibernate-ext package with it's corresponding hibernate core package ?)
-- Max Rydahl Andersen callto://max.rydahl.andersen
Hibernate [EMAIL PROTECTED] http://hibernate.org
JBoss Inc [EMAIL PROTECTED] http://jboss.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
