Hi Stephen,
> -----Original Message-----
> From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> Sent: vendredi 28 juillet 2006 01:07
> To: Jakarta Commons Users List
> Subject: Re: [VFS] Snapshot timestamped version has disappeared from the
> m1 snapshot repo!
>
> 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'.
That's true for Maven but certainly not for Cargo. I wish Cargo had a good
size developer's community but that's completely there yet... But you're
right, Cargo doesn't release containers individually but this is something
I'd like us to do because right now it's just too bad for end users who have
to wait for long release cycles before getting new features implemented for
their favorite container.
> 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.
I agree. It's only because we have Maven and especially Maven2 that we can
easily perform releases.
> 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.)
I'm a commons committer. So do you mean that I'm expected to vote on every
single component, even those that I have never heard of, never used and
never participated to? That would be pretty useless... Isn't the rule that
you need at least 3 +1 and no -1? Is it really that hard to release a
commons component? If so maybe there's something to fix there. I haven't
participated in commons for a few years now so I'm a bit away from out it
works these days.
> 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.
In any case there's no point in arguing about this I believe as it's up to
Mario to decide what he wants to do. I don't like when people tell me what
to do on my project so I won't tell Mario or VFS what to do. I'm just
highlighting options :-)
However, more generally speaking, I have the feeling that the reason for not
releasing more often in commons is more a state of mind. It seems it has
become the rule and that it's ok for components to remain unreleased for
long period of time. I don't think it's doing any good for commons and VFS.
Back to VFS, it has never had any release for years. There are probably lots
of reasons but from what I hear from Mario, the main reason is that this
project is too monolithic and has only one jar. As a consequence there are
VFS providers lagging behind, either in term of implementation of in term of
their dependencies being themselves released... But Mario has make a good
decision: split vfs in 2 jars: a main one and a sandbox one. So that's a
step in the right direction.
Thanks
-Vincent
___________________________________________________________________________
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet
!
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos
expériences.
http://fr.answers.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
