Sounds like a good plan Andy. And yes, I think we need to at least be mindful of major point churn. Though I do agree with Bob that we shouldn't be precious.
How about landing that console.info change and then creating a new JIRA for the removal and marking it as "for 2.0"? On 27 November 2013 21:29, Andy Wenk <[email protected]> wrote: > +1 for > console.info, > waiting till 2.0 > and communicating it prominently > > Cheers > > Andy > > > On 27 November 2013 14:29, Alexander Shorin <[email protected]> wrote: > >> On Wed, Nov 27, 2013 at 5:02 PM, Octavian Damiean <[email protected]> >> wrote: >> > I'm also -1 on removing it. If we really plan to remove it we should do >> it >> > gracefully. Add a big note somewhere, maybe even in the header of the >> > source file notifying users that it will be deprecated. >> > >> > Maybe even add a console.info or console.warn stating that it is a >> > deprecated library. >> > >> > That way people have time to react to it. If we'd just remove it now >> > because we know it is not used internally we might risk a bad image by >> > breaking peoples applications. >> >> Hello! >> >> Seem like you miss all the beginning: >> https://issues.apache.org/jira/browse/COUCHDB-1934 >> >> but it's good idea to add console warning. +1 >> >> -- >> ,,,^..^,,, >> > > > > -- > Andy Wenk > Hamburg - Germany > RockIt! > > http://www.couchdb-buch.de > http://www.pg-praxisbuch.de > > GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 -- Noah Slater https://twitter.com/nslater
