[Pkg-octave-devel] Re: [Pkg-octave-commit] rev 816 - in trunk/packages/octplot/debian: . patches

[Thomas Weber]

Hi, 

Am Mittwoch, 6. Dezember 2006 18:35 schrieb Rafael Laboissiere:
> * Thomas Weber <thomas.weber.mail at gmail.com> [2006-12-04 08:25]:
> > I think we should upload, in order to get the buildds fixed (which means
> > that we should upload to _unstable_). I don't expect this version to be
> > part of etch, though.
>
> This is an excerpt of Andreas Barth's post in d-d-a:
>
> ==========================================================================
> The soft freeze continues
> ~~~~~~~~~~~~
> We have not yet reached a point where we believe there should be a hard
> freeze of updates into etch, but we ask your continued support by avoiding
> uploads that are likely to introduce regressions or be disruptive to other
> packages so close before release.  Please do not upload new upstream
> releases or start library transitions without discussing with the release
> team, and please don't upload changes to unstable that are not meant for
> Etch.  You can always upload such changes to experimental.
> ==========================================================================
>
> I think that packages upload now to unstable have a good chance to be in
> etch.  The question is: are the last changes in SVN meant for etch or not?

Well, I wouldn't mind shipping etch with its current version of octplot. OTOH. 
this package fixes bugs and we need to get the buildds fixed rather sooner 
than later (which only works if we are uploading to unstable; experimental 
uses different chroots, afaik). 

So yes, I think we should upload octplot to unstable. It will still take 10 
days to migrate into etch.

By the way, if it's possible, an upload of _Octaviz_ would be nice as well. 
The failing examples are not that good and if we have time to fix it, we 
should fix it.

	Thomas