Re: getting ready for a pyblosxom 1.4 release

will <[email protected]> writes:

> I've got spring break this coming week and I'll be able to do some
> work.  But after that I won't be able to fit in much work until May
> after my semester is over.  Given that, I think we have the following
> options:
>
> 1. release what we have now
> 2. wait until the work is done and release then
> 3. find some more people to help do the work

I'd recommend Option 1.  It's more important to have frequent releases
than to meet every single goal.  Better is to push the unit testing
goal to the release after this, IMHO.

-- 
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net
  /` |\ | | | Projects: Emacs, Muse, ERC, EMMS, Planner, ErBot, DVC
 |_] | \| |_| Reclaim your digital rights by eliminating DRM.
      See http://www.defectivebydesign.org/what_is_drm for details.

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

iD8DBQFF6PGG+1Ho2POo0xkRAt4yAKChQzXO6BI+y2Xb5QoGyMj3+VBvkQCgmMGB
wiyOk+DQbIbBl94jdEl/sos=
=zvgN
-----END PGP SIGNATURE-----