Re: getting ready for a pyblosxom 1.4 release
Ryan Barrett <pyblosxom-6sb6M7qyT/[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 2 Mar 2007, Michael Olson wrote: > 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. good point. i can't really argue with release early, release often. :P as long as releasing doesn't take more than an hour or so of will's time, i'll withdraw my complaint and say, go for it. i'd lean toward making it a patch release (1.3.3) rather than a minor release (1.4), but that's just my vote. -Ryan -- http://snarfed.org/ ------------------------------------------------------------------------- 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