How does this sound? CloudStack's database is created using the 4.0 schema and updated to the 4.1 schema when the management server starts for the first time. It is fine to see the same schema as 4.0 if the management server has not started yet.
--Alex > -----Original Message----- > From: Chip Childers [mailto:chip.child...@sungard.com] > Sent: Wednesday, March 20, 2013 6:28 PM > To: cloudstack-dev@incubator.apache.org > Subject: Re: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires cherry- > pick commits from master > > On Wed, Mar 20, 2013 at 02:23:33PM -0700, Alex Huang wrote: > > > My take on this is that we shouldn't do anything to 4.1 The people > > > that matter (users) are taken care of when they start the MS - and > > > that is a well- tested path. > > > The only visible benefit for 4.1 is for developers/QA - and while I > > > want everyone's life to be as easy as possible - last minute changes > > > to help folks in a branch that's already feature frozen and days > > > away from RC doesn't seem like the wisest path. > > > > > Then we should document for the benefit of the end users in case they > were comparing the schema to 4.0 schema. > > > > --Alex > > > > Suggested wording? Probably belongs in the release notes.
