octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: plans for release


From: marco atzeri
Subject: Re: plans for release
Date: Thu, 3 Feb 2011 12:41:57 +0100

On Thu, Feb 3, 2011 at 11:07 AM, John W. Eaton  wrote:
> In the seven weeks since I first asked whether we were ready for a new
> release, we've fixed a large number of bugs and made many other
> improvements.  There are currently no bugs in the tracker tagged with
> "blocker" severity.  So I'd like to make the 3.4.0 release this
> weekend if possible.
>
> Perhaps you are thinking, "WAIT!  Is he crazy?  This weekend?  We have
> only had two test releases so far.  And they weren't even announced on
> the web site!!!  And my favorite bug is still not fixed.  And the
> build system is not perfect.  And what about all those functions that
> still need better documentation?"
>
> Well, yeah, I know.
>
> But please remember that there is no way we can make any given release
> perfect, and it has been more than a year and a half since the last
> major stable release (3.2.0).  Look also at the NEWS file to see how
> much has happened since then.  I think we will be much better off to
> make a 3.4.0 release now rather than delay any longer.  Then we should
> focus on fixing only serious bugs for the 3.4.x series while we
> continue to make more general improvements in the default branch in
> the Mercurial archive, with the idea of shortening the release cycle
> in the future (and this time, I mean it! :-).
>
> Don't get me wrong, the improvements of the last few weeks have been
> great, but I fear that we are slipping into a cycle of trying to fix
> every problem, no matter how small.  If we continue on this path, it
> seems we will never have a release because there is an endless supply
> of nits to pick.
>
> So, Are there any serious problems that absolutely must be fixed before
> a release can happen?  If so, then those problems should be entered in
> the bug tracker already, and you can just post a link to them here.
>
> Thanks,
>
> jwe
>

John,
fine for me on cygwin.
The fltk print crash is the only real problem, but I have no
time/knowledge to solve it
in short term.

We can always let user solve the curent bugs or find other bugs to be
solved for 3.4.1

Regards
Marco


reply via email to

[Prev in Thread] Current Thread [Next in Thread]