Sven Schreiber wrote:
Hi,
I hope I'm not sounding "pushy" but isn't rc2 overdue?
1.5.0 is _long_ overdue...
IMHO it would be more efficient to test the current status instead of
stumbling over "fixedintrunk" bugs again and again. Currently it seems
to me that many known and/or fixed bugs are reported again and again,
which in turn may induce some people (like me) not to report (minor)
issues anymore. As a consequence, this way some bugs may go unnoticed.
Another solution would be that you compile from source ;-)
Or that someone produces daily binaries for the main distributions
(including Mac and Windows). I think this would be a great way to
contribute for non-developers... any volunteers?
If the reason is that rc2 is scheduled to be the last rc, then I would
ask: why not simply add a rc3 to the plan? I don't see any disadvantages
of having more than two rc's, or am I missing something.
I personally think rc2 should just be renamed to 1.5.0 after a day or
two if no critical bug (i.e. crash) appears. The remaining bugs would
then be fixed in 1.5.1. But I am not the release manager, Jose is the
guilty guy ;-)
Abdel.
