I'll answer some of the questions here, and leave it to Sunanda to make any changes.
>> http://wikis.sun.com/display/WebStack/MySQL+51ArcCase are > > Some quick comments: > > #0: This case is a minor update (from 5.0 to 5.1) of a component which 5.0 to 5.1 is *NOT* a minor update, please don't class it as such. > has been ARC'd before. As such, the expectation is that the ARC case > for the new one should tell the reader what exactly is different this > time around. On this, the current draft unfortunately isn't very > helpful. It covers everything about the integration as if it was a > brand new component. I can't tell (without finding the 5.0 case, > reading it and making a mental diff) what's different here. It is, in many respects, a brand new component. 5.1 is not replacing 5.0, it is going to co-exist with it, and they will be treated as two completely separate packages. As such, I think the current ARC is completely correct in its approach. > Presenting it as an all-new case makes ARC review very hard. ARC wants > to see what's new and what changed. The things which are identical to > what they were in 5.0 were already approved back when the 5.0 case was > approved, listing them all here again just clutters the doc and makes > it hard to find what is new/changed. See above. I dont see 5.0 and 5.1 as 'the same'. > #1: Explain why the dtrace interfaces are Volatile. Because they are not (a) finalized and (b) in the MySQL 5.1 source tree yet. They are stable and working (I wrote the majority of them, so I can be sure of that :) ), but they are not part of standard release. We are using a patch into the 5.1 code. > #2: Say more about the upgrade experience in the spec. Since /var has > different paths for 5.0 and 5.1, will running mysql_update out of the > box work? Or do I have to manually copy files around first? You will have to copy them over, because the database files in 5.0 and 5.1 are in different directories. You can't have them in the same directory and allow both version to co-exist. I thought we'd made the case for co-existence and the differences clear. > #3: Is 'mysql' (the CLI) linked from /usr/bin? That's the command > everyone wants to run out of the box. No, again, I thought this was clear (and we had a long discussion about it). We wont be creating symbolic links for 5.1 to the /usr/ mysql base. The *standard* /usr/bin/mysql currently in Solaris is actually linked to /usr/sfw/bin, and is from the 4.0 version that should be discontinued. For 5.0, we dont create /usr/bin/mysql for either 5.0 or 5.1. > #4: "Going by this we intend to provide support for 5.0 in Opensolaris > for a minimum period of 6 months > so that dependant components can migrate to MySQL 5.1 within that > timeframe." > That's not a call you can make by saying it in this spec. Since > you'll ship 2008.11 with MySQL 5.0, it's going to be supported for as > long as 2008.11 is supported. True, the point we are trying to make is that 5.0 wont be a standard component in an OpenSolaris release once we've given people time to migrate, and 5.1 is GA (RSN). > #5: Where can we find documentation for these dtrace probes? It will be in the standard MySQL manual - and yes, I'm writing those too :)) MC -- Martin 'MC' Brown, mc at mcslp.com and mc at mysql.com Technical Writer, Database Group, Sun Microsystems Everything MCslp: http://planet.mcslp.com
