The current plan right now is to keep it around for at least 6 months to allow for porting.
Ultimately the older architecture is manual, error prone, and a detriment to the project from a forward thinking perspective. The old plugin style does not allow for installation without a human copy/pasting a bunch of junk and editing config files. It doesn't allow for easy discovery or removal either. Contrast with the new architecture: you decouple platform from APIs, automated discovery, installation, and removal. This is going to be far easier to maintain, upgrade and extend. It solves all the issues of 2.x and is recommended development workflow. I respect, and I know all our developers do, that ppl have legacy code to maintain. We're not going to 'force' you to upgrade and we will keep 2.9 around in long lived branch to make sure you aren't left behind. That said, we're going to strongly encourage developers to upgrade b/c we think its a far better development experience. On Wed, Jul 3, 2013 at 2:53 PM, David Pfahler <[email protected]> wrote: > What about support for 2.x? They'll still need plugins. > — > Sent from mobile > > On Wed, Jul 3, 2013 at 11:49 PM, Brian LeRoux <[email protected]> wrote: > >> For sure, tho I think the other package mgmt ecosystem have >> demonstrated that the good stuff naturally rises to the top and, I'd >> assume, diligent use of <platform> will help that happen. Either way >> you are right we need to encourage that to the broader community. >> On Wed, Jul 3, 2013 at 11:34 AM, Bryan Higgins <[email protected]> >> wrote: >>> One challenge with this will be merging plugins which have the same >>> functionality but target different platforms, especially when authored by >>> different individuals. >>> >>> Someone at BlackBerry recently created a LowLatencyAudio plugin based on >>> the iOS/android client spec. I already reached out to Andrew Trice to try >>> to work something out in this specific case, but for others a wiki or some >>> other means of fostering cross platform collaboration might be useful. I'd >>> hate to see the discovery service full of plugins which only support one >>> platform. >>> >>> >>> On Wed, Jul 3, 2013 at 2:09 PM, Brian LeRoux <[email protected]> wrote: >>> >>>> Post 3.0 we'll want to encourage the community to: >>>> >>>> 1. Remove their code from phonegap/phonegap-plugins and into their own >>>> repos (we've already started this) >>>> 2. Follow the Plugman spec (we just started doing this) >>>> 3. Publishing using the Plugman discovery (we have not shipped this yet) >>>> >>>> We should help them do this too. Just want to get this message out there. >>>>
