Thanks for the heads- up Vladimir. I'll try to increment the pom.xml version and test it out soon. Fingers crossed that the final release is soon.
All, we discussed merging the branch back into trunk, and I can do that whenever necessary. What is not clear to me is whether I should wait until Lift 2.2 final is cut or if we should proceed with the release candidate. If we merge the branch then I think we *must* wait until Lift 2.2 final before we do an ESME release. I doubt we'll beat the Lift release out the door, but anything is possible ;-) Thoughts? Ethan On Sun, Jan 2, 2011 at 10:34 AM, Vladimir Ivanov <[email protected]> wrote: > Lift 2.2-RC6 has been announced: http://lift.la/announcing-lift-22-rc6 > > 2010/12/22 Richard Hirsch <[email protected]> > >> I haven't committed the change to the branch, because we currently >> have a svn authorization problem. >> >> D. >> >> On Wed, Dec 22, 2010 at 9:38 AM, Richard Hirsch <[email protected]> >> wrote: >> > RC4 is now deployed on stax. >> > >> > I also committed the change to the branch. >> > >> > D. >> > >> > On Tue, Dec 21, 2010 at 6:52 PM, Vladimir Ivanov <[email protected]> >> wrote: >> >> Lift 2.2-RC4 version was announced: >> http://lift.la/announcing-lift-22-rc4 , >> >> with three issues fixed. >> >> >> >> Should this new version be used? >> >> >> >> 2010/12/21 Richard Hirsch <[email protected]> >> >> >> >>> Are we ready to migrate the 2.2 branch (which is really based on lift >> >>> 2.3) back into trunk? >> >>> >> >>> I think so. We've fixed all of the open bugs that were related to the >> >>> branch. >> >>> >> >>> What do others think? >> >>> >> >>> D. >> >>> >> >> >> >> >> >> >> >> -- >> >> Best Regards, >> >> Vladimir Ivanov >> >> >> > >> > > > > -- > Best Regards, > Vladimir Ivanov >
