Will's blog

purpose: Will Kahn-Greene's blog of Miro, PyBlosxom, Python, GNU/Linux, random content, PyBlosxom, Miro, and other projects mixed in there ad hoc, half-baked, and with a twist of lemon

[ home | blog home | recent activity ]

Wed, 30 Jun 2004

Thinking about releasing a 1.0.1

I think I may release 1.0.1 this weekend depending on what else is going on life-wise. I tossed a feeler email out to the dev list in regards to what else should be fixed for 1.0.1, but didn't get anything back--which isn't surprising as people are pretty busy these days.

So... to do a release or not--that is the question. Is there anyone reading this blog who has things that they'd like to see for a very minor fix-it point release that's doable by one man who only has a bit of free time (unless they're interested in sending in a patch)?

[ tags: dev, pyblosxom, python | category: /dev/pyblosxom | Permalink | View/Add Comments: 2 ]

Comments:

Posted by Adam Shand on Wed Jun 30 22:38:59 2004
The main thing I'd like is for pyblosxom to ship in a way so it has the standard plugins enabled (category, archives, calendar, search, blogger api, etc) and a simple theme that uses all of these things.  This would make getting a blog up and running much easier (it's generally easiest to start with something that has more features then you need and tweak then to figure out how to enable and configure things).

Apologies if this has been done recently and I missed it.


Posted by wari on Wed Jul 7 03:56:37 2004
somewhat of a valid point there, but we probably don't want to dictate things like where plugins go to, etc.. Or maybe we do... hmm. This would probably make sense on a site wide installation, something that a debian or RPM packager would do, but he/she will probably be beaten to death on what is standard and what is not.


Post a new comment:

Three things:

  1. New comments get placed in a "draft" status and will NOT show up on the site until I explicitly approve it. Sometimes that happens within 24 hours.
  2. I reserve the right to reject/remove inappropriate comments.
  3. Sometimes I'll reply to a comment directly in email--so make sure your email address is correct.

If you can't for some reason post a comment, send me an email: willg at bluesock dot org.

Your name:


Your e-mail address (this doesn't get displayed to anyone--sometimes I'll reply directly to you):


URL of your website (optional):


Comment:


Yes, I am a human!

pyblosxom::1.5-dev git-master

Copyright 1996 to 2012, Will Guaraldi Kahn-Greene, under the Creative Commons BY-SA 3.0 license

Creative Commons License
Will's Blog by William Kahn-Greene is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.