Going for Gold?

[Guest]

Hi all,

I've been using the Release candidate routinely for quite a while now. There seem to be no show-stoppers and few bugs of any substance in the release candidate with the patches applied. Patrick: are you ready to roll a gold-master release? I know lots of people who are switching to Mac at the moment, and Neo is a huge selling point for that switch, so a released product is very important I feel.

Cheers, Phil

[sardisson]

Our original timeline (last winter, when I argued we needed to do a Release Candidate build if we moved OOo codebases from 1.1.3 to 1.1.4) was a couple of weeks between RC and an official release.

We all found more bugs in Beta than at least I expected, so RC didn't happen until late March, and within that period of "a couple of weeks," the release date for Mac OS X 10.4 was announced as just around the corner. So even though Neo/J tested well recently on the last developer build (as opposed to the actual 10.4 release build), it's prudent to wait until 10.4 has been out and make sure there are no new 10.4-caused bugs that would appear in the Neo/J release; it's as big a change, or moreso, than moving OOo codebases, and strange things break.

So we're looking at a few more weeks after 10.4 release at least, plus the flock of existing bugs in Bugzilla. Edit: Er, well, maybe longer.

I'm as eager as the next person to have a "release" version, but I also don't want to see us embarrased by bugs (and VersionTracker reviews) we might have found if we had let the 10.4 adopters have some time to report them. Especially since we are trying to do some concerted press coverage/announcements for this forthcoming release....

Smokey