This project is read-only.

Version to version migration

Dec 8, 2008 at 5:40 PM
Assuming I kick off an Oxite implementation today (in Alpha) and there are subsequent releases what is the version to version migration path likely to be?

I am not a developer so want to minimise the number of times I have to dip into .aspx pages to make changes, and I don't have control of the server (so updates will be via FTP)
Dec 8, 2008 at 5:50 PM
Not being a developer will make working on Oxite hard.  We really targeted developers for it and make some assumptions that developers would be the ones using it.  That said, if the community wants to take this down the path of making it work well for non-developers we're not going to stop it.  :)
Dec 8, 2008 at 7:30 PM
For fear of playing "Captain Obvious", it would be great if you guys posted a planned roadmap.  This would help those of us that are planning on modding Oxite to prepare for changes.  Obviously, I'm not asking for data committments, but just something that gives an idea of the changes you guys foresee in the next few releases.
Dec 8, 2008 at 7:37 PM
Captain Obvious is always welcome here.  :)

We will publish a roadmap soon.  That said, the list will not be very large.  We know of a few things we're definitely going to work on and will publish that, but we really want to see what the community involvement is going to be like and where you all want this to go.  We're going to help guide where it goes, but want help from the community too so we don't want to be too strict on the roadmap.
Dec 10, 2008 at 6:58 AM
Suck it up Jeremy (offbeatmammal), and if you get stuck, just go poke Erik on the shoulder with a "please help"

Dec 10, 2008 at 7:08 AM
:) I like one-click automation... isn't that what WebAI promises us
(and why is it all XHTML compliant... I want a 100% Silverlight front-end!)