Re: Proposal for Package naming : updating existing non-conform packages
| From: | Cipriano Groenendal | Date: | Wed, 28 Apr 2004 13:42:59 +0000 |
| Subject: | Re: Proposal for Package naming : updating existing non-conform packages | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-28502@lists.php.net to get a copy of this message | ||
> Var_Dump is at state 'stable', but it also break the rule about Version
Naming
> (accepted) that
> - The first release with state "RC" or "stable" must have a version number
of
> "1.0.0".
> - BC may only be broken in releases ... that have a version number below
> "1.0.0".
> So I don't know if it should really be marked at state Stable, or if I'd
have to
> release a new major version in case of BC.
It should be, and you shoud, respectivly ;)
The source code IS stable, so there's no problem there. It's state should be
stable. Having a version < 1.0.0 does not mean the code isn't stable yet,
and since the rules didn't exist yet when your package was released, the "BC
may be broken if < 1.0.0" rule also doesn't apply to it :)
HTH,
Cipri