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 ]

Tue, 12 Oct 2004

PyBlosxom 1.1 status

I finished taking the GRE so now I'm going to start the long process of moving everything in /contrib to the registry, moving the flavours to the registry, and then going through the steps to release PyBlosxom 1.1.

We'll do an RC and wait a week for people to speak up about issues. That puts a PyBlosxom 1.1 release around the end of October. Things that will be in the release:

We're also removing the contrib directory and all the flavour examples. This is probably going to be controversial, but I don't think we have enough polish to continue distributing them with PyBlosxom and it'll be easier to distribute fixes and such if they're separate from the PyBlosxom release.

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

Comments:

Posted by limodou on Tue Oct 12 22:45:03 2004
Wonderful!

I'v send you an email about my midification of xmlrpc_metaweblog.py and comment.py for several weeks. Did you received it ?


Posted by Jason on Wed Oct 13 11:46:15 2004
I won't put up opposition to this (and anyways, who am I in the pyblosxom world), but I will miss pulling down pyblosxom from CVS, symlinking to plugins in the contrib directory, doing my own hacks and having it all merged up on my next update :)


Posted by will on Thu Oct 14 10:20:39 2004
limodou--I did receive them.  I applied your changes to comments.py but haven't checked it in yet.  I've been kind of stuck on xmlrpc_metaweblog.py because it does some other things I'm not familiar with.  So I'm going to wait until after PyBlosxom 1.1 is out (hopefully soon).

Jason--That's a good point.  I think there are a few of us that do that.  What I think I'm going to do is move the contributed plugins to their own module in CVS.  So you should be able to do what you're doing today and other people will be able to get recent fixed versions of the plugins without us having to release new versions of PyBlosxom.  Theoretically, it should work for most peoples' use cases.


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.