Re: Package status

From: "Lorenzo Alberton" <l.alberton@quipo.it> > Similar topic, different package: Translation2. > It has the "2" suffix in the name since it's a complete > rewrite, but what should the package number be? > I started with 0.x, then I used 2.x since it was > decided so in the last naming guidelines (now > "freezed"), but I'm don't completely understand > why I should start from 2.x since it's a completely > different package from Translation 1.x. Basically, Translation2 would have been Translation 2.x under the old system. Therefore, the Translation2 series will bear the version numbering 2.x. Development releases, etc. should be 0.x. First stable should be 2.x. (Translation3 == 3.x, etc). This has been discussed a few times on this list, and this is the understanding I've taken away. The reason it is Translation2 2.x rather than Translation 2.x is because it makes it possible to install both versions and use both in one application. It also means that you can fully support legacy applications without limiting your options. As for your other question about release status, I also made a mistake: I released HTML_CSS 0.2.0 as stable. Current releases are in the 0.3.x series, and the api may well change before 1.0.0. So.. If you aren't done with development yet, we already determined that < 1.0.0 releases do not need to maintain BC. If you made a pre-1.0.0 stable release prior to the "no stable releases before the major version" rule, you don't need to worry about it, but should not mark subsequent releases as stable until you are ready for 1.0.0 (or 2.0, etc., depending on the package name). hth Klaus