[Catalog-sig] Stable-releases-only PyPi
g.brandl at gmx.net
Tue Jul 12 20:00:44 CEST 2011
Am 12.07.2011 15:14, schrieb Éric Araujo:
> Le 12/07/2011 08:28, Georg Brandl a écrit :
>> Am 12.07.2011 08:17, schrieb Sergey Schetinin:
>>> On 12 July 2011 09:14, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>>> If you go by trove classifiers, my proposal would be to include all
>>>> releases with a classifier "Development Status :: 5 - Production/Stable"
>>>> or "Development Status :: 6 - Mature".
>>> That's very unlikely to work. Once webob got to maturity we set that
>>> classifier and it's there even for repo snapshots. I'm sure it's the
>>> case for ~100% other projects.
>> Yeah, the classifier seems to be more appropriate for the project's status,
>> not that of individual releases.
> ISTM that the discussion is confusing “stable” and “final”.
> In my understanding,
> stable = project status = Trove classifier
> final = release status = PEP 386 version
Exactly. While a project itself can be stable (or mature, even),
individual releases still can be of pre-release quality.
More information about the Catalog-SIG