rstrong's blog
in search of ponies
Status Update – App specific actions after App Update
February 12th, 2010 by rstrong
Application update is going to support an application provided string in the update xml which can then be used by the application to determine what to do after a successful application update.
Progress:
- Client side patches reviewed but still need to finish tests for Bug 530872 [Toolkit] – app.update.url params / update.xml cleanup and addition of a custom string property for apps [All]. The xpcshell tests are finished but the mochitest chrome tests have shown there are leaks in the client code (it also asserts in debug builds) due to the work done to support remote html which was done for Firefox 3.0. As soon as I fix the leaks and assertions the tests should be done. This is taking much longer than I like but tests are important and it is very important to not add new oranges to the tinderbox.
- ddahl has started work again on Bug 538331 [Firefox] – On update perform action based upon the update metadata [All] as well as general cleanup of overridden attributes in the update xml.
- Reviewed code / provided guidance for Bug 523410 [Core] – Disable LSPs in WinSock for Firefox [Windows.]
Future targets:
- Finish up the tests for and land Bug 530872 [Toolkit] – app.update.url params / update.xml cleanup and addition of a custom string property for apps [All]
- Write mochitests for Bug 538533 [Toolkit] – If a complete update fails the update prompt should state the error and offer a link to download the update [All].
- Finish up Bug 538331 [Firefox] – On update perform action based upon the update metadata [All].