my stance on versioning is for when something has changed that breaks backwards compatibility. in this case, we haven't broken backwards compatibility, but a regression was introduced. regressions can get introduced in a variety of different ways, and across a variety of different properties unfortunately. software projects do their best to avoid them -- but its orthogonal to versioning....
either way - we're working on a fix. On Wed, May 5, 2010 at 2:11 PM, Orian Marx (@orian) <or...@orianmarx.com>wrote: > Well, I'm not sure if Rich was referring to the output per se or > rather that this bug was probably tied to the skip_user parameter that > was just added to timelines... which one could argue is a candidate > for versioning. > > On May 5, 5:02 pm, Raffi Krikorian <ra...@twitter.com> wrote: > > versioning has absolutely nothing to do with this - this is clearly a > bug. > > > > On Wed, May 5, 2010 at 1:39 PM, Rich <rhyl...@gmail.com> wrote: > > > Oh I'll add, I thought the point of a versioned API was that this sort > > > of thing didn't happen? > > > > > On May 5, 9:37 pm, Rich <rhyl...@gmail.com> wrote: > > > > I noticed today inside the user tags an extra user tag has appeared > > > > > > We now have user->status->user > > > > > > This is causing a crash on my app and number of engines I've tried. > > > > When did this get added and did I miss the notification? > > > > > > Many thanks > > > > Richard > > > > -- > > Raffi Krikorian > > Twitter Platform Teamhttp://twitter.com/raffi > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
