Hi, * William A. Rowe, Jr. <[EMAIL PROTECTED]> [2005-12-20 16:05:50]:
> Maxime Petazzoni wrote: > > > >The mailing list archives browser mod_mbox [1] has been tagged and > >released as v0.2 (Alpha) a few hours ago. > > if you just created a new tarball, this isn't an alpha or 'released' just > yet... you need votes on the release candidate tarball. > > Please be careful of the word 'released', it applies only to a > tarball which has recieved 3 +1's and more ayes than nays. We > usually call the 'before' file a release candidate, or simply tagged > and rolled. Yes, I should not have used to word 'released' itself, but I specified "as v0.2 *Alpha*" which should be enough to indicate that it's only for the first stage of the release process (as defined in the Apache HTTP Server Release Guideline). So how should I call it ? If it's not yet Alpha, how do you publish the initial tarball that would eventually get the 3 +1 votes so it can become Alpha ? > In these httpd projects, we prefer to land candidates in the dev playground, > /www/httpd.apache.org/dev/dist on people.apache.org, (which then maps to > http://httpd.apache.org/dev/dist/) and if you don't have permission > (I -think- you should) we can ensure that you at least gain access to > a mod_mbox/ subdirectory under that tree. I was going to do that when I was told on #httpd-dev that it was easier to drop it in my people.apache.org web space : 16:45:08 colmmacc | well, that gets mirrored, I'd use people.apache.org/~whatever/ 16:45:17 colmmacc | that's what the cool kids have used lately ;-) Anyway, if it is needed, I can create a mod_mbox subdir in /dev/dist and put the tarballs in there. I was not really confident into touching minotaur's DocumentRoot directory structure, that's why I used this easier and safer solution. - Sam -- Maxime Petazzoni (http://www.bulix.org) -- gone crazy, back soon. leave message.
signature.asc
Description: Digital signature
