Option 1. The version number change will not make any task easier, and will just complicate developers' lives by having to configure 2 libraries instead of 1.
On Fri, May 1, 2009 at 8:54 AM, Jesse Myers <[email protected]> wrote: > > Option 3 > > On Fri, May 1, 2009 at 8:29 AM, Jim Meyer <[email protected]> wrote: >> +1 ... er, +.1 >> >> --j >> >> On May 1, 2009, at 7:55 AM, "Matt Sanford" <[email protected]> wrote: >> >>> >>> Option 3 … that's what versions are for, incrementing. >>> >>> On May 1, 2009, at 1:25 AM, Blaine Cook wrote: >>> >>>> >>>> We need to build some consensus around the version preference. As I >>>> see it, there are several options: >>>> >>>> 1. "1.0 Rev A" with no version string change (i.e., >>>> oauth_version=1.0) >>>> 2. "1.0a" (with oauth_version=1.0a) >>>> 3. "1.1" >>>> >>>> Please indicate your support for one of these options, and try to >>>> refrain from arguing your case here. The other thread remains open >>>> for >>>> that purpose. I would especially like to hear from library >>>> implementers here, and others who have not voiced their opinions in >>>> the other threads. >>>> >>>> b. >>>> >>>>> >>> >>> >>> > >> >> > >> > > > > -- --Breno +1 (650) 214-1007 desk +1 (408) 212-0135 (Grand Central) MTV-41-3 : 383-A PST (GMT-8) / PDT(GMT-7) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. 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/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
