Merge plugin dev branchs into master

[Steven Gill <st...@gmail.com>]

I want to try and flush out the process for merging the dev branches for
the core plugins into master and get it onto the wiki.

Currently the dev branches have some readme changes, namespace changes and
package changes for android.

I don't believe any of these changes should be breaking changes.

Process
1. Create issue on jira for running mobile spec tests on all platforms
using dev branch of plugins
2. Test on all platforms
3. Merge in change into master
4. Publish to plugins.cordova.io?

Do we really need to test the plugins on all the platforms for changes that
won't affect them at all?

Re: Merge plugin dev branchs into master

[Andrew Grieve <ag...@chromium.org>]

Just to loop back on this - I've updated the
https://wiki.apache.org/cordova/CommitterWorkflow to include a section at
the bottom on which branch to commit against.


On Thu, Aug 29, 2013 at 4:00 PM, Becky Gibson <gi...@gmail.com>wrote:

> Yes, updating the wiki would be helpful.  I'd like to submit a fix but
> since I don't follow this list all this time, I'm not sure if I should be
> working off of dev or master.  Based on the above thread I think dev?
>
> thanks,
> -becky
>
>
> On Thu, Aug 29, 2013 at 11:48 AM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > Steve, did you do this? I didn't notice a JIRA issue or blog post.
> >
> >
> > On Fri, Aug 16, 2013 at 10:59 AM, Andrew Grieve <agrieve@chromium.org
> > >wrote:
> >
> > > Thought of another step!
> > >
> > > Generate a changelog, and turn it into a blog post so that people will
> > > know about the update :)
> > >
> > >
> > > On Thu, Aug 15, 2013 at 4:59 PM, Steven Gill <stevengill97@gmail.com
> > >wrote:
> > >
> > >> Thanks for the feedback Andrew!
> > >>
> > >> Sounds good to me. I am going to go through these steps today.
> > >>
> > >>
> > >> On Thu, Aug 15, 2013 at 12:07 PM, Andrew Grieve <agrieve@chromium.org
> > >> >wrote:
> > >>
> > >> > Great! I agree it's time someone take a stab at this!
> > >> >
> > >> >
> > >> > On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill <
> stevengill97@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > I want to try and flush out the process for merging the dev
> branches
> > >> for
> > >> > > the core plugins into master and get it onto the wiki.
> > >> > >
> > >> > > Currently the dev branches have some readme changes, namespace
> > changes
> > >> > and
> > >> > > package changes for android.
> > >> > >
> > >> > > I don't believe any of these changes should be breaking changes.
> > >> > >
> > >> > > Process
> > >> > > 1. Create issue on jira for running mobile spec tests on all
> > platforms
> > >> > > using dev branch of plugins
> > >> > > 2. Test on all platforms
> > >> > > 3. Merge in change into master
> > >> > > 4. Publish to plugins.cordova.io?
> > >> > >
> > >> > > Do we really need to test the plugins on all the platforms for
> > changes
> > >> > that
> > >> > > won't affect them at all?
> > >> > >
> > >> > I think no. And we should only test plugins that have changes to
> them
> > >> (in
> > >> > this case all of them).
> > >> >
> > >> > Should add in bumping of the version number.
> > >> >
> > >> > I think one thing to add to the process is to create mobilespec with
> > the
> > >> > existing versions of plugins, then `cordova plugin rm` them all,
> then
> > >> > `cordova plugin add` the new ones using a URL that points to the dev
> > >> > branch. aka, test out the upgrade process.
> > >> >
> > >>
> > >
> > >
> >
>

Re: Merge plugin dev branchs into master

[Becky Gibson <gi...@gmail.com>]

Yes, updating the wiki would be helpful.  I'd like to submit a fix but
since I don't follow this list all this time, I'm not sure if I should be
working off of dev or master.  Based on the above thread I think dev?

thanks,
-becky


On Thu, Aug 29, 2013 at 11:48 AM, Andrew Grieve <ag...@chromium.org>wrote:

