Zine

Re: Soon there will be a new Zine Release

From:

Michael Crute

Date:

2010-06-18 @ 16:00

Subject:

Re: Soon there will be a new Zine Release

On Fri, Jun 18, 2010 at 10:32 AM, Armin Ronacher
<armin.ronacher@active-4.com> wrote:
> Just want to point out that there will be an upcoming Zine release.
> This is what for a long time should have become 0.2 but I think I will
> push the version number to 0.9.  My expectations for Zine are kinda down
> so I think what there is now + a few more small fixes could become a
> good 1.0 version.
>
> Please play around with the current development version: it has
> migration support and tons of new features compared to 0.1.2.

I did a lot of work to pull together the latest patches and do some
other needed fixes. These are located in my branch at
http://bitbucket.org/mcrute/zine-main. Can you merge those changes
before you do the release?


-- 
Michael E. Crute
http://mike.crute.org

It is a mistake to think you can solve any major problem just with
potatoes. --Douglas Adams

+1 to mcrute's question

A while back I sent an email to the list (which was completely
ignored) about a group of us in the Cleveland area wanting to
revitalize Zine.  Mike spent a decent amount of time trying to
unify all of the important bits from Zine's many forks.  I'd
personally consider it an open source tragedy if his work were
not *at least* reviewed... so please don't let that happen ;-)

</rant>

-- 
~Dan

On Fri, Jun 18, 2010 at 12:00:24PM -0400, Michael Crute wrote:
> On Fri, Jun 18, 2010 at 10:32 AM, Armin Ronacher
> <armin.ronacher@active-4.com> wrote:
> > Just want to point out that there will be an upcoming Zine release.
> > This is what for a long time should have become 0.2 but I think I will
> > push the version number to 0.9.  My expectations for Zine are kinda down
> > so I think what there is now + a few more small fixes could become a
> > good 1.0 version.
> >
> > Please play around with the current development version: it has
> > migration support and tons of new features compared to 0.1.2.
> 
> I did a lot of work to pull together the latest patches and do some
> other needed fixes. These are located in my branch at
> http://bitbucket.org/mcrute/zine-main. Can you merge those changes
> before you do the release?
> 
> 
> -- 
> Michael E. Crute
> http://mike.crute.org>
> 
> It is a mistake to think you can solve any major problem just with
> potatoes. --Douglas Adams

Hi,

On 6/19/10 3:32 AM, Dan Buch wrote:
> A while back I sent an email to the list (which was completely
> ignored) about a group of us in the Cleveland area wanting to
> revitalize Zine.  Mike spent a decent amount of time trying to
> unify all of the important bits from Zine's many forks.  I'd
> personally consider it an open source tragedy if his work were
> not *at least* reviewed... so please don't let that happen ;-)
I already pulled from mcrute/zine-main this afternoon.  If there is 
anything else I missed that should be merged, please let me know.


Regards,
Armin

On Sat, Jun 19, 2010 at 03:39:33AM +0200, Armin Ronacher wrote:
> Hi,
> 
> On 6/19/10 3:32 AM, Dan Buch wrote:
> > A while back I sent an email to the list (which was completely
> > ignored) about a group of us in the Cleveland area wanting to
> > revitalize Zine.  Mike spent a decent amount of time trying to
> > unify all of the important bits from Zine's many forks.  I'd
> > personally consider it an open source tragedy if his work were
> > not *at least* reviewed... so please don't let that happen ;-)
> I already pulled from mcrute/zine-main this afternoon.  If there is 
> anything else I missed that should be merged, please let me know.

hottt!
I take all rants back!

> 
> 
> Regards,
> Armin

On Fri, Jun 18, 2010 at 8:02 PM, Armin Ronacher <armin.ronacher@active-4.com
> wrote:

> Just want to point out that there will be an upcoming Zine release.
> This is what for a long time should have become 0.2 but I think I will
> push the version number to 0.9.  My expectations for Zine are kinda down
> so I think what there is now + a few more small fixes could become a
> good 1.0 version.
>

I have been out of sync with Zine for a while. My tree was incompatible with
zine-main in that it stored keywords for the post as JSON instead of a
Python pickle.

Has there been any change on that? I haven't been working on Zine, so I want
to discard my tree and work off main, but also have an existing blog to
migrate.

Hi,

On 6/18/10 6:46 PM, Kiran Jonnalagadda wrote:
> I have been out of sync with Zine for a while. My tree was incompatible
> with zine-main in that it stored keywords for the post as JSON instead
> of a Python pickle.
Indeed.  I remember that someone implemented JSON for these things.  Do 
you know which repository you pulled from?


Regards,
Armin

Hi,

On 6/18/10 7:49 PM, Armin Ronacher wrote:
> Indeed.  I remember that someone implemented JSON for these things.  Do
> you know which repository you pulled from?
Just did a bit of annotation:

(env)mitsuhiko@nausicaa:~/Development/zine-main$ hg log -r 1038
changeset:   1038:800638fae864
user:        Kiran Jonnalagadda <jace@pobox.com>
date:        Sun May 24 15:34:37 2009 +0530
summary:     Undid JSON storage changes from revision 1024:b190c3739a78. 
They'll be reintroduced via a database upgrade.


Regards,
Armin

Re: Soon there will be a new Zine Release

From:

Michael Foord

Date:

2010-06-18 @ 17:22

Subject:

Re: Soon there will be a new Zine Release

On 18/06/2010 15:32, Armin Ronacher wrote:
> Hi,
>
> Just want to point out that there will be an upcoming Zine release.
> This is what for a long time should have become 0.2 but I think I will
> push the version number to 0.9.  My expectations for Zine are kinda down
> so I think what there is now + a few more small fixes could become a
> good 1.0 version.
>
> Please play around with the current development version: it has
> migration support and tons of new features compared to 0.1.2.
>
>    

Awesome news.

Michael

> Regards,
> Armin
>    


-- 
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.