<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
On 6/16/2011 2:02 AM, Mark Banner wrote:
<blockquote cite="mid:4DF9C696.7040000@mozilla.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Even with automatic updates, I believe we won't be automatically
updating a user if their extensions are incompatible. If you've
seen something to the contrary, please let me know.<br>
</blockquote>
I have not heard either way. But it sounds risky to me to hold off
on updates (which are also security updates) because of an
incompatible addon. But it also sounds annoying to update and break
an extension that might be important to the user. This process is
going to be challenging.<br>
<blockquote cite="mid:4DF9C696.7040000@mozilla.com" type="cite"> So
here is the rough plan of what will be happening:<br>
<ul>
<li>...</li>
<li>Once aurora has been stabilised wrt features, add x.*
version to AMO (this may actually happen earlier). At the same
time, re-run the compatibility bump tool, and bump add-on max
versions to x.*.</li>
</ul>
Hence this will get us compatibility for beta users before the
merge to the beta channel and the first beta build.<br>
</blockquote>
That is the main point I would like to see. The timing will be quite
tight however. It would be good to have a target date relative to
the cutover date when this will be done.<br>
<br>
rkent<br>
</body>
</html>