Richard, Ethan, Vassil

Thank you for your efforts and help. I'm very happy that Lift 2.2 branch has
been merged into trunk.

2011/1/6 Richard Hirsch <[email protected]>

> @Ethan - Thanks - I'll do a stax deployment based on the trunk on
> Monday when I return to work.
>
> D.
>
> On Thu, Jan 6, 2011 at 7:35 PM, Ethan Jewett <[email protected]> wrote:
> > Ok, all set. All the Lift 2.2, Scala 2.8.1, SBT, and removal of
> > deprecated methods should now be in trunk. All tests are passing in
> > both Maven & SBT, though SBT is still suffering from the Ivy cache
> > problem so tests don't pass for the first couple runs.
> >
> > A big thank you to Vladimir for all the work on this! :-)
> >
> > Ethan
> >
> > On Thu, Jan 6, 2011 at 7:20 PM, Ethan Jewett <[email protected]> wrote:
> >> Should be done in a few minutes. Just testing and sorting out a couple
> >> of tree conflicts that I think happened due to me merging trunk into
> >> the branch a while ago and then attempting to merge the original
> >> version of the branch into trunk....
> >>
> >> Ethan
> >>
> >> On Thu, Jan 6, 2011 at 6:22 PM, Richard Hirsch <[email protected]>
> wrote:
> >>> Looks like the Lift 2.2 release is finished:
> >>>
> http://groups.google.com/group/liftweb/browse_thread/thread/240f60d91a1af2c4/d284eeca820e391a?show_docid=d284eeca820e391a
> >>>
> >>> @Ethan - would you be so kind as to migrate the 2.2 branch into the
> trunk.
> >>>
> >>> Thanks.
> >>>
> >>> D.
> >>>
> >>>
> >>> On Mon, Jan 3, 2011 at 6:47 PM, Richard Hirsch <[email protected]>
> wrote:
> >>>> I just looked at the lift mailing list.  It looks like RC6 will be the
> >>>> final 2.2 release. Ethan - why don't you upgrade the pom.xml in the
> >>>> branch to RC6 and then we can run a few tests. When 2.2 final is
> >>>> officially released, then we'll merge the branch to the trunk and
> >>>> update to the 2.2 final (no RC) version.
> >>>>
> >>>> D.
> >>>> On Mon, Jan 3, 2011 at 5:46 PM, Ethan Jewett <[email protected]>
> wrote:
> >>>>> t
> >>>>
> >>>
> >>
> >
>



-- 
Best Regards,
Vladimir Ivanov

Reply via email to