Re: 3.0.20 regression testing

Ian Silvester <[email protected]> wrote:

> On 2013-01-05, at 8:03 AM, Fabian Keil wrote:
> 
> > Ian Silvester <[email protected]> wrote:
> > 
> >> On 2013-01-04, at 8:36 AM, Fabian Keil wrote:

> > At the moment the missing pieces known to me are:
> > 
> > - Writing the ChangeLog based on the commits that happened since
> >  the previous release.
> 
> I'll do this.
> 
> > - Reintegrating the ChangeLog in the documentation, which isn't
> >  completely automated.
> 
> I can do this if you can explain how.

I usually start by dumping the relevant commit log into the ChangeLog:
git log v_3_0_19 >> ChangeLog

and then edit the ChangeLog to throw away commit messages that
don't affect the release and don't require crediting.

For example if a user reported a regression that only existed in CVS
it's still worth mentioning in the ChangeLog as the problem might have
otherwise made it into the release unnoticed.

Commit messages have to be reformatted and usually slightly
reworded so someone less familiar with Privoxy's internals
can understand them.

The ChangeLog has a special format so that it can then be translated
with utils/changelog2doc.pl to SGML and (currently manually) inserted
into the user manual source. Using the converter script is optional,
but in my biased opinion is less painful than doing the SGML by hand.

As can be expected, this occasionally causes syntax errors
that have to be addressed by either modifying the ChangeLog
so it can be properly converted, by modifying the converter,
or by manually fixing the problem if it's trivial.

I always try to do the ChangeLog conversion once when it's done,
but there are usually last-minute problems which I only notice
after the checking the conversion result ...

> > - Writing the announcement.
> 
> I'll do this.

The text to edit is:
doc/webserver/announce.txt

It usually has a small summary followed by the ChangeLog text
(and is thus also affected by last-minute ChangeLog fixes).

> > - Rebuilding the documentation and various other things for
> >  "3.0.20 beta".
> 
> I've tried damned hard but cannot do this! Neither Fink nor Macports have
> what it takes to get the toolchain running correctly and OS X is my only OS.

No problem. Just let us know when you are done with the ChangeLog
text so we can take over without causing merge conflicts.

> > - Proof reading and fixing the problems found.
> 
> Happy to do this.

That's great, hopefully everybody else does, too.

> I'll start on all the above this week (get more time during the work day
> than at the weekends, what with two young kids to entertain ;o)

Awesome.

Fabian

------------------------------------------------------------------------------
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_123012

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlDpdMwACgkQSMVSH78upWPM8gCdHtNBLWuZ6YRizANlPLmhQo8e
rk8AmgK5WhuZSZJ1iwJQNgfCmQyRTvrX
=hhxI
-----END PGP SIGNATURE-----