I'm live-testing trunk SeaMonkey (as my UA string will tell you if you
care to look ;-) ), I have lots of extensions (more than 40 I think, not
counting the disabled ones), and, as someone said before me, the ACR is
my friend. But I don't trust it blindly:
Not getting auto-updates for extensions whose maxVersion are below what
I'm currently using may seem a little awkward, but IMHO it's normal
(I'll explain why near the bottom of this post). I work around it by
having the following two URLs bookmarked:
https://addons.mozilla.org/en-US/seamonkey/extensions/?sort=updated&unreviewed=on
https://addons.mozilla.org/en-US/seamonkey/themes/?sort=updated&unreviewed=on
and visiting them once a day as I get ready to (manually) upgrade to the
next nightly. If there is an update for an addon I already have, or one
whose functionality seems interesting, I go to the individual addon
page, scroll all the way down and unfold the "Versions" foldout (why the
h??? couldn't they leave it displayed as in the previous version of the
AMO stylesheet?): if it supports a not-too-old version of SeaMonkey
(e.g. aurora), or any version of SeaMonkey together with the latest
trunk build of Firefox or Thunderbird, I take my chances and install it
(and check at the next startup how it actually works, and disable or
downgrade it if I don't like what I see). But I wouldn't want anything
to update itself behind my back to a new version which, according to its
maintainers, does not even support the build I'm on.
Best regards,
Tony.
--
There is no distinctly native American criminal class except Congress.
-- Mark Twain
AMO already auto-updates the maxVersions of extensions which pass some
tests, meant to avoid regressions; those which fail the same tests (and
in particular those which, like the Lightning calendar extension for
Thunderbird and SeaMonkey, include binary XPCOM, or those which use an
API which will soon be removed) don't get the maxVersion bump. IMHO the
ACR shouldn't auto-update extensions which, despite this AMO maxVersion
bumping, don't support the current app version even after the update:
such updates can and may be installed manually, but IMHO it is the
user's full responsibility to decide whether (s)he wants to take the
chance to update to that still-not-officially-supported version of this
or that addon. To that end, (s)he can visit the AMO pages sorted by last
update date, and then decide which updates (s)he wants to install.
Similarly, for addons not hosted at AMO, (s)he can visit each addon's
home site, but of course those off-AMO addons won't be found all in one
place.
Best regards,
Tony.
--
"I'd love to go out with you, but I've been scheduled for a karma
transplant."