| From: | elein(at)varlena(dot)com (elein) |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org> |
| Cc: | elein <elein(at)varlena(dot)com>, pgsql-advocacy(at)postgresql(dot)org |
| Subject: | Re: Conventions for release numbering |
| Date: | 2005-06-13 02:38:18 |
| Message-ID: | 20050613023818.GW17206@varlena.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On Sun, Jun 12, 2005 at 11:13:15PM -0300, Marc G. Fournier wrote:
> On Sun, 12 Jun 2005, elein wrote:
>
> >(No, wait, I'm not starting a release numbering discussion.)
> >
> >
> >If we have release 8.0.3 where 8 is the Major releae,
> >0 is the minor release and 3 is the version (revision?),
> >how would we refer to a generic release number:
> >
> > postgresql-M.m.v ? postgresql-M.m.r ?
> >
> >Is this our convention? Do either of these work?
>
> Assuming v==version and r==release, is there a big difference between the
> two? How are each defined?
That is my question! What do we conventionally use?
>
>
> ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2005-06-13 04:49:01 | Re: Conventions for release numbering |
| Previous Message | Marc G. Fournier | 2005-06-13 02:13:15 | Re: Conventions for release numbering |