We've taken quite a few fixes (over 50*) since RC1 so we could use lots
of testing of today's and tomorrow's branch builds
If all goes well with landing the remaing fixes and testing the previous
landings, we could see RC2 as soon as tomorrow.
* buglist pulled from bonsai checkin comments (so not necessarily
completely accurate) of changes that have landed on the 1.4 branch since
RC2 which have approved patches and either fixed1.4 or verified1.4 keywords:
Great news! I'm looking forward to the 1.4 release and will test 1.4 RC2
as much as I can.
well I'm using today's...
> If all goes well with landing the remaing fixes and testing the previous
> landings, we could see RC2 as soon as tomorrow.
I guess it doesn't necessarily need to be before RC2, but someone needs to
take a look through the nominated blockers before we get too close the
release to do anything... for example:
Bug 207641 - update localeVersion for 1.4 final - seems pretty essential
to avoid another release that can't be localised...
bug 208359 - unable to create templates/drafts of HTML email) - also seems
serious if it's real...
and there's a couple of others that could be critical regression bugs...
> We've taken quite a few fixes (over 50*) since RC1 so we could use lots
> of testing
Well, if there would be a source tarball ...
Yes, why aren't there tarballs for rc1 or rc2?
You /do/ realize that for many people (especially source-based
distributions) to try the software it's got to be easily available in a
tarball. Saying "check it out from CVS" just doesn't cut it -- it
/certainly/ doesn't work for source-based distributions very easily, and
many users that would otherwise give it a go won't bother.