Peter Donald wrote:
>On Fri, 16 Aug 2002 20:26, Carsten Ziegeler wrote:
>
>
>>Peter Donald wrote:
>>
>>
>>>On Fri, 16 Aug 2002 20:09, Carsten Ziegeler wrote:
>>>
>>>
>>>>can someone give me a hint on what's the procedure to release a
>>>>subproject? Is a vote necessary?
>>>>
>>>>
>>>There is no real formal process for release. Usually it is lazy
>>>consensus for
>>>components that are already released so just state intentions and unless
>>>anyone objects go for it.
>>>
>>>
>>Ok, but what does 'go for it' mean? Where do I put the dists, do we
>>have bin and src dists etc. Or is this a matter of the subproject as well?
>>
>>
>
>oh that.
>
>* Update jakarta-avalon-site CVS with new docs.
>* create distribution (I usually create a single distribution for excalibur
>components and include src in src.zip inside a "binary distribution).
>
>Ideally a distribution would look like
>
>foo-1.0/README.txt
>foo-1.0/LICENSE.txt
>foo-1.0/docs/**
>foo-1.0/src.zip (the source for foo)
>foo-1.0/foo-1.0.jar
>foo-1.0/foo-all-1.0.jar (contains foo and its dependencies)
>foo-1.0/lib/baz-2.3.jar (contains jars foo is dependent upon)
>
>(The last two jars may be optional depending on personal preference).
>
>
>
>>>One thing
>>>I would like
>>>to see is for sourceresolve to be upgraded so that components do not
>>>implement Component interface however that requires changes to cocoon
>>>presumably ...
>>>
>>>
>>Hmm, the only problem is the release() method of the component manager,
>>were we would have to cast to Component for these components - this
>>would not be an incompatible change as we did not release Cocoon
>>with the sourceresolve package, but it's inconsistent - there are
>>components were you have to cast and 95% you don't have to.
>>What do others thing on this?
>>
>>
>
>No I mean the whole package should not be using Component - instead Cocoon
>should upgrade to Serviceable in all places possible ;)
>
-1 on removal of Component from implements clause
Project that are already currently using ComponentManager and have not
yet moved to ServiceManager will break if you remove the Component
interface. It seems a lot more friendly to our users (Cocoon, James,
etc.) to leave in place the "implements Component".
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
