[prev in list] [next in list] [prev in thread] [next in thread] 

List:       muse-user
Subject:    Re: Apache muse2.0 queries
From:       "Pushkar Sachdeva" <pushkarsachdeva () gmail ! com>
Date:       2006-06-28 13:42:55
Message-ID: 391aa3d20606280630k5391d90fn131a653aba024d77 () mail ! gmail ! com
[Download RAW message or body]


Thanks a lot Dan.

On 6/27/06, Daniel Jemiolo <danjemiolo@us.ibm.com> wrote:
>
> Hi Pushkar,
>
> The latest release of Muse is/will be a development milestone, which means
> it's not at full beta yet. We have created a stable driver for our
> development team to reference and build against, and we will likely create
> a few more before the code is ready to be supported as a beta or final
> release. In other words, don't rush to upgrade yet! :)
>
> To answer your questions:
>
> 1) No - it is based on a new programming model and supports the new specs
> from OASIS (WSDM 1.1 and dependencies)
>
> 2) The team has agreed to a six-week release cycle, and a persistence API
> will be provided in the next milestone, so it should be available by
> mid-August. Again, this will be a milestone, but we'd love for you to look
> at the API and provide feedback before/after that milestone is released.
> Watch muse-dev for an email proposal for this API in the next week or so.
>
> Dan
>
>
>
> "Pushkar Sachdeva" <pushkarsachdeva@gmail.com> wrote on 06/27/2006
> 04:39:37 AM:
>
> > Hi all,
> >
> > I have been using muse1.0, now as beta for muse2.0 is out, I want to
> upgrade
> > my application to muse2.0. So i have the following queries regarding
> this:-
> >
> > 1) Is muse2.0 downward compatible with muse1.0??
> > 2) When can we expect muse2.0 being released with persistence API
> > incorporated??
> >
> > Please help me ..
> >
> > Thanks in advance.
> > -Regards
> > Pushkar
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>


[prev in list] [next in list] [prev in thread] [next in thread]