Re: Running 2.0dev

2.0 isn't stable.  I'm still making a bunch of changes and the changes 
definitely haven't been carried through to plugins.

If your expectation is for something stable with plugins you don't have 
to mess too much with, I'd go with 1.4.3.

If your expectation is to help me finish 2.0 (hopefully sooner rather 
than later), and help me flesh out idiot decisions I'm making with the 
changes, I'd go with 2.0.

As a side note, I'm running my blog with the 2.0 branch, though I 
haven't updated in a few months.  I was waiting until I figured my way 
through the formatter changes and then carried those fixes through to 
plugins that I use.

As another side note, there's no reason you can't run your blog with 
1.4.3 and help me test 2.0.  Grab it with svn checkout, follow the notes 
in README and INSTALL, and then deploy it with instructions in the wiki. 
  The easiest way to deploy locally without affecting anything is with 
Paste:

http://pyblosxom.sourceforge.net/wiki/index.php/DeploymentPaste


Mario Fernández wrote:
> Hi,
> 
> I tried to use 2.0 a couple of weeks ago, but got a variety of  
> problems, so I stayed with 1.4.3. For the plugins I usually take the  
> last version though.
> 
> Cheers,
> Mario
> 
> On May 28, 2008, at 6:35 AM, David Pratt wrote:
> 
>> Hi. I am thinking about hacking pyblosxom and don't want to waste the
>> effort on legacy code. I see you are running 2.0dev for your own blog.
>> Can someone tell me how volatile 2.0 is? Many thanks.
>>
>> Regards,
>> David

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/