Re: Mail_IMAP 1.0.0A How to Release Package??
| From: | Pierre-Alain Joye | Date: | Thu, 12 Feb 2004 11:48:15 +0000 |
| Subject: | Re: Mail_IMAP 1.0.0A How to Release Package?? | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-25613@lists.php.net to get a copy of this message | ||
Organization: Freelancer
X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
On Thu, 12 Feb 2004 12:40:18 +0100
"Cipriano Groenendal" <cipri@cipri.com> wrote:
> Traditionally speaking, a 1.0.0 release is usual the first
>
Stable
> release. I'd suggest you first release a nice'n simple 0.1.0 release.
> I can't find the mail that (I think Lukas) send some time ago with all
> the version-number-howto's in it.. Anyone that could shed some light
> on that? :)
It's not a defined rule but a well known rule (well I hope). We are
working on a document to explain the release status and version is on
its way.
A quick summary:
A stable release should be at least 1.0 .
A RC is not stable, but beta (ie current DB release is a bad example).
We recommand (not a strong rule) to do not release a stable release as
an initial release. Having an alpha/beta release help you to change
bad stuffs. It is not always easy to get a """perfect""" package/api
with the first shot.
hth
pierre