Re: PyBlosxom 2.0 status 7/27/2008

holy crap. that's awesome! the 300% increase in tests alone is huge, but of 
course, i'm also psyched to hear that you think there's measurable progress on 
2.0. congratulations!!!

hope oscon went well...

On Sun, 27 Jul 2008, will wrote:

> I was at OSCON last week and in the process of going to and coming back
> from OSCON, I had some time on the airplane and in various airports that
> had ass-tastic wireless access (i.e. non-free or non-existent) to work
> on PyBlosxom.
>
> I've switched my development system to use git over svn.  This makes it
> _much_ easier for me to stage work on the various things I'm working on.
>  It also makes it easier for me to work on things without access to the
> Internet without creating massive checkins with unrelated changes.
>
> The ramifications of this are that I'm now checking in batches of
> commits all at once.
>
> In the last week, I got my testing groove on:
>
> * I fixed the existing tests we had so that they're better.
> * I added a bunch of new tests--we went from 53 or so to 207.
> * I increased test coverage to 57% from some number lower than that.  :p
> * I added a bunch of tests that makes sure PyBlosxom works correctly
> with utf-8.
>
> In the process of doing that, I fixed a bunch of problems.  I was also
> able to adjust some critical sections to run faster.  I'm also cleaning
> things up so that it's easier to read and easier to hack on.
>
> I'm happy with the last week of development.  The code is evolving into
> better, provably correct code.  This in turn will make PyBlosxom more
> stable than it has been in the past.
>
> In the interim between now and when trunk stabilizes, it's very likely
> that trunk won't work with some/many plugins.  I'm working on backwards
> compatibility to reduce plugin breakage, but it's not my current focus.
>
> Given that, consider trunk to be _UNSTABLE_ until someone deems it
> otherwise.  Feel free to play around with it and test it.  Don't bother
> spending time to re-write plugins to work with it--it's a moving target.
>  If it's any indication of instability, I'm not running up-to-date
> trunk on my site right now.
>
> I want to finish 2.0 as soon as possible, but until last week, I hadn't
> spent much time on it.  I'm hoping that will change in the near future.
>  I'd love to finish up development in August--we'll see how far I get
> with that.
>
> It feels good to be able to write a status report with measurable
> progress behind it.  Whew!
>
> Thank you all for your patience.
>
> /will
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Pyblosxom-devel mailing list
> Pyblosxom-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/pyblosxom-devel
>

-Ryan

--
http://snarfed.org/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/