-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Blake Johnson wrote: > On Apr 25, 11:45 am, Owen Winkler <[email protected]> wrote: >> Plugins should be tagged for specific versions of Habari, and when we >> reach Habari 1.0, we will standardize on a single version of jQuery (we >> won't change jQuery versions until 2.0) so that plugins don't have a >> moving target. >> > > Don't you think that this should depend on the amount of time between > releases? You are completely right that it will not be possible to > allow plugins to load their own version of jQuery within the admin > (they can do whatever they like on theme pages). I also feel that it > is not unreasonable to update the jQuery version which ships with > Habari on an annual basis. > > On a related note, we probably should change the way we ship jQuery > UI. Previously, we included individual files for each component > (ui.slider.js, ui.sortable.js, etc). When I upgraded the version of > jQuery UI in trunk, I changed this to a single compressed file. This > currently also has a version specific name: jquery- > ui-1.7.1.custom.min.js. Perhaps this should just be renamed jquery- > ui.js? > > --Blake
Our stated release policy is that major version numbers should maintain API compatibility. In my mind this means that we don't change things (even third-party things) that will break themes and plugins. Within a major number, we keep backwards compatibility. - -- Sean T. Evans -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkn2Mo0ACgkQmQpMBUWJpdtAnwCg9AYnXw23fhOT8YAflTE1Y61V 3p8AoLyTUAdQ5YRBsU6FMuwTb21MsLZU =jWl+ -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
