httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guenter Knauf <fua...@apache.org>
Subject Re: Time for httpd 2.4.0-RC1 ??
Date Wed, 14 Dec 2011 12:44:44 GMT
Am 14.12.2011 13:09, schrieb Jim Jagielski:
> Okey dokey...
>
> Let's talk about the specifics of carrying this out... the
> main issues is how we tag and roll this. Recall that we don't
> have any "real" concept of Release Candidates.
maybe time to add one? ;-)
>
> I'm assuming we can simply tag as 2.4.0-RC1 but what about
> the MMN and the below:
>
>    #define AP_SERVER_MAJORVERSION_NUMBER 2
>    #define AP_SERVER_MINORVERSION_NUMBER 4
>    #define AP_SERVER_PATCHLEVEL_NUMBER   0
>    #define AP_SERVER_DEVBUILD_BOOLEAN    1
>
>    /* Synchronize the above with docs/manual/style/version.ent */
>
>    #if AP_SERVER_DEVBUILD_BOOLEAN
>    #define AP_SERVER_ADD_STRING          "-dev"
>    #else
>    #define AP_SERVER_ADD_STRING          ""
>    #endif
>
> I propose that for the RCs, we keep AP_SERVER_DEVBUILD_BOOLEAN as
> '1'... When we go for GA, we then, and only then, change to '0'
> and retag as 2.4.0.
>
> OK?
>
what about changing the above to:
     #if AP_SERVER_DEVBUILD_BOOLEAN && !defined(AP_SERVER_ADD_STRING)
and then adding a line in configure to add -DAP_SERVER_ADD_STRING="-rc1"
?
this way the server would carry out the -rc1 and it would be possible to 
differ between rc1, rc2, ... (and btw. other add strings like svn 
revisions -r123456789 would then also be easily possible ...)

Gün.




Mime
View raw message