Re: Package status

> I'm about to release a new (minor) version of > [M]DB_QueryTool; both packages have been > labeled as "stable" for several months, > even if they're below 1.0.0 (because there was > no guideline back then). > Should I keep the "stable" label for the next releases, > or should I mark them as "beta", as the latest directives > may suggest? Hi Lorenzo. The focus on the combination version-number <-> code-status lies with the later. If you want to relase this code as Stable, then give it that name and figure out a version# from there(1.0.0 would be appropriate). Don't feel forced to release an otherwise stable package as beta since you're < 1.0.0 :) Also, note that if you don't want to release this code as 1.0.0 yet, know that if you release a 0.9.8 as BETA, users who have set their prefered-state to "stable", will NOT get upgraded. As such, unless there's some major refactoring, and you think the code is stable, just relase it as such as 1.0.0 (stable). Cipri