Re: getting ready for a pyblosxom 1.4 release

On 3/2/07, Lance Levsen <lance-8fVGZEMlguYsA/[email protected]> wrote:
>
> 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.

Hrm...  I think I didn't really get across what I was trying to get
across accurately.  I had the following in the TODO pertaining to
release 1.4--and this was mildly arbitrary:

MILESTONE VERSION 1.4
=====================

Prospective release date: February sometime.

UNIT TESTING

 - Look at the Cheesecake system and use something similar so that we
   have some basic tests we can run that test the whole system.

MANUAL

 - Go through and fill in more FIXMEs.
 - Add instructions for PyBlosxom with FastCGI.
 - Add instructions for servers with multiple users (look at Martin Kraaft's
   stuff).

PYBLCMD

 - Finish up pyblcmd so that it's a good alternative to running
   pyblosxom.cgi.


Of which I've completed the PYBLCMD portion, I've made some head way
on the UNIT TESTING portion (I want to finish the changes that allow
someone to do "python setup.py test" and run the test harness), and
made some headway on the MANUAL portion, as well.

But if you look at the CHANGELOG file, you'll see a bunch of things
that are worth a release:


Changes between 1.3.2 and 1.4
=============================

Pertinent to users:
-------------------

1. Added a pyblcmd command line program for PyBlosxom command line
   things.  This now handles static rendering, rendering a single
   url to stdout, testing your blog setup, ...

2. The Atom story template now has a $default_flavour bit in the link.
   Bug 1667937.  (Thanks Michael!)

3. PyBlosxom is now locale aware in respects to dates, months, days of the
   week and such.  Users should set the "locale" config property to a
   valid locale if they don't want English.

4. Added a $blog_icbm config variable, for use in the ICBM meta tag.

5. Changed the num_entries property in config.py from 40 to a much more
   conservative 5.
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373658
   (Thanks Jon!)

6. Changed the self link in the atom feed to be of type
   application/atom+xml.
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403008
   (Thanks Brian!)

7. Added DOCUMENT_ROOT to the python path per Martin's suggestion.
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367127
   (Thanks Martin!)


Pertinent to developers:
------------------------

1. Lots of code clean-up, documentation, test-code, and some refactoring.

2. cb_filestat will only do an os.stat if no plugin handles the filestat.
   Previously, cb_filestat did an os.stat and ran through all the
   plugins allowing them to over-ride it.

3. Moved documentation docbook files form /doc to /docsrc figuring it
   makes more sense because they need to be "compiled" before they're
   useful.


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

Options 1 and 2 are doable.  I was figuring that option 1 was better
because some of the fixes that are in svn trunk right now fix issues
that people are having now.  But I'm ok with doing option 2.  Option 3
I think sucks up too much of my time unless one of the existing
developers wants to help out.  Otherwise I'll just be spending time
bringing someone up to speed and I might as well just do the work
myself but I really don't have time to and the paradox is complete.
;)

I'm definitely all ears about other thoughts, options and other ways
we could go with this.

/will

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