Personally I think one should not replace a release with a new version without changing its name. This causes confusion. So at least call it RC2-build2 or something like that.

To ensure this does not happen again in the future, should we include a check in the build.xml for the JavaC version used?

Odi

Michael Becke wrote:
Assuming this new build fixes the problem, what is everyones' opinion about how we should proceed? As I see it we have the following options:

- replace the existing 2.0 RC2 distributions with the new ones and add a note about the change to the HttpClient site
- create a new release 2.0 RC3 and proceed with the normal release process
- do nothing. leave the unofficial build in my directory for the time being and wait for 2.0 final.


What does everyone think?

Mike


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to