Avalon has a lot of different subprojects where some of them are more "active" then others. I think a general policy however for all projects
should be "release early, release often".
So I kindly ask you for new release for the following subprojects:
excalibur-component excalibur-sourceresolve excalibur-store excalibur-xmlutil fortress-container fortress-tools excalibur-logger
At the Cocoon project we really suffer from the fact that we currently have to use CVS versions that are not tagged ect. This makes it very hard for users to get the corresponding source code. As all of these projects are used and can therefore be considered stable and as the latest CVS in all cases contains a lot of bug fixes and enhancements, it really makes sense to release them.
I would release them but two things are preventing me: a) a pmc vote is required (right?) b) I can't build the releases as the build process is not working for me
So, what do you think?
Although having released versions of Avalon components is obviously the better solution, is there anything that prevents Cocoon committers that are also Avalon committers to tag some of these components?
Is a vote needed to place a tag on the CVS? We can also define a naming convention to identify tags related to Cocoon needs, e.g. name them "cocoon_xxxx".
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
