cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Gill <stevengil...@gmail.com>
Subject Re: Plugins release prep: Cherry-picking plugin updates
Date Wed, 06 May 2015 18:57:00 GMT
I haven't heard back. Should I move forward with those 5 plugins?

file-transfer, device-motion, dialogs, vibration, and camera.

I will update the process to support specific plugins release (instead of
all plugins) as I work through it.


On Tue, May 5, 2015 at 12:29 PM, Jesse <purplecabbage@gmail.com> wrote:

> + file-transfer so we can resolve CB-8951
>
>
> @purplecabbage
> risingj.com
>
> On Tue, May 5, 2015 at 12:19 PM, Steven Gill <stevengill97@gmail.com>
> wrote:
>
> > Hey guys,
> >
> > I can help you out. The process is designed for all plugins but it is
> > pretty easy to do it for just a few. I've done it many times.
> >
> > If changes are on master, they shouldn't be incomplete. Any known problem
> > with release the master branch of those plugins?
> >
> > We could cherry-pick, but it is just more work than probably required.
> > Since we don't have release branches for plugins, just tags.
> >
> > If you guys merge changes into master, I can take over the release or at
> > least tell you the parts to modify in the release process to make it
> work.
> >
> > -Steve
> >
> > On Tue, May 5, 2015 at 11:44 AM, Rob Paveza <Rob.Paveza@microsoft.com>
> > wrote:
> >
> > > Hi all -
> > >
> > > I started a [discuss] thread about plugin updates last week,
> effectively
> > > saying that we wanted to take four JIRA items which are causing
> problems
> > > for Windows 10: CB-8926, CB-8928, CB-8930, and CB-8943.  Since Murat
> is a
> > > committer, he's actually trying to do the release.  We're looking at
> > > device-motion, dialogs, vibration, and camera.
> > >
> > > However, as we go through the [release process](
> > >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md
> > ),
> > > there are a lot of things that give us pause, specifically that we're
> > going
> > > to end up tagging each plugin rather than just the four.  We're also
> > > concerned that we'll bring in unstable or not-yet-completed changes
> from
> > > 'master' in some of the plugins.  Instead, we're trying to cherry-pick.
> > >
> > > So, we know that where the final state is supposed to be:
> > > - Each plugin that we're updating gets a new tag with a build-version
> > bump
> > > - The branch that we submitted as the PR should become the new tag
> (since
> > > it was based on the previous release tag)
> > > - Then we'll go on with the rest of the publish-to-NPM work, etc.
> > >
> > > Since all of the steps are automated, is there a straightforward way to
> > > cherry-pick the individual pieces that is known and has been used
> before?
> > > Or are we in new territory?
> > >
> > > Thanks!
> > > -Rob and Murat
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message