OK, Analysis 2.0.5 is alive now. And for people who did happen to save
their project while the API was broken in 2.0.4, I think it ought to load
ok in 2.0.5 (and it's possible, like I said below, that it would also have
opened ok in the backtracked 2.0.4).
Wayne
On Fri, 17 Oct 2008, Wayne Boucher wrote:
> Hello,
>
> Rasmus, really, really wanted that API change in (because one of our
> collaborators requires it; it is a change which nobody else should need or
> should notice, famous last words). So I'm now creating a new, 2.0.5,
> release for Analysis, which will have that change in it. This means that,
> from half an hour or so from now, the next time anyone updates, they will
> get this installed instead of the 2.0.4 updates.
>
> Wayne
>
> On Fri, 17 Oct 2008, Wayne Boucher wrote:
>
> > Hello,
> >
> > After investigation it became clear that there was no easy way to fix the
> > broken API problem as it was.
> >
> > So I have backtracked the API-specific code on the update server to be the
> > same as it was when the 2.0.4 release was made.
> >
> > For people who have not updated in the last day this should mean you do
> > not notice anything wrong.
> >
> > For people who have updated in the last day this means you should update
> > again, to get back the original API.
> >
> > For people who have updated in the last day and saved a project using this
> > broken API, we might have to fix your
> > PROJECT_DIR/ccp/nmr/Nmr/*.xml file by removing a bogus attribute from the
> > DataDimRef entries (but we might not, Rasmus would have a better idea
> > about this). Let us know if you do notice a problem.
> >
> > Sorry about this, but one lesson we have learned is that the API can never
> > really be updated via the update server, unless all of it is updated that
> > way.
> >
> > Wayne
> >
>
|