(non-binding)
OK, although jumping in late I think the height of the number does not
really matter. The only point here (maybe it's just me) that I'm searching
maven for the latest versions more frequently than the homepage itself --
It's always a little bit confusing if there are big gaps -- +1
I think I can speak for everyone here that our current release has
taken a long time to stabilize, and finalize (and we are not even
there yet!). Given that we are all volunteers and many of us also try
to have a family and/or social life, it is what it is.
When we hit RC status, we should be
+1
-igor
On Mon, Aug 29, 2011 at 3:15 PM, Martijn Dashorst
martijn.dasho...@gmail.com wrote:
I think I can speak for everyone here that our current release has
taken a long time to stabilize, and finalize (and we are not even
there yet!). Given that we are all volunteers and many of us also
-1
I propose that Wicket modules be released separately. Projects that are small
can be released as a monolithic whole. Wicket is no longer a small project.
With the changes that went into 1.5 to make it easier to program, there should
be very few changes in the core modules.
Maven
non-binding
-1 to independent module versioning. I don't want to have a compatibility
matrix like Hibernate's (
http://community.jboss.org/wiki/HibernateCompatibilityMatrix).
+1 to semantic versioning (http://semver.org/)
-1 to jump to 6.0, unless it features some major architectural change
I'm revising my vote to agree with Tetsuo on all three of his aspects. (That
semver.org link is an excellent and concise capture of everything I have been
trying to advocate, thank you for providing it!)
Regarding semantic versioning, note the paragraph starting with A simple
example will
On Mon, Aug 29, 2011 at 6:28 PM, tetsuo ronald.tet...@gmail.com wrote:
non-binding
-1 to independent module versioning. I don't want to have a compatibility
matrix like Hibernate's (
http://community.jboss.org/wiki/HibernateCompatibilityMatrix).
+1 to semantic versioning
The difference is that we would have had a version 2.0, 3.0, 4.0 and 5.0
before 6.0. Or, more care would be taken to not introduce unnecessary API
incompatibilities (although I can't see any way to avoid it in both 1.3~1.4
and 1.4~1.5 transitions).
Oh well, ok, I just like 2.0 better, and I'm
Even Hibernate started to release its modules altogether. From the matrix
compatibility website:
Please note that as of 3.5.x Hibernate Core, Hibernate Annotations and
Hibernate EntityManager are all versioned and released together which
greatly simplifies this matrix; see this
They also run parallel development tracks on multiple versions, providing a
different means of solving the same problem.
On Aug 29, 2011, at 11:33 PM, Bruno Borges wrote:
Even Hibernate started to release its modules altogether. From the matrix
compatibility website:
Please note that as of
10 matches
Mail list logo
