Talk:SeaMonkey/2.1/AddonCompat: Difference between revisions

Jump to navigation Jump to search
Line 9: Line 9:
* How will rapid releases of new SeaMonkey versions affect this list?  See http://news.slashdot.org/story/11/06/22/172229/No-Additional-Firefox-4-Security-Updates regarding the impact on extensions from making Firefox 5 the security update of Firefox 4.   
* How will rapid releases of new SeaMonkey versions affect this list?  See http://news.slashdot.org/story/11/06/22/172229/No-Additional-Firefox-4-Security-Updates regarding the impact on extensions from making Firefox 5 the security update of Firefox 4.   
* How will pending changes to Add-ons Manager affect this list?  (My understanding is that maxVersion values with wild-cards (e.g., 2.*) will no longer be accepted.)
* How will pending changes to Add-ons Manager affect this list?  (My understanding is that maxVersion values with wild-cards (e.g., 2.*) will no longer be accepted.)
: For Firefox, maybe (and yet…) but what about SeaMonkey? Here 2.3.* to 2.6.* seem "sensible", while 2.6a1 (more "conservative" for trunk support) <nowiki>!=</nowiki> 2.6.* OTOH, 2.* would we a little wild, and not really meaningful as long as we don't know when 3.x will happen, and which API changes might be expected before then. — [[User:Tonymec|Tonymec]] 17:06, 7 September 2011 (PDT)


== Smooth Wheel ==
== Smooth Wheel ==
Confirmed users
704

edits

Navigation menu