Re: about a new Archive_Tar release
| From: | Chuck Burgess | Date: | Sat, 28 Nov 2009 15:23:39 +0000 |
| Subject: | Re: about a new Archive_Tar release | ||
| References: | 1 | Groups: | php.pear.dev php.pear.qa |
| Request: | Send a blank email to pear-dev+get-53075@lists.php.net to get a copy of this message | ||
On Wed, Nov 25, 2009 at 1:34 PM, Michiel Rook <michiel.rook@gmail.com>wrote:
> Hi all,
>
> I've been able to close a few bugs since taking over maintenance of
> Archive_Tar, preparing a new release is something that has slipped through
> the cracks unfortunately (sorry about that!)
>
> Now that I have some time to spend on that, I'm thinking about marking the
> next release 'beta'. Even though I'm pretty confident about my fixes,
> Archive_Tar is an essential package.
>
> Any thoughts?
>
> regards,
>
> Michiel
>
Hey Michiel,
Releasing an alpha or beta is certainly an option that's up to you, as the
maintainer. If you've made any changes that aren't *strictly* bug fixes,
then an X.Y release number bump, and an alpha or beta stability, are
certainly the way to go. Whenever I do an X.Y bump for a stable package, I
typically do release at least one alpha and one RC beta before a final
stable.
It's not *customary* to mark an X.Y.Z bump as beta if it's part of an
already stable X.Y, but I don't think there are any *guidelines* against
it. I think you'll be fine to do so.
--
CRB