Berin Loritsch wrote:
Stephen McConnell wrote:I am tired of seeing little piddly things come up trying to slow down
or derail the release. Can I encourage us in something?These are not little piddly things: 1. dist - index.html, link to JavaDoc API is broken 2. JavaDoc apis are missing ALL compat classes 3. manifest is requiredDocumentation can be fixed post release. It is not a big deal.
Look - IT'S BROKEN - IT'S WRONG - IT'S BAD - please let's stop pretending that it anything else - you need to add three lines to the buildfile - JUST FIX IT - it's not changing the binaries! You are release manager - use a little discretion - but please - DON'T go releasing something that is just plain incomplete.
It's Open Source software! It doesn't have to be 100% perfect with every 'i' dotted and every 't' crossed. The code (which is what is important) *works*, and people need it.
Come on - I'm not asking for perfection.
I'm looking for a distribution that is clean, free of errors, and functional. RC6 is very close to meeting that criteria.
Sure you are. The distribution is free of errors and functional. THere are some really *minor* points that really should not delay a release. Esp. since they can be taken care of afterwords.
You and I have totally different ideas about what is acceptable in a release and what is not. A release that is missing class and interface description of only those classes and interfaces that are changing and likely to be dropped in the next major release - ummm ... So explain to me how this actually helps those users migrate! Explain to me again why this is a good thing. Explain to me why you cannot fix this now? This isn't about another RCx - its about responsibility and doing the best job we can. Forget about the f*** process for a moment. Instead - explain to me why we cannot fix this problem now.
So let's get off our high horses. If there is a *major* *technical* reason why it should not be released, issue a -1. However these things are very minor, and they can be fixed later.
These are small but important corrections that I feel should be addressed at this time. After all, a vote is about expressing an opinion - I'm not looking for perfection but I am looking for a release with at least all of the javadoc in place and a manifest that tells me what I'm using.
Is it a *major*, *technical* reason? No. They are small reasons. They don't affect many people at all.
Your release manager - so its your call - I just don't agree with you.
* the release has missing documetation
* the release has sources have not been updated on copyright year
* the release does not contain a manifest
* the generated docs linking is inconsistent
All of the above can be fixed without modifying the binary.
All of the above takes about 5 minutes.
All of the above is related to the quality of our work.
Cheers, Steve.
--
Stephen J. McConnell
mailto:[EMAIL PROTECTED]
http://www.osm.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
