The issue that if use a tag to signify the new version, then the tag is applied to all plugins in the repo. This is probably not a big deal for minor bumps, but when a plugin needs a major bump, they all will. So you will/could have a plugin with a major version bump even though the code has not changed.
@purplecabbage risingj.com On Fri, Nov 22, 2013 at 6:36 PM, Michal Mocny <mmo...@chromium.org> wrote: > I don't understand, whats the problem? I thought you publish plugins by > git-repo & subdir & hash -- so multiple plugins makes no difference. > > The master & dev branch deal was to do with cordova-3.0 users that did not > support plugin repo install from !master branch, right? But none of these > plugins in cordova-plugins existed back then, so we just set engine > requirement to 3.1? > > -Michal > > > On Fri, Nov 22, 2013 at 1:32 PM, Steven Gill <stevengil...@gmail.com> > wrote: > > > +1 on one plugin per repo. Would making releasing and tagging much > simpler. > > > > > > On Fri, Nov 22, 2013 at 1:29 PM, Carlos Santana <csantan...@gmail.com > > >wrote: > > > > > Yep that's the problem with having independent plugins in a single > repo, > > > and just using directories to separate them. > > > > > > If I would have a choice I would strongly encourage one plugin per repo > > > containing its own version and source control. > > > > > > > > > On Friday, November 22, 2013, Shazron wrote: > > > > > > > The cordova-plugins repo has plugins as well, but are outside of the > > > > purview of the planned weekly core plugins release - I plan to upload > > > > independently. > > > > > > > > The repo does not have the concept of "dev" and "master" plugins as > > well > > > > like the core plugins. It was suggested we have tags, but this is > > > > problematic because we have multiple plugins in that one repo. > > > > > > > > > > > > > -- > > > Carlos Santana > > > <csantan...@gmail.com> > > > > > >
