Re: [picocontainer-dev] Sync Pico Script + Pico for next release

Michael Rimov wrote:
>>> A lot of dependencies have been updated since the last pico script
>> release
>>> (especially pico itself!)
>>>
>>> When we do Pico 2.8 release, can we sync a Pico-Script and Pico-
>> Persistence
>>> release on it?
>>>
>> Hi Mike, what's the added benefit?  I assume you're after an updated
>> transitive dependency.  But the default transitive dependencies can be
>> easily upgraded when declaring the dependency in the pom.
> 
> Of course, but in respect for any newbies taking it for a test drive, it would
> be wiser to have it closer to synchronized transitive dependencies than letting
> the updates languish for too long.  If scanning new a project and see that it
> references an too old of a transitive dependency, then it sets off alarm bells
> in my head:  specifically, it means to me that the project hasn't been tested
> with the latest 3rd party libraries, so it may be an update minefield.
> 
> I'm certainly not all for trying to keep everything 100% synchronized, but after
> a couple update release to Pico (We have had 4 since the last script release), I
> would think it would be good to get the other libraries synchronized once in a
> while.
> 
> Additionally, I have done work in getting the XMLContainerBuilder and
> XStreamContainerBuilder to both inherit attributes from the Parent container
> much in the way that groovy can as well as allow both of them to be able to
> reference Parameter.ZERO.
> 
> So there are some bugfixes present too.
>

Well, we can certainly publish bugfix releases of script and 
persistence, which at very least update dependencies, if not actual code 
fixes too.  And leave major incremental releases for new functionality.

So, following the 2.7 Pico release, we can right now publish a 2.0.1 for 
script and persistence.  What I'm not keen on is to release say a 2.1 
solely to synch up transitive dependencies.

Plan?

Cheers





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email