Same here ...what about a quick vote?


Could do. I'd like to see someone with the necessary perms and knowledge just get the correct jar in apache's maven repository, it sounds like that would get sync'd across to ibiblio.org automatically anyway. I think its just a case of copying the correct version into some directory on the daedalus but I'm not sure where and I don't think I have access anyway.


I can do that ...but I would us to agree
on that first.

What's left to do for the 1.0.1 release?


We need to copy the 1.0 tag and get it buildable again. The changes to the common maven config have meant that this tag is no longer buildable against the current setup and I haven't had much luck getting a working copy into the correct historical state to build using the old one.


Hm... that's unfortunate. So we would not
provide any version 1.0 but only the 1.0.1
anymore? ...maybe we should then make an
announcement, provide the jdiff and be
sure 1.0.1 can replace 1.0 without any
hurdles.
WDYT?


I think the best plan for a 1.0.1 is simply to go from the 1.0 tag with the necessary build changes (i.e. no code changes) as Simon pointed out. It just needs a little work to get it there. I'm sure a jdiff report can be produced to reassure people if needed.


Ok ...sounds cool.

cheers
--
Torsten


Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to