Re: getting ready for a pyblosxom 1.4 release

will wrote:

> This is useful to know.  I figure the more people that are running svn
> trunk, the more likely it is that there aren't any major issues
> floating around.  Until we flesh out the unit and regression testing,
> we're still doing most of our testing by anecdotal-testing methods.
> :(
> 
> /will

I agree w/ Ryan. Code clean-up, docs, and the like shouldn't be
sufficient for a full dot release when testing was one of the conditionals.

I'm not running svn, as I started w/ the Debian packages and they work
well enough for me. I'll migrate this weekend if I can find the time and
see what's up. I've been spending so much time with TurboGears that I've
been neglecting other projects. :)

Cheers,
lance
-- 
Lance Levsen,
Catprint Computing
Tel:  (306) 493-2249
Cell: (306) 230-8783
Blog: http://www.catprint.ca/blog/
SaskBlogs: http://saskblogs.catprint.ca/

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Pyblosxom-devel mailing list
Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF6EwxWSOc2vLaecgRArNAAKDcfqKPXo6PKJoqYO4biQwMjcd2ogCfS8Iv
pg1/oUGIhk8mEwy5kP2Exso=
=r96c
-----END PGP SIGNATURE-----