Maybe I should rephrase my original question. "Safe" is a loaded word I suppose.

My question really is: has the API stabilized? I've spent weeks making custom templates. When the RC's were coming out, I got the impression that any work I did porting my templates to the new API's may need to be re-ported for each RC and final release. I didn't look forward to repeating the work so many times. So my question really is, if I port my custom templates now, will I have to port again with the next release?

And any other information concerning upgrading would be welcome.

--

Thanks,

James Reynolds - University of Utah - Student Computing Labs - 801-585-9811 james(a)scl.utah.edu - james(a)magnusviri.com - http:// james.magnusviri.com



On Dec 13, 2006, at 8:57 AM, Boris Kraft wrote:

On 12 Dec 2006, at 1:55 AM, James Reynolds wrote:

I've taken a little Magnolia break while I've waited for the changes in Magnolia to settle down so that I can safely upgrade my custom templates to 3.0. By safely, I mean during the RC period, the API's were changing and any upgrading I did may be invalidated out by a new RC.

So have changes slowed down?  Is it safe to upgrade?

Also, is there documentation on what has changed anywhere? Periodically I've read up on what is being said on the user list, but the RC period lasted a lot longer than I thought it would. Besides knowing about API changes and that I'm either going to have to purchase the repository upgrade util or make my own, I don't know what else has changed as far as details.

Also, I see an email that says something about Magnolia 3.0.1 CE. Is this released already and there was no announcement on the user list? Or is this person using a CVS version? Or do I need to subscribe to the dev list to be notified about minor updates?

Its on SF. It hasn't been announced since I am currently away from work...

Cheers
Boris


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to