[CB-6521] Merge plugin development branches into master - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Task
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: None
Component/s: cordova-plugin-battery-status, cordova-plugin-camera, cordova-plugin-console (DEPRECATED), cordova-plugin-contacts (DEPRECATED), cordova-plugin-device, cordova-plugin-device-motion (DEPRECATED), cordova-plugin-device-orientation (DEPRECATED), cordova-plugin-file, cordova-plugin-file-transfer (DEPRECATED), cordova-plugin-geolocation, cordova-plugin-globalization (DEPRECATED), cordova-plugin-inappbrowser, cordova-plugin-media, cordova-plugin-media-capture, cordova-plugin-network-information, cordova-plugin-splashscreen, cordova-plugin-statusbar, cordova-plugin-vibration
Labels:
None

Description

Following the mailing list discussion, all plugins development is going to take place on the master branch. Any current work on the "dev" branches should be merged in to master.

After things settle down, the "dev" branch names should be deleted to prevent any accidental branching.

Update: The dev branch is not being deleted; instead, all of the files within it are being removed, and the README is being updated to indicate that development should proceed on the master branch.

Attachments

Issue Links

relates to

CB-6530 Plugins docs for v3.4 not working

Closed

Activity

People

Assignee:: Ian Clelland

Reporter:: Ian Clelland

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 25/Apr/14 15:31

Updated:: 23/Aug/18 07:19

Resolved:: 25/Apr/14 18:32