asterisk 1.2.0-0beta1

[Mark Purcell]

On Sunday 09 October 2005 12:00, Kilian Krause wrote:
> > 1:1.2.0.beta1.dfsg-1	-> experimental
> > 1:1.2.0.beta1.dfsg-2	-> experimental (if debian makes changes)
> > 1:1.2.0.beta2.dfsg-1	-> experimental (if upstream makes another beta
> > release) 1:1.2.0.rc1.dfsg-1		-> experimental (if upstream makes a RC
> > release) 1:1.2.0.rc2.dfsg-1		-> experimental
> > [...]
> > 1:1.2.0.dfsg-1			-> unstable (when upstream makes final release)
> > 1:1.2.0.dfsg-2			-> unstable (when debian makes another release)
>
> sorry, if I contradict, but rc* is greater than dfsg* AFAICT. Thus we
> should not go for rc* unless we want to put release.dfsg afterwards
> (which would be greater than rc again) IMHO. Rather we should jump from
> beta to dfsg which is a consistent step from b->d.

Opps! Thanks for that!

You are of course correct and my mistake again.. That said I think we will 
need to accomidate some sort of RC versioning as digum have done that in the 
past.

Here is a reworked proposal, using - and . to get around the issues :-)

asterisk:
1:1.2.0-beta1.dfsg-1    -> experimental
1:1.2.0-beta1.dfsg-2    -> experimental (if debian makes changes)
1:1.2.0-beta2.dfsg-1    -> experimental (if upstream beta release)
1:1.2.0-rc1.dfsg-1              -> experimental (if upstream RC release)
1:1.2.0-rc2.dfsg-1              -> experimental
[...]
1:1.2.0.dfsg-1                  -> unstable (when upstream final release)
1:1.2.0.dfsg-2                  -> unstable (when debian release)

zaptel/ libpri:
1.2.0-0beta1-1          -> already uploaded to expiermenal
1.2.0-0beta1-2          -> experimental (next debian release)
1.2.0-beta2-1          -> experimental (upstream next beta release)
1.2.0-rc1-1            -> experimental (upstream RC release)
[...]
1.2.0-1                 -> unstable (-b when upstream makes final release)
1.2.0-cvs2005xxxx-1	-> experimental (to fixup versioning)

Mark