They're still supported and recommended for use. Just because they haven't been updated recently doesn't mean they're in danger of falling out of support.
On Sat, Apr 12, 2014 at 11:04 AM, Karthik Narendran <alia... AT yahoo.in> wrote:What about oauth1? Is it still being used? And other api based packages(namely twitter, github, linkedin, facebook, google etc) are they still based on latest api version? Just asked because all those packages are last updated 2 months ago.--
On Thursday, April 10, 2014 6:52:59 PM UTC+5:30, Michael Babker wrote:As suggested in another thread, let's use this thread for discussing the various packages and the type of work that should go into them for 2.0.First, a bit of backstory so everyone is clear why we're moving to 2.0 rather quickly (remember 1.0's "official" release was 4 months ago). The Framework team decided that as each package is relicensed from GPL v2+ to LGPL v2.1+ that the new release for that package would be 2.0. This helps a bit in making it clear which version of the Framework packages fall under which license (1.x is GPL, 2.x is LGPL).This increment gives us the chance to look at refactoring code as appropriate for a major version increment. We also have the chance to discuss deprecating support for packages.Thus far, the Framework team has elected to deprecate our Log and Session packages, and those commits have been made to the repos to indicate such.What types of changes or deprecations would you like to see (and be willing to assist with) as we update our packages to 2.0, and why?Framework source code: https://github.com/joomla/
Visit http://developer.joomla.org for more information about developing with Joomla!
You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-framework+
unsubscribe AT googlegroups.com.
Visit this group at http://groups.google.com/