[Pkg-octave-devel] Octave 3.0.x releases

[Rafael Laboissiere]

[Cc:ing to pkg-octave-devel, which I forgot to do when sending my last
message. I hope you do not mind being quoted publicly.]

* John W. Eaton <jwe at bevo.che.wisc.edu> [2008-07-28 15:54]:

> On 28-Jul-2008, Rafael Laboissiere wrote:
> 
> | I am just curious: are you applying these changesets to both the 3.0 and 3.1
> | branches?
> 
> No.  I'm not doing that job anymore.  Jaroslav is handling the stable
> branch.  The informal criteria for applying a patch to the stable
> branch is
> 
>   * The change must not break backward compatibility with the .oct
>     file API.
> 
>   * The change should fix a bug.  Adding new features to the stable
>     release series is strongly discouraged.  At some point we may
>     change this to the require that the bug fix is for a problem that
>     can be classified as a regression from a previous version of
>     Octave.
> 
>   * The change should be unlikely to introduce new problems.  Complex
>     or very intrusive patches are discouraged.

Okay, these rules are clear and sound enough.  I was asking this because the
bug reports filed by Francesco Potortì last week regard octave3.0 and we may
apply the patches to the Debian package.  Hence, my question:

> |  A subsidiary question: any plans on releasing 3.0.2?
>
> I have no strong objection to a 3.0.2 release happening fairly soon.

If 3.0.2 is going to be released soon, I will not bother fixing the Debian
bugs.

> I could also see making 3.0.x releases after 3.2 is available, but my
> preference would be that we avoid that if possible.

That sounds reasonable.  As soon as 3.2 will be released, we will arrange
for octave3.2 to replace octave3.0 in Debian.

Thanks,

-- 
Rafael