> Steve, did you do this? I didn't notice a JIRA issue or blog post.
>
>
> On Fri, Aug 16, 2013 at 10:59 AM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > Thought of another step!
> >
> > Generate a changelog, and turn it into a blog post so that people will
> > know about the update :)
> >
> >
> > On Thu, Aug 15, 2013 at 4:59 PM, Steven Gill <stevengill97@gmail.com
> >wrote:
> >
> >> Thanks for the feedback Andrew!
> >>
> >> Sounds good to me. I am going to go through these steps today.
> >>
> >>
> >> On Thu, Aug 15, 2013 at 12:07 PM, Andrew Grieve <agrieve@chromium.org
> >> >wrote:
> >>
> >> > Great! I agree it's time someone take a stab at this!
> >> >
> >> >
> >> > On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill <st...@gmail.com>
> >> > wrote:
> >> >
> >> > > I want to try and flush out the process for merging the dev branches
> >> for
> >> > > the core plugins into master and get it onto the wiki.
> >> > >
> >> > > Currently the dev branches have some readme changes, namespace
> changes
> >> > and
> >> > > package changes for android.
> >> > >
> >> > > I don't believe any of these changes should be breaking changes.
> >> > >
> >> > > Process
> >> > > 1. Create issue on jira for running mobile spec tests on all
> platforms
> >> > > using dev branch of plugins
> >> > > 2. Test on all platforms
> >> > > 3. Merge in change into master
> >> > > 4. Publish to plugins.cordova.io?
> >> > >
> >> > > Do we really need to test the plugins on all the platforms for
> changes
> >> > that
> >> > > won't affect them at all?
> >> > >
> >> > I think no. And we should only test plugins that have changes to them
> >> (in
> >> > this case all of them).
> >> >
> >> > Should add in bumping of the version number.
> >> >
> >> > I think one thing to add to the process is to create mobilespec with
> the
> >> > existing versions of plugins, then `cordova plugin rm` them all, then
> >> > `cordova plugin add` the new ones using a URL that points to the dev
> >> > branch. aka, test out the upgrade process.
> >> >
> >>
> >
> >
>

Re: Merge plugin dev branchs into master

[Andrew Grieve <ag...@chromium.org>]

Steve, did you do this? I didn't notice a JIRA issue or blog post.


On Fri, Aug 16, 2013 at 10:59 AM, Andrew Grieve <ag...@chromium.org>wrote:

> Thought of another step!
>
> Generate a changelog, and turn it into a blog post so that people will
> know about the update :)
>
>
> On Thu, Aug 15, 2013 at 4:59 PM, Steven Gill <st...@gmail.com>wrote:
>
>> Thanks for the feedback Andrew!
>>
>> Sounds good to me. I am going to go through these steps today.
>>
>>
>> On Thu, Aug 15, 2013 at 12:07 PM, Andrew Grieve <agrieve@chromium.org
>> >wrote:
>>
>> > Great! I agree it's time someone take a stab at this!
>> >
>> >
>> > On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill <st...@gmail.com>
>> > wrote:
>> >
>> > > I want to try and flush out the process for merging the dev branches
>> for
>> > > the core plugins into master and get it onto the wiki.
>> > >
>> > > Currently the dev branches have some readme changes, namespace changes
>> > and
>> > > package changes for android.
>> > >
>> > > I don't believe any of these changes should be breaking changes.
>> > >
>> > > Process
>> > > 1. Create issue on jira for running mobile spec tests on all platforms
>> > > using dev branch of plugins
>> > > 2. Test on all platforms
>> > > 3. Merge in change into master
>> > > 4. Publish to plugins.cordova.io?
>> > >
>> > > Do we really need to test the plugins on all the platforms for changes
>> > that
>> > > won't affect them at all?
>> > >
>> > I think no. And we should only test plugins that have changes to them
>> (in
>> > this case all of them).
>> >
>> > Should add in bumping of the version number.
>> >
>> > I think one thing to add to the process is to create mobilespec with the
>> > existing versions of plugins, then `cordova plugin rm` them all, then
>> > `cordova plugin add` the new ones using a URL that points to the dev
>> > branch. aka, test out the upgrade process.
>> >
>>
>
>

Re: Merge plugin dev branchs into master

