I'd like us to keep drawing our attention to that world 'everything is a plugin'. That said, having tagged versions that target specific api releases would be the way to go.
On Mon, Feb 20, 2012 at 10:10 AM, Dave Johnson <dave.c.john...@gmail.com> wrote: > In the land of "everything is a plugin" I guess those old versions just > become another plugin that's available for use? > > On Monday, February 20, 2012, Patrick Mueller wrote: > >> On Mon, Feb 20, 2012 at 11:57, Dave Johnson >> <dave.c.john...@gmail.com<javascript:;> >> >wrote: >> >> > Yah I think that makes sense. We can even remove the old one when we hit >> a >> > major release. >> > >> >> It's not clear what the lifetime of such "versioned spec'd APIs from >> somewhere" should be. >> >> While it seems that we would certainly "drop support" for "old" versions of >> spec impls, not sure that we'd want to remove them entirely. Maybe "old >> versions" require a bit more work to "add" to your project - you have to >> point to a repo with a version-specifc URL or something, rather than just >> run a simpel command which does an "add the File API plugin". >> >> -- >> Patrick Mueller >> http://muellerware.org >>
