Re: 3.0.20 ChangeLog progress

Okay,

So I've attached the 3.0.20 ChangeLog here for comment. I don't want to merge it into ChangeLog until it's had at least first-pass approval, plus I've listed here below a number of commit messages (and the file(s) they relate to) that I haven't yet included in the log, grouped under relevant headings; please suggest whether each should be added or not.


Put this in the ChangeLog or just in the announcement?


  - Enable tolerate-pipelining for the beta as discussed on ijbswa@

doc/source/p-config.sgml, 






Are all of these covered by other items I've already added to the ChangeLog? 


  - Set the SERVER_CONTENT_LENGTH_SET flag after creating a new Content-Length header

This allows to keep the client connection alive after
filtering a chunk-encoded response.

parsers.c, 


  - Allow serve() to keep client connections open if the response content length is zero

jcc.c, 


  - Keep track of how many requests have been received on a client socket

jcc.c, project.h, 


  - Keep track of how many request are sent through a server connection

gateway.c, jcc.c, project.h, 


  - Figure out the request length before running sed()

We may want to adjust the Connection header based on the information.

jcc.c, 


  - Add get_expected_content_length()

parsers.c, parsers.h, 


  - Let get_content_length() use a header value as input instead of the whole header

This makes it easier to use it in combination with get_header_value().

parsers.c, 





Can't find reference to this keyword in the documentation, and don't know how to represent it in the ChangeLog. Presume it's a new feature?


  - Mention the shiny new LOG_LEVEL_ACTIONS

doc/source/p-config.sgml, 


  - Add LOG_LEVEL_ACTIONS to log the applying actions

Unlike in the "Final results", the effect of tags is taken into account.

actions.c, actions.h, errlog.c, errlog.h, jcc.c,





 
 

Presume these are internal to the project and don't need entries in ChangeLog?


  - Redirect requests for http://config.privoxy.org/.* to http://www.privoxy.org/config/

config.privoxy.org used to be a separate server that was
administrated by Andreas, but will be relocated to the SF
webserver after the domain transfer is done.

Note that the things SF calls VHOSTS all point to the
same root directory, so we can't use a dedicated .htaccess
file for config.privoxy.org.

doc/webserver/.htaccess, 


  - Adjust attribution and fix the URL of this file on the server

doc/webserver/.htaccess, 




Thanks all,

Ian



On 2013-01-09, at 7:06 AM, Ian Silvester wrote:

> 
> On 2013-01-09, at 5:06 AM, Fabian Keil wrote:
> 
>> Ian Silvester <[email protected]> wrote:
>> 
>>> Another question - should I specify each and every case of comment tidying or just add a general "various typo corrections and comprehensibility improvements"?
>> 
>> As comments affect neither the binary nor the user I don't think
>> each modification has to be explicitly mentioned.
> 
> Phew. I was hoping you'd be of that opinion!
> 
>> In my opinion typo corrections for the documentation can be combined
>> like you suggested unless the typo caused a lot of confusion. For example
>> if a directive was consistently written wrong and the user was thus
>> unable to use it without checking the sources.
>> 
>> I don't think that ever happened, though.
>> 
>> In general our ChangeLog is already pretty verbose compared to
>> ChangeLogs from other projects
> 
> Yes, I'd noticed!! Still, it has bugged me previously that a project I use fixed a minor issue that affected me but didn't say so in it's changelog so I'd upgrade in hope and only find out that the fix was present when using the software, so I think we're doing the right thing.
> 
>> and combining a few more entries
>> probably wouldn't hurt. For example it's unclear how many users
>> really care about a detailed "Log message improvements" section.
> 
> I'll see what things look like when I've finished taming the beast (who knew there'd been so many commits in only one year!) and take a view on how many separate sections to include.
> 
> Should be finished today or tomorrow,
> 
> Ian
> 
> 
> 
>> 
>> Fabian
>> ------------------------------------------------------------------------------
>> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
>> and much more. Keep your Java skills current with LearnJavaNow -
>> 200+ hours of step-by-step video tutorials by Java experts.
>> SALE $49.99 this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122612 _______________________________________________
>> Ijbswa-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/ijbswa-developers
> 
> 
> ------------------------------------------------------------------------------
> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
> and much more. Keep your Java skills current with LearnJavaNow -
> 200+ hours of step-by-step video tutorials by Java experts.
> SALE $49.99 this month only -- learn more at:
> http://p.sf.net/sfu/learnmore_122612 
> _______________________________________________
> Ijbswa-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ijbswa-developers

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712

_______________________________________________
Ijbswa-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ijbswa-developers