[Andrew Grieve <ag...@chromium.org>]

Thought of another step!

Generate a changelog, and turn it into a blog post so that people will know
about the update :)


On Thu, Aug 15, 2013 at 4:59 PM, Steven Gill <st...@gmail.com> wrote:

> Thanks for the feedback Andrew!
>
> Sounds good to me. I am going to go through these steps today.
>
>
> On Thu, Aug 15, 2013 at 12:07 PM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > Great! I agree it's time someone take a stab at this!
> >
> >
> > On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill <st...@gmail.com>
> > wrote:
> >
> > > I want to try and flush out the process for merging the dev branches
> for
> > > the core plugins into master and get it onto the wiki.
> > >
> > > Currently the dev branches have some readme changes, namespace changes
> > and
> > > package changes for android.
> > >
> > > I don't believe any of these changes should be breaking changes.
> > >
> > > Process
> > > 1. Create issue on jira for running mobile spec tests on all platforms
> > > using dev branch of plugins
> > > 2. Test on all platforms
> > > 3. Merge in change into master
> > > 4. Publish to plugins.cordova.io?
> > >
> > > Do we really need to test the plugins on all the platforms for changes
> > that
> > > won't affect them at all?
> > >
> > I think no. And we should only test plugins that have changes to them (in
> > this case all of them).
> >
> > Should add in bumping of the version number.
> >
> > I think one thing to add to the process is to create mobilespec with the
> > existing versions of plugins, then `cordova plugin rm` them all, then
> > `cordova plugin add` the new ones using a URL that points to the dev
> > branch. aka, test out the upgrade process.
> >
>

Re: Merge plugin dev branchs into master

[Steven Gill <st...@gmail.com>]

Thanks for the feedback Andrew!

Sounds good to me. I am going to go through these steps today.


On Thu, Aug 15, 2013 at 12:07 PM, Andrew Grieve <ag...@chromium.org>wrote:

> Great! I agree it's time someone take a stab at this!
>
>
> On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill <st...@gmail.com>
> wrote:
>
> > I want to try and flush out the process for merging the dev branches for
> > the core plugins into master and get it onto the wiki.
> >
> > Currently the dev branches have some readme changes, namespace changes
> and
> > package changes for android.
> >
> > I don't believe any of these changes should be breaking changes.
> >
> > Process
> > 1. Create issue on jira for running mobile spec tests on all platforms
> > using dev branch of plugins
> > 2. Test on all platforms
> > 3. Merge in change into master
> > 4. Publish to plugins.cordova.io?
> >
> > Do we really need to test the plugins on all the platforms for changes
> that
> > won't affect them at all?
> >
> I think no. And we should only test plugins that have changes to them (in
> this case all of them).
>
> Should add in bumping of the version number.
>
> I think one thing to add to the process is to create mobilespec with the
> existing versions of plugins, then `cordova plugin rm` them all, then
> `cordova plugin add` the new ones using a URL that points to the dev
> branch. aka, test out the upgrade process.
>

Re: Merge plugin dev branchs into master

[Andrew Grieve <ag...@chromium.org>]

Great! I agree it's time someone take a stab at this!


On Thu, Aug 15, 2013 at 3:00 PM, Steven Gill <st...@gmail.com> wrote:

> I want to try and flush out the process for merging the dev branches for
> the core plugins into master and get it onto the wiki.
>
> Currently the dev branches have some readme changes, namespace changes and
> package changes for android.
>
> I don't believe any of these changes should be breaking changes.
>
> Process
> 1. Create issue on jira for running mobile spec tests on all platforms
> using dev branch of plugins
> 2. Test on all platforms
> 3. Merge in change into master
> 4. Publish to plugins.cordova.io?
>
> Do we really need to test the plugins on all the platforms for changes that
> won't affect them at all?
>
I think no. And we should only test plugins that have changes to them (in
this case all of them).

Should add in bumping of the version number.

I think one thing to add to the process is to create mobilespec with the
existing versions of plugins, then `cordova plugin rm` them all, then
`cordova plugin add` the new ones using a URL that points to the dev
branch. aka, test out the upgrade process.