Re: 3.0.20 regression testing

Ian Silvester <[email protected]> wrote:

> On 2013-01-04, at 8:36 AM, Fabian Keil wrote:

> > Whether or not the user-manual directive is enabled by default
> > is up to the packager.
> > 
> > The advantage for the user is that Privoxy will serve the manual itself,
> > which is a lot faster (at least when also using Tor) and also prevents
> > SF (and us) from monitoring the requests:
> > http://www.privoxy.org/user-manual/config.html#USER-MANUAL
> > 
> > From a packaging point of view the disadvantage is that it requires
> > knowledge about where the user manual will be located. For some packages
> > the location may depend on the user and dealing with dynamic locations
> > can be messy.
> 
> Thanks for enlightening me. Whilst my package allow choice of installation
> drive the relative locations of all elements are fixed, so I can indeed take
> advantage of this feature with relative ease. I'll look into modding my
> packaging tools to do so.

And it even looks like this has already be done which
I'm sure will positively affect the user experience.

> > Without the directive the skipped tests aren't expected to work,
> > so as long as the directive is intentionally not used everything
> > looks indeed fine.
> 
> Great. I presume it's your call as to when the freeze on 'current'
> will occur; just let us know when the tagging's been done and I'll
> get building the 3.0.20 beta release set for OS X.

While in the last years I've been usually the one doing the tagging,
this was less because I consider it my call, but because I ended up
being the one doing the last commits that were still missing,
so tagging was the next logical step.

At the moment the missing pieces known to me are:

- Writing the ChangeLog based on the commits that happened since
  the previous release.
- Reintegrating the ChangeLog in the documentation, which isn't
  completely automated.
- Writing the announcement.
- Rebuilding the documentation and various other things for
  "3.0.20 beta".
- Proof reading and fixing the problems found.
- More testing.
- Adjusting Privoxy-Log-Parser to properly deal with changed log
  messages when generating statistics (or verifying that it works
  as expected which I doubt).

Everything but the last one is (in my opinion) really boring and
takes a surprising amount of time (and blood, sweat and tears).
I don't consider doing them a privilege, but someone has to do it.

Back in the days that someone was Hal, who also did the announcements.
From my point of view that was a pretty sweet deal and I only see
myself as an "interim Hal", until somebody else takes over.

Assuming nobody accepts that challenge I intent to start working
on all those issues this weekend.

My current estimate is that getting it done before next weekend
might not be realistic. This is fine with me, though, as we have
no exact release date yet anyway.

Once the issues (and any issues anyone else might want to bring up)
are addressed, I think we're ready for tagging and could release
a few day later.

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. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912

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

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

iEYEARECAAYFAlDoJJIACgkQSMVSH78upWOxIQCfe2bonAOCdjofVF6exn79MUPI
JpgAnig3LMS167/xsi47WtI2maX0UlBK
=o75N
-----END PGP SIGNATURE-----