Hey guys. I am nearing completion of the second cut of CJAN, that will
read from the web an xml file and then download a jar file from the
schema that it reads. I really need some jars to test with, and since I
use beanutils, collections, and digester, it would be great to be able
to test CJAN using these.
Is there any way to convince you all to release a 0.1 of the
corresponding projects?
I understand that this test case is missing or that API might change,
but I don't really care about that. I need to start testing CJAN
relatively heavily, as I see it being a key component in the strategy of
all java open source development, and I want to see all those bloddy
jars disappear from CVS!
Anyway, I am happy to do the release for digester, since I imported it,
but it does depend upon beanutils and collections, so I would really
hope for a release there as well
Scott Sanders
Geir Magnusson Jr. wrote:
> "Waldhoff, Rodney" wrote:
>
>> Not that I read them carefully, but I'm pretty sure Morgan et al put
>> together some release guidelines we probably want to follow. IIRC, I think
>> we should be calling this "1.0 Beta 1" or something like that. Milestone 2
>> would be 1.0 Beta 2, etc., until we're ready for a real 1.0 release. (Which
>> should be soon, I hope.)
>
>
> Why not back off and just call it 0.1 - the point really is to get a
> version in a jar that Turbine and Velocity can use.
>
> We have changes we want to make, and want to avoid having to do them in
> two places. I'll take a look at the release guildines and get this
> going.
>
> geir
