[Lift] Lift Release 2.0 count-down

[David Pollak]

Folks,

I'm pleased to announce that we have a schedule for the release of Lift 2.0.

Lift 2.0 will run against Scala 2.7.7.

Here's the schedule:

• June 5th -- All features that are going into 2.0 are code complete, reviewed on review board and integrated into master.
• June 5th - 7th -- Smoke testing of the code, and bug-fixes of any defects found in the code.
• June 8th -- Lift 2.0 RC 1 is rolled out into Scala-tools.org
• June 9th - June 27th -- Community testing with new RCs rolled out on bug fixes (we'll batch up bug fixes if it looks like there are lots of bugs)
• June 28th -- Community vote on the release.  Barring any significant no votes...
• June 30th -- Lift 2.0 release

Questions?  Comments?  Feedback?

Thanks,

David

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.

[Indrajit Raychaudhuri]

Fantastic! Should we mark M6 as RC1 instead or should RC1 come out the week after M6?

- Indrajit

[David Pollak]

On Mon, May 24, 2010 at 11:09 AM, Indrajit Raychaudhuri <indr...@gmail.com> wrote:

Fantastic! Should we mark M6 as RC1 instead or should RC1 come out the week after M6?

Your call.  Whatever we drop when we freeze the code at the end of this development cycle (which I extended for 1 week to give folks time to clean up their tickets) is both M6 and RC1.  Naming is up to you.

[Heiko Seeberger]

Oops! I am very surprised that Lift 2.0 will not be built against Scala 2.8. That's really bad for my projects ...

Heiko

--
Heiko Seeberger

Company: weiglewilczek.com
Blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: scalamodules.org
Lift, the simply functional web framework: liftweb.net
Stambecco, highly scalable computing: stambecco.org

[Indrajit Raychaudhuri]

On 24-May-2010, at 11:41 PM, David Pollak wrote:

On Mon, May 24, 2010 at 11:09 AM, Indrajit Raychaudhuri <indr...@gmail.com> wrote:

Fantastic! Should we mark M6 as RC1 instead or should RC1 come out the week after M6?

Your call.  Whatever we drop when we freeze the code at the end of this development cycle (which I extended for 1 week to give folks time to clean up their tickets) is both M6 and RC1.  Naming is up to you.

Would prefer RC1 - signifying that it's not just another regular 'monthly milestone'. But between 8th and 30th we might have to spin multiple RC's though :)

- Indrajit

[David Pollak]

On Mon, May 24, 2010 at 11:26 AM, Indrajit Raychaudhuri <indr...@gmail.com> wrote:

On 24-May-2010, at 11:41 PM, David Pollak wrote:

On Mon, May 24, 2010 at 11:09 AM, Indrajit Raychaudhuri <indr...@gmail.com> wrote:

Fantastic! Should we mark M6 as RC1 instead or should RC1 come out the week after M6?

Your call.  Whatever we drop when we freeze the code at the end of this development cycle (which I extended for 1 week to give folks time to clean up their tickets) is both M6 and RC1.  Naming is up to you.

Would prefer RC1 - signifying that it's not just another regular 'monthly milestone'. But between 8th and 30th we might have to spin multiple RC's though :)

Yes, I am expecting we'll spin 2-4 additional RCs.

[Francois Armand]

Le 24/05/2010 20:20, Heiko Seeberger a écrit :
> Oops! I am very surprised that Lift 2.0 will not be built against Scala
> 2.8. That's really bad for my projects ...

My project also use the 2.8 port, and so it is not a good news for me
either.

What will be the plan to support Scala 2.8 ? It will be done trought the
"fresh Scala" project ?


--
Francois Armand
http://fanf42.blogspot.com

[Ivan Porto Carrero]

I'd also be curious to find out what lies ahead for scala 2.8 support
---
Met vriendelijke groeten - Best regards - Salutations
Ivan Porto Carrero

[walterc]

what's happening to the 2.8 support???!!!

On May 25, 2:50 pm, Ivan Porto Carrero <i...@cloudslide.net> wrote:
> I'd also be curious to find out what lies ahead for scala 2.8 support
> ---
> Met vriendelijke groeten - Best regards - Salutations
> Ivan Porto Carrero
>
>
>
>
>
> On Tue, May 25, 2010 at 8:31 AM, Francois Armand <fan...@gmail.com> wrote:
> > Le 24/05/2010 20:20, Heiko Seeberger a écrit :
> > > Oops! I am very surprised that Lift 2.0 will not be built against Scala
> > > 2.8. That's really bad for my projects ...
>
> > My project also use the 2.8 port, and so it is not a good news for me
> > either.
>
> > What will be the plan to support Scala 2.8 ? It will be done trought the
> > "fresh Scala" project ?
>
> > --
> > Francois Armand
> >http://fanf42.blogspot.com
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Lift" group.
> > To post to this group, send email to lif...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > liftweb+u...@googlegroups.com<liftweb%2Bunsu...@googlegroups.com >
> > .

