Lein 2? (again)

[Sean Corfield]

Leiningen 2 is at preview 10 and the Leiningen team are recommending
everyone move off Leiningen 1.x at this point (well, they've been
recommending that for a while).

Some of the committers here feel that we should wait for the "stable"
release of Leiningen 2 before moving but I've moved every project I
work on to 2.0 at this point - including running Leiningen 2.0 on
production servers to manage various processes - so I thought I'd push
for approval again...

And Raynes is giving me grief in IRC about CongoMongo being a hold out
on Leiningen 1.x :)
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)

[Steve Purcell]

Yeah, go for it.

[Dave Ray]

If lein2's ready for production use, it should be released and drop the alpha-y sounding "preview" label. If it's not, people shouldn't feel pressured into using it. I've been using it for new projects and haven't had any problems. On the other hand, for existing projects, I'm waiting for a real release so I only have to go through the upgrade gauntlet once.

Cheers,

Dave

[Bruce Durling]

I did have some problems with preview 8 around out of memory issues,
but I believe they are fixed now.

cheers,
Bruce

--
@otfrom | CTO & co-founder @MastodonC | mastodonc.com

[Dave Ray]

Oh yeah. I guess I did have lein2 problems. Forgot about that :)

[Sean Corfield]

On Wed, Sep 12, 2012 at 7:20 AM, Dave Ray <dav...@gmail.com> wrote:
> If lein2's ready for production use, it should be released and drop the
> alpha-y sounding "preview" label.

The #leiningen IRC channel says RC1 is due real soon now... The
remaining open issues before 2.0.0 gold are:

https://github.com/technomancy/leiningen/issues?milestone=3&page=1&state=open

> If it's not, people shouldn't feel pressured into using it.

Well, if folks don't try switching existing projects over before the
2.0 release, it's more likely that bugs will not be found until after
that release. I'd rather bugs be found sooner so the more projects
that move to 2.0 during the preview phase, the better IMO :)

Given the overall feedback, I'm going to take on the congomongo
upgrade to 2.0.0 myself today.

[Dave Ray]

 

Given the overall feedback, I'm going to take on the congomongo
upgrade to 2.0.0 myself today.

I appreciate you doing the leg-work for Luddites like myself :)