Vincent Massol wrote:
No, quite the opposite. Working with thinner slices is always easier than
working with bulk. Saying it differently, it's much easier to do regular
releases than longer ones because less has changed. Take the example of
Maven again. Releasing a plugin is really a breeze, including the votes. The
same would be true of VFS. The core might require lots of thoughts as it's
critical but the providers would be real easy to release.
This whole debate is a matter of perspective - cargo and vfs have very
different perspectives on two points:
- community
- ease of release
Cargo, and hence maven, comes to the table with a decent-sized community
and the full knowledge and use of maven. Together these two points
probably do make releasing a plugin 'a breeze'.
However vfs is effectively a single person project (at present), and
does not heavily use maven. (Commons does use maven, but does not have
the background knowledge, desire, etc to commit fully to it, in
particular maven version 2). Together, these points make it virtually
inconceivable to release lots of small jars, one per filesystem.
To further complicate this, commons rules currently effectively require
every release to be manually checked by every voter. Or to put it
another way, there is no trust of the releasable artifacts, maven
generated or not. (In fact, I typically raise more issues with a maven
generated release than a non maven generated release.)
My point here is that IMHO the 'correct' solution is a single core jar,
plus one jar per filsystem, together with an 'all' jar for users who
want everything in one go. But such a solution is unfortunately not
viable in the commons of today. Which is one reason why commons does not
release early release often.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
