Actually I volunteered to do that, bot got no reply. :-/
You don't need my go-go to commit release-related suff :-) Actually, we need a clean tar.gz archive (the zip is in the contributor.xml file) and bug fixes.
Actually it's not a fork at all. It's a tag, nothing more. We have some interesting code that would be nice to commit (I'm talking about the metadata stuff) but I don't like to commit it to what might be 1.1 codebase. A tag is only that, a tag, to keep things clean.
yes but if you tag the tree, you still have only one branch (the HEAD). The only way to commit code for only one version is to fork the tree, not to tag it. Please reread the cvs manual <http://www.cvshome.org/docs/manual/cvs_5.html>. Otherwise I haven't understood cvs at all. :-)
2. spend the next week fixing bugs;
weekS :-)
1. some committers willing to actually do the job of bug hunting and fixes. I'm here. I suppose Vladimir is here too: anyone else?
I won't have broadband in the next few weeks (only a modem... argh!). So I will be less responsive regarding jar upgrading and stuff. That's why I already committed new jars for xupdate.
2. a release manager (the guy actually doing the release). Again, I volunteer for that but if some of you guys is willing to do it, he's most welcome and saves me a lot of work;
As I said, I won't be able to do this. But I'll try to help.
Sounds good?
Sounds fine for me.
-Vladimir
-- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice
