On Fri, 2007-03-16 at 21:23 -0400, Mike Frysinger wrote:
> On Friday 16 March 2007, William L. Thomson Jr. wrote:
> > Well that's the problem. When I use say _pre instead of _dev it gives
> > off the wrong impression to users judging package by it's name. Since
> > it's not a pre-release. A user may go upstream looking for some sort of
> > pre-release. Which they won't find.
> 
> isnt it though ?  how is a "development" release different from a "pre" 
> release ?

I take it as a pre-release is more of an official release. Where in it
would be easily found on a projects download page or else where. What I
would consider a _dev release is something coming out of a developers
space on the project. Not really announced say beyond the developers
mailing list. In that same regard alpha's and beta's usually can be
found on project download pages. Same I would assume for any
pre-releases.

Given conceptually a development release is "pre" release. But not
really advertised as such by upstream. Either way it would not really
fit into our hierarchy. Most times the dev release will precede an alpha
or beta, sometimes does skip and is before an official release.

This might help a bit
http://marc.info/?l=tomcat-dev&m=117251925901310&w=2

In that example a _dev is more of a snapshot, which could also be
considered as pre-release :) Good old interpretation of words.

P.S. OTT
With regard to above link and following development that closely.
Between revisions of mod_jk, not only was there a security
vulnerability. But in compatible changes effect certain file
extensions .jsf, that a user reported. Which they only mentioned during
stabilization of a given version (literally in stabilization bug). So in
a sense a version with a problem got stabilized. But was an upstream
bug, effecting a small subset. So did not really merit keeping the
package from going stable for others. But bug was not filed with
upstream either till 30+ days after release due to our stabilization
policies and etc.

-- 
William L. Thomson Jr.
Gentoo/Java

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to