> > For more options, visit this group at
> >http://groups.google.com/group/liftweb?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to lif...@googlegroups.com.
> To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.

> For more options, visit this group athttp://groups.google.com/group/liftweb?hl=en.

[David Pollak]

On Mon, May 24, 2010 at 11:50 PM, Ivan Porto Carrero <iv...@cloudslide.net> wrote:

I'd also be curious to find out what lies ahead for scala 2.8 support

Scala 2.8 is not released yet.  It is unclear when it will be released (I'm betting mid-July).  RC2 still has some non-trivial issues, especially related to JPA.  I don't know when RC3 will come out.  And we want to ship Lift 2.0 (it's already 3-4 months behind where I wanted it to be.)  So, without a solid Scala 2.8 ship date, with a lot of companies running on 2.7.7 and without a migration plan to 2.8, we have to ship Lift 2.0 as 2.7.7.

We will continue to maintain the 280_port_refresh branch (which tracks the Lift 2.0 code.)  We will likely do a full-scale effort to port all the Lift modules to Scala 2.8.0 RC3 and we will have a Fresh Scala tracking branch as well (these two branches will hopeful only be different in the pom.xml files that specify versions).

After 2.8 ships, there will be a snapshot of Lift (based on Lift 2.0 and Scala 2.8) that has all of Lift's features.

We will ship Lift 2.1 against Scala 2.7.7 and Scala 2.8... that will likely happen 3 months after 2.0 and will contain (1) fixes to 2.0 (2) minor, non-breaking enhancements to 2.0 and (3) the stable 2.7.7 and 2.8.x versions.

More globally, Scala 2.8 is not released and it's more than a year past the originally targeted release date.  The Lift project is committed to keeping up with the latest stable versions of Scala.  I am personally committed to keeping Lift up to date with the latest stable versions of Scala.  I started the Fresh Scala project so that Lift and other projects in the Scala ecosystem would have more timely, up-to-date builds and so that we can give better feedback to EPFL.  But, if you build on not-yet-released software, you are taking a risk and in this case, the cost to the risk is that you're going to have to wait until Lift 2.1 (unless Heiko or another Lift committer wants to do the 2.0 -> 2.8 release when 2.8 comes out) for a release version of Lift on Scala 2.8.x.

--
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Surf the harmonics

[Francois]

On 25/05/2010 17:36, David Pollak wrote:
[...]

>
> More globally, Scala 2.8 is not released and it's more than a year past
> the originally targeted release date. The Lift project is committed to
> keeping up with the latest stable versions of Scala. I am personally
> committed to keeping Lift up to date with the latest stable versions of
> Scala. I started the Fresh Scala project so that Lift and other
> projects in the Scala ecosystem would have more timely, up-to-date
> builds and so that we can give better feedback to EPFL. But, if you
> build on not-yet-released software, you are taking a risk and in this
> case, the cost to the risk is that you're going to have to wait until
> Lift 2.1 (unless Heiko or another Lift committer wants to do the 2.0 ->
> 2.8 release when 2.8 comes out) for a release version of Lift on Scala
> 2.8.x.

OK, great !

I do understand your point as a project leader, and I think it is a
conragous choice - at least, you are drawing the line for Lift, and it
is perhaps even more conforting for me, as a Lift "consumer": you act as
your role command.

And ok, it's not the nicest path for me (it would have been: Scala 2.8
final for April, Lift 2.0 based on Scala 2.8 on may, Tim updated book at
the same time ;), but when I chose to go with Scala 2.8 and Lift port, I
knew what was the risk :)

Thanks for the point, and good 2.0 release !

--
Francois ARMAND

[ido]

Is anybody who works on _port_refresh with scala 2.8.0.Beta1 seeing
bugs that are not
there in the 2.7.7 branch?
Do I have to look out or avoid something?

I use the 2.8 branch because of JPA annotations. And it seems to work
fine until now.

best,
ido

[Indrajit Raychaudhuri]

On 26/05/10 10:34 AM, ido wrote:
> Is anybody who works on _port_refresh with scala 2.8.0.Beta1 seeing
> bugs that are not
> there in the 2.7.7 branch?

All fixes committed to master (2.7.7) are applied to 280_port_refresh as
well.

> Do I have to look out or avoid something?

Not any known ones other than:
a. 2.8 specific open tickets in assembla
b. codes marked with "FIXME: 280" inline in 280_port_refresh

>
> I use the 2.8 branch because of JPA annotations. And it seems to work
> fine until now.

Good for you. But JPA would quite certainly break in 2.8.0.RC1 and
2.8.0.RC2 - one of the key reasons we have to stick with 2.8.8.Beta1 for
now.

>
> best,
> ido
>