+0 And .. I agree with Peters points And .. I'll upload the build if its ready And .. two version control points:
1/ IMO it helps if you change the name of the archive files in build.xml to include either a date or a version, and increment the version (either the minor number or the modifier a,b,rc, this avoids users confusion with any other builds. We should ensure builds have unique names 2/ Then TAG the HEAD with this command in the root of jakarta-james: cvs tag <version> where version might be 2.1rc1 d. > I'd prefer that too, but there are other considerations. I'll be > willing to vote +1 on this provided that we can get the new milestone > build up and posted by 24 hours from the date of this email. I don't > have appropriate access to daedalus, so I can't guarantee that. If we > can get someone with that access to guarantee that, I've got no problem > with this fix. Otherwise I've got concerns that this will further push > out an already delayed release. > > To speed the process, I've applied the patch, build a dist, and am > uploading to a public directory in my home directory on cvs.apache.org. > This will enable Danny or someone else just to copy it into the nightly > build directory. > > If we can't make this timeframe I'll have to vote -1. Getting 2.1 out > the door is a very high priority, even if it means we leave some issues > unaddressed. This issue affects only a small segment of our user base. > If necessary, we'll issue that point release. > > --Peter > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
