"John Hunter" <[EMAIL PROTECTED]> writes:

> On Fri, Jun 13, 2008 at 9:25 AM, Chris Walker
> <[EMAIL PROTECTED]> wrote:
> 
> >> So if we want to support stable, *and*
> >> the latest releases, we've got a lot of ongoing compatibility work to
> >> do.  For backend maintainers willing to do it, I think that will be
> >> good.  But I am hesitant to target such a slow moving repository as a
> >> requirement.
> >
> > Would the next debian release (lenny) be a better target for
> > development versions of matplotlib?
> >
> > What version of matplotlib do you want to go into the next debian release?
> 
> Hi Chris -- thanks for all the information.  

Pleasure, Hope it was useful, but please note I don't speak for the
Debian Matplotlib maintainers.

There are some things I need to clarify though.


> Since 0.98 requires numpy
> 1.1, 0.98.1 (a bugfix release slated for next week or the week after)
> should be in unstable and 0.91.4 (again a bugfix scheduled for next
> week or the week after) should be in testing 

Ah, I think you may have misunderstood how debian
stable/testing/unstable works.

A grossly oversimplified view[1] is as follows.

1) A new version of the package is uploaded to sid (unstable) 

2) When the package has been in sid (unstable) for 10 days, it is a
   candidate for moving to lenny (testing). when they can do so
   without breaking other packages lenny (testing).

3) Eventually, lenny is released as the stable distribution, and you
   are stuck with it for a year or two (except security or dataloss
   bugs). 

so it sounds like 0.98.x should be what is uploaded to unstable (from
where it will migrate to testing).

> and 0.91.2 should be in
> stable.  

The version in etch (stable) is only likely to be upgraded (from
0.87.7-0.3) if there are major bugs (such as security problems or data
loss issues). See http://www.debian.org/security/


> I find this a bit conservative, since I think numpy 1.1
> should be in testing 

It was only uploaded 3 days ago, so in theory could migrate in 7 days
time.

> along with matplotlib 0.98.1, 

http://packages.qa.debian.org/m/matplotlib.html gives debian package
information on matplotlib - including which versions are in
stable,testing and unstable. Hopefully 0.98.0 or 0.98.1 packages will
be uploaded soon. If not, then giving the maintainers a push to ensure
they are in the next debian stable would be a good idea.


> but that is
> apparently how debian does it.
> 

Hopefully that is now slightly clearer. 


Chris


[1] Packages can migrate more quickly if they contain urgent bug fixes
http://www.debian.org/ and specifically
http://www.debian.org/devel/testing contains more accurate
information.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to