You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apreq-dev@httpd.apache.org by Stas Bekman <st...@stason.org> on 2004/02/16 21:52:51 UTC

[apreq2] CHANGES format

I still find the CHANGES file full of irrelevant to users clutter. This file 
is for end users and dating each change adds no additional values to users. 
Those who want dates have a full cvs control to figure them out. I suggest to 
change the format to be the same as modperl-2.0/Changes (i.e. dates only on 
release dates and move attributions next to the change item.).

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Re: [apreq2] CHANGES format

Posted by Stas Bekman <st...@stason.org>.
Stas Bekman wrote:
[...]

> The suggested format is:
> 
> -----------------------------------------------------
> @section v2_03_dev Changes with libapreq2-2.03-dev
> 
> - February 16, 2004

drop that date of course...

> -- Perl API
> 
> Include ppport.h from blead-perl to support older perls. [stas]
> 
> Add a proper support for ithreads. [stas]
> 
> -- C API
> 
> Fixed bug in calculation of Netscape cookie expiration dates.
> apr_time_t is measured in microseconds, not seconds, which
> threw off the arithmetic; apr_time_from_sec was needed for
> the conversion. [Swen Schillig, joes]
> 
> Fix segfault caused by invalid %-escape sequence in query string.
> [Max Kellermann]
> 
> @section v2_02_dev Changes with libapreq2-2.02-dev

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Re: [apreq2] CHANGES format

Posted by Stas Bekman <st...@stason.org>.
Joe Schaefer wrote:
> Stas Bekman <st...@stason.org> writes:
> 
> 
>>I still find the CHANGES file full of irrelevant to users
>>clutter. This file is for end users and dating each change adds no
>>additional values to users. Those who want dates have a full cvs
>>control to figure them out.  
> 
> 
> +1.  However, please keep in mind that the CHANGES file is
> also part of our doxygen-generated files:
> 
>   http://httpd.apache.org/~joes/libapreq2/CHANGES.html
> 
> I don't want to see the doxygen stuff pulled out entirely,
> since the generated links are pretty nifty.

why would it affect doxygen? The suggested format is:

-----------------------------------------------------
@section v2_03_dev Changes with libapreq2-2.03-dev

- February 16, 2004

-- Perl API

Include ppport.h from blead-perl to support older perls. [stas]

Add a proper support for ithreads. [stas]

-- C API

Fixed bug in calculation of Netscape cookie expiration dates.
apr_time_t is measured in microseconds, not seconds, which
threw off the arithmetic; apr_time_from_sec was needed for
the conversion. [Swen Schillig, joes]

Fix segfault caused by invalid %-escape sequence in query string.
[Max Kellermann]

@section v2_02_dev Changes with libapreq2-2.02-dev
-----------------------------------------------------

that also shows that we may need to split CHANGES for C and Perl APIs. Perhaps 
the perl API changes should go into glue/perl/CHANGES or CHANGES.perl? 
Thinking here about other glues is a good idea.

BTW, the URL that you quoted above, try to click on mod_apreq.c on Oct 23, 
2003 entry. it's 404.

And that file is quite outdated... Oct 26, 2003 is 5 months old.


__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Re: [apreq2] CHANGES format

Posted by Joe Schaefer <jo...@sunstarsys.com>.
Stas Bekman <st...@stason.org> writes:

> I still find the CHANGES file full of irrelevant to users
> clutter. This file is for end users and dating each change adds no
> additional values to users. Those who want dates have a full cvs
> control to figure them out.  

+1.  However, please keep in mind that the CHANGES file is
also part of our doxygen-generated files:

  http://httpd.apache.org/~joes/libapreq2/CHANGES.html

I don't want to see the doxygen stuff pulled out entirely,
since the generated links are pretty nifty.

-- 
Joe Schaefer