Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
roll on to 2.3.5-dev
prepare for 2.3.4 tag
roll on to 2.3.4-dev
Prepare for 2.3.3 release tag.
Roll on to 2.3.2.
happy new year
Roll on to 2.3.2-dev.
Prepare for tagging 2.3.1.
Roll on trunk to 2.3.1-dev.
Remove -dev flag to prepare for 2.3.0.
Adjust for 2008
Update copyright dates from 2006 to 2007
update license header text
Remove a host of dependencies upon awk, using the same template for nearly every .rc compilation (giving the output .res file a different name for each component). Adds AP_SERVER_BASEPROJECT to ap_revision.h so we can display the proper name of "Apache HTTP Server" as opposed to AP_SERVER_BASEPRODUCT (which is, and should remain, simply "Apache" for the server string tokens.)
Update the copyright year in all .c, .h and .xml files
Update one of the more important copyright notices prior to any 2006 releases.
Determined that yes; apr_general.h may be included in .rc files, so eliminate a substitute declaration. Correct version and copyright generation, this involves 'long line' flavor of the first ASF copyright line; next step will be no more awk generation of .rc files, so there we will use the new macro AP_SERVER_COPYRIGHT and defined tokens from this file for versions.
Doxygen fixup / cleanup submited by: Neale Ranns neale ranns.org reviewed by: Ian Holsman
move trunk to 2.3.0-dev.
Move on to 2.1.7-dev.
- Prepare for 2.1.6 tag.
Onward to 2.1.6-dev!
* include/ap_release.h: Remove -dev to prepare for 2.1.5 tag.
And carry on with 2.1.5-dev. * include/ap_release.h Bump AP_SERVER_PATCHLEVEL_NUMBER to 5. Set AP_SERVER_DEVBUILD_BOOLEAN. * CHANGES Add a 2.1.5 section.
Prepare for 2.1.4 tag. * include/ap_release.h Clear AP_SERVER_DEVBUILD_BOOLEAN.
Onward ho to 2.1.4. * CHANGES: Bump. * include/ap_release.h: Bump.
* include/ap_release.h: Time for 2.1.3.
Fix some symbols which should -not- be exported, and decorate real_exit_code with ap_ (this symbol must be exported.) If the others were desired to be public, they should have been ap_xxx decorated.
Update copyright year to 2005 and standardize on current copyright owner line.
Onward ho to 2.1.3...
It's time for 2.1.2.
Eliminate awk autogeneration of the ApacheMonitor's .rc resource
source file.
By adding several macros to ap_release.h:
- the stringize magic, in leiu of including a ton of cruft,
- split subversion and "-dev" tokens (with a binary flag)
- a _CSV token in the form of m,n,p (not a string)
we are able to have use a static ApacheMonitor.rc file, which picks
up all of the necessary values right from ap_release.h.
If the group likes this approach, I will percolate it throughout
the project, and we will lose the requirement of awk for everything
-except- rewriting the installed httpd.conf script (developer builds
always get an installed httpd.conf script - it's only 'fixed up'
with the correct @@ substitutions if they have awk.)
This project was chosen because ApacheMonitor.rc already exists in svn.
Comment please.
general property cleanup
Onward to 2.1.2-dev. * CHANGES: Bump... * include/ap_release.h: to 2.1.2-dev.
* include/ap_release.h: Bump to 2.1.1.
fix name of The Apache Software Foundation
fix copyright dates according to the first check in
apply Apache License, Version 2.0
Add core version query function ap_get_server_revision and accompanying ap_version_t structure (minor MMN bump). The function is similar to apr_version() and allow for exact querying of the core revision level.
update license to 2004.
finished that boring job: update license to 2003. Happy New Year! ;-))
Branch tag APACHE_2_0_BRANCH now contains Apache 2.0 development. Persist cvs HEAD as Apache 2.1. After discussion at AC, a number of individuals including Sander, Will, Justin and Rich will begin reverting the appropriate changes from the APACHE_2_0_BRANCH, while continuing their documentation and development of the Authorization reorganization on this branch.
On to .44
On to the 2.0.43 candidate
Update after the tag (and roll).
Prepare for the tag.
Update after the tag.
Prepare for the tag.
Major/Minor/Min[imal] now working as one (with a sane mind) would thing it should
new option to ServerTokens. "Maj[or]" which displays a server response similar to Apache/2.0 Also surfaced the directive in the standard config, defaulting to FULL
Bump after the tag.
Getting ready for the tag.
bump after the tag
here goes nothing
moving on. :)
bump before the tag
Bump after the tag
bump before the tag
Bump after the tag.
Bump for the tag
Bump after the tag and roll
Bump for the 2.0.35 tag. Just waiting for Will's commit to actually do the tag.
Up to .35 [no need to call out .35-dev in changes, that's just silly.]
Ready for .34 evaluation.
Update our copyright for this year.
bump after the tag.
Push for a new tag. PR: Obtained from: Submitted by: Reviewed by:
Welcome to .33-dev.
Bump for .32
32-dev is now it PR: Obtained from: Submitted by: Reviewed by:
its tag time v31 is being tagged
Welcome to 2.0.31
About to tag 2.0.30
welcome to .30
about to tag 29
advancing release numbers to 2.0.29-dev after tag
about to tag 2.0.28
bumping release number to 2.0.28-dev after tag
bump release number to 2.0.27
Bump after the 2.0.26 tag.
Bump the versions for the 2.0.26 tag.
Ryan apparently bumped this back DOWN from 2.0.25 to 2.0.25-dev after the last tag, rather than UP to 2.0.26-dev. =-)
Bump after the tag.
Forgot to bump these numbers before the tag. Re-tagging these three files only.
Bump after the tag.
Bump for a 2.0.24 tag
Bump to 2.0.24-dev after tag
Bump for 2.0.23 tag
Bump to 2.0.23-dev after tag update
Bump for 2.0.22
Bump after the tag.
Bumps for the release. The tag will be moved to this version.
We are tagged, so bump the numbers everywhere.
Update to prepare for 2.0.20 release
Bump after the tag/roll
Bump a couple things for the tag and roll!!!!
On to 2.0.19-dev
Preparing for the tag and roll of 2.0.18.
Retagged.. Now bump back to 2.0.18-dev. For anyone looking at this in the future, I screwed up tagging the 2.0.17 release. Should have set the string to 2.0.17, then tagged. I left it at 2.0.17-dev by mistake.
Retag at 2.0.17
Bump the release num
Back out the 2.0.17 stuff. We'll just re-tag the one file in 2.0.16 and re-roll.
Update for 2.0.17. The only change was in APR-util, but APR and APR-util aren't at a point that they have their own release strategy, so this means a new tag for Apache. :-(
Working in 2.0.17-dev now.
Update the CHANGES and ap_release files.
We are working on 2.0.16 now.
Prepare for the next roll
OtherBill told me last night that I never bumped for 2.0.15. Whoops.
Bump for version 2.0.14
nice to compile for a change note that recent tags are FUBAR because this file was broken
2.0.13 is tagged, so bump everything for 2.0.14
Bump to 2.0.13 for a tag and roll
Remove the APACHE_RELEASE macro. We never use it in the code, and it makes automating releases harder, because it is one more number to bump.
Tag is done, update the source tree
Update the version string before the roll.
Remove the b1 description from ap_release. It doesn't belong there anymore.
Update copyright to 2001
bring along the comment (from httpd.h) that went with these defines
Move release.h to ap_release.h. This was done to namespace protect the release header file. While doing this, I also made sure that the file was only included once. Submitted by: Greg Stein
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |