3.5.0rc1

[Jesse <pu...@gmail.com>]

There are numerous changes I would like to see pushed out. Can we start
talking about a 3.5.0 platform release?


@purplecabbage
risingj.com

Re: 3.5.0rc1

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

On Wed, Apr 30, 2014 at 11:08 AM, Marcel Kinard <cm...@gmail.com> wrote:

>
> On Apr 29, 2014, at 11:14 PM, Andrew Grieve <ag...@chromium.org> wrote:
>
> >> I say we aim to make 3.5.0 our last cadence release. I'm hoping to
> switch
> >> to independent platform releases.
> >>
> >> As for docs, I don't think everyone is convinced yet that loosing the
> >> version numbers is the way to go. I say we add version 3.5.0 to docs and
> >> then make the switch to edge for the next cli release. That way it fits
> >> well with this being our last cadence release.
> >>
> > Haven't seen any opposition to this on the list or in your doc. Might as
> > well go to edge now, no?
>
> I like Steve's idea to make the switch to edge at the first post-cadence
> release.
>
> For losing the version numbers in the docs, I can see how something like a
> "@since" tag could help, but that is really just for new APIs. If there is
> a behavioral change or return value change, how does that get documented?
> Are we talking something like:
>
> globalization.getLocale() returns:
>     symbolic name, i.e. "English" (before r1.0.0)
>     BCP-147 identifier, ie "En_US" (since r1.0.0)
>
> For this reason, I'm not yet sold on the non-creation of versions in the
> docs.
>
> Thinking out loud: For plugins, the docs are now in each plugin repo. We
> could continue to create versions there, or link to github with a
> tag/branch name to render as HTML. I think the latter would be sufficient
> and easy. But to do this right, the same thing ought to happen with
> platforms and tools. Then it becomes consistent across all our repos, and
> the same approach can be used for versioning the docs. The only thing in
> cordova-docs would be overviews. Is this idea loathed?
>

Having plugin docs versioned with the plugin is definitely the idea. Only
guides & specs will remain in docs.cordova.io.
For changes in CLI / guides, then we should call out when features were
added right inline in the docs.

For the events APIs, I think the button events should be moved into a
plugin. That would leave only deviceready, pause, resume.


>
> On a slightly different topic: So what identifier are we using to specify
> a point in the timeline of all these independent releases (platforms,
> plugins, tools)? The goal is to have a recreatable state of Cordova. Is it
> the CLI version because that gets bumped for every component release?


We don't actually have this right now since plugins are uncoupled. If you
wanted right now to take the release version of everything and tag it, I
think you'd be fine to just use a timestamp as the label.

Re: 3.5.0rc1

[Marcel Kinard <cm...@gmail.com>]

On Apr 29, 2014, at 11:14 PM, Andrew Grieve <ag...@chromium.org> wrote:

>> I say we aim to make 3.5.0 our last cadence release. I'm hoping to switch
>> to independent platform releases.
>> 
>> As for docs, I don't think everyone is convinced yet that loosing the
>> version numbers is the way to go. I say we add version 3.5.0 to docs and
>> then make the switch to edge for the next cli release. That way it fits
>> well with this being our last cadence release.
>> 
> Haven't seen any opposition to this on the list or in your doc. Might as
> well go to edge now, no?

I like Steve's idea to make the switch to edge at the first post-cadence release.

For losing the version numbers in the docs, I can see how something like a "@since" tag could help, but that is really just for new APIs. If there is a behavioral change or return value change, how does that get documented? Are we talking something like:

globalization.getLocale() returns:
    symbolic name, i.e. "English" (before r1.0.0)
    BCP-147 identifier, ie "En_US" (since r1.0.0)

For this reason, I'm not yet sold on the non-creation of versions in the docs.

Thinking out loud: For plugins, the docs are now in each plugin repo. We could continue to create versions there, or link to github with a tag/branch name to render as HTML. I think the latter would be sufficient and easy. But to do this right, the same thing ought to happen with platforms and tools. Then it becomes consistent across all our repos, and the same approach can be used for versioning the docs. The only thing in cordova-docs would be overviews. Is this idea loathed?

On a slightly different topic: So what identifier are we using to specify a point in the timeline of all these independent releases (platforms, plugins, tools)? The goal is to have a recreatable state of Cordova. Is it the CLI version because that gets bumped for every component release?

Re: 3.5.0rc1

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

On Tue, Apr 29, 2014 at 3:17 PM, Steven Gill <st...@gmail.com> wrote:

> I can take a crack at updating our cadence release process to better
> represent dist/.
>
Awesome!

>
> I think for the 3.5.0 release, we add package.json files to all platforms
> and publish to npm as well as dist. I have created an issue to track this
> [1]. This way we can begin work on the CLI post 3.5.0 to use the npm
> releases instead of fetching from our git servers.
>
Good idea.

>
> I am going to start the release train for 3.5.0 as soon as I add these.
>
> I say we aim to make 3.5.0 our last cadence release. I'm hoping to switch
> to independent platform releases.
>
> As for docs, I don't think everyone is convinced yet that loosing the
> version numbers is the way to go. I say we add version 3.5.0 to docs and
> then make the switch to edge for the next cli release. That way it fits
> well with this being our last cadence release.
>
Haven't seen any opposition to this on the list or in your doc. Might as
well go to edge now, no?


>
> We should also take this opportunity to let our community know that 3.5.0
> will be the final cadence release. They should focus on CLI updates from
> now on.
>
No need to announce this until it's ready. Never know what hiccups there
might be.


>
> [1] https://issues.apache.org/jira/browse/CB-6551
>
>
> On Fri, Apr 25, 2014 at 12:57 PM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > Would love to get to a platforms-independently-released world, but am
> happy
> > to do another cadence release.
> >
> > In terms of getting our act together, we need to update our cadence
> release
> > process to not have the release to dist/ as an afterthought:
> >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md
> >
> > Any volunteers for taking a crack at it? Can be edited via pull request
> > right on github via clicking the "edit" button:
> >
> >
> https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md
> >
> > E.g. Need to release to dist/dev *before* npm
> > E.g. Don't add -rc1 to versions anymore since those don't create archives
> > we can vote on
> > E.g. Probably don't need pre-emptive release branches anymore (although I
> > think this can be up to each platform to decide on)
> >
> >
> > Another question, can we do this without creating a v3.5.0 of the docs,
> as
> > in Steve's proposal?
> > https://docs
> > .google.com/document/d/1qwpypH7sH0wH9Sbesmg8JZow-l8IqdZtF1BtLUZb1As/edit
> >
> > I think this would be a great time to switch to always edge/.
> >
> >
> >
> >
> >
> > On Fri, Apr 25, 2014 at 3:42 PM, Ian Clelland <iclelland@chromium.org
> > >wrote:
> >
> > > It's probably time.
> > >
> > > Joe and I were discussing the possibility of including an (alpha) API
> for
> > > pluggable webviews in a 3.5.0 release of cordova-android. I'd like to
> see
> > > that in place, but it would probably not be ready until mid-next-week
> at
> > > the earliest.
> > >
> > > iOS has had only a couple of commits since 3.4.1, so there's no rush
> > there.
> > > I have no doubt that the other platforms are overdue for a release,
> > though.
> > >
> > >
> > > On Fri, Apr 25, 2014 at 3:34 PM, Jesse <pu...@gmail.com>
> wrote:
> > >
> > > > There are numerous changes I would like to see pushed out. Can we
> start
> > > > talking about a 3.5.0 platform release?
> > > >
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > >
> >
>

Re: 3.5.0rc1

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

I can take a crack at updating our cadence release process to better
represent dist/.

I think for the 3.5.0 release, we add package.json files to all platforms
and publish to npm as well as dist. I have created an issue to track this
[1]. This way we can begin work on the CLI post 3.5.0 to use the npm
releases instead of fetching from our git servers.

I am going to start the release train for 3.5.0 as soon as I add these.

I say we aim to make 3.5.0 our last cadence release. I'm hoping to switch
to independent platform releases.

As for docs, I don't think everyone is convinced yet that loosing the
version numbers is the way to go. I say we add version 3.5.0 to docs and
then make the switch to edge for the next cli release. That way it fits
well with this being our last cadence release.

We should also take this opportunity to let our community know that 3.5.0
will be the final cadence release. They should focus on CLI updates from
now on.

[1] https://issues.apache.org/jira/browse/CB-6551


On Fri, Apr 25, 2014 at 12:57 PM, Andrew Grieve <ag...@chromium.org>wrote:

> Would love to get to a platforms-independently-released world, but am happy
> to do another cadence release.
>
> In terms of getting our act together, we need to update our cadence release
> process to not have the release to dist/ as an afterthought:
>
> https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md
>
> Any volunteers for taking a crack at it? Can be edited via pull request
> right on github via clicking the "edit" button:
>
> https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md
>
> E.g. Need to release to dist/dev *before* npm
> E.g. Don't add -rc1 to versions anymore since those don't create archives
> we can vote on
> E.g. Probably don't need pre-emptive release branches anymore (although I
> think this can be up to each platform to decide on)
>
>
> Another question, can we do this without creating a v3.5.0 of the docs, as
> in Steve's proposal?
> https://docs
> .google.com/document/d/1qwpypH7sH0wH9Sbesmg8JZow-l8IqdZtF1BtLUZb1As/edit
>
> I think this would be a great time to switch to always edge/.
>
>
>
>
>
> On Fri, Apr 25, 2014 at 3:42 PM, Ian Clelland <iclelland@chromium.org
> >wrote:
>
> > It's probably time.
> >
> > Joe and I were discussing the possibility of including an (alpha) API for
> > pluggable webviews in a 3.5.0 release of cordova-android. I'd like to see
> > that in place, but it would probably not be ready until mid-next-week at
> > the earliest.
> >
> > iOS has had only a couple of commits since 3.4.1, so there's no rush
> there.
> > I have no doubt that the other platforms are overdue for a release,
> though.
> >
> >
> > On Fri, Apr 25, 2014 at 3:34 PM, Jesse <pu...@gmail.com> wrote:
> >
> > > There are numerous changes I would like to see pushed out. Can we start
> > > talking about a 3.5.0 platform release?
> > >
> > >
> > > @purplecabbage
> > > risingj.com
> > >
> >
>

Re: 3.5.0rc1

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

Would love to get to a platforms-independently-released world, but am happy
to do another cadence release.

In terms of getting our act together, we need to update our cadence release
process to not have the release to dist/ as an afterthought:
https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md

Any volunteers for taking a crack at it? Can be edited via pull request
right on github via clicking the "edit" button:
https://github.com/apache/cordova-coho/blob/master/docs/cadence-release-process.md

E.g. Need to release to dist/dev *before* npm
E.g. Don't add -rc1 to versions anymore since those don't create archives
we can vote on
E.g. Probably don't need pre-emptive release branches anymore (although I
think this can be up to each platform to decide on)


Another question, can we do this without creating a v3.5.0 of the docs, as
in Steve's proposal?
https://docs
.google.com/document/d/1qwpypH7sH0wH9Sbesmg8JZow-l8IqdZtF1BtLUZb1As/edit

I think this would be a great time to switch to always edge/.





On Fri, Apr 25, 2014 at 3:42 PM, Ian Clelland <ic...@chromium.org>wrote:

> It's probably time.
>
> Joe and I were discussing the possibility of including an (alpha) API for
> pluggable webviews in a 3.5.0 release of cordova-android. I'd like to see
> that in place, but it would probably not be ready until mid-next-week at
> the earliest.
>
> iOS has had only a couple of commits since 3.4.1, so there's no rush there.
> I have no doubt that the other platforms are overdue for a release, though.
>
>
> On Fri, Apr 25, 2014 at 3:34 PM, Jesse <pu...@gmail.com> wrote:
>
> > There are numerous changes I would like to see pushed out. Can we start
> > talking about a 3.5.0 platform release?
> >
> >
> > @purplecabbage
> > risingj.com
> >
>

Re: 3.5.0rc1

[Ian Clelland <ic...@chromium.org>]

It's probably time.

Joe and I were discussing the possibility of including an (alpha) API for
pluggable webviews in a 3.5.0 release of cordova-android. I'd like to see
that in place, but it would probably not be ready until mid-next-week at
the earliest.

iOS has had only a couple of commits since 3.4.1, so there's no rush there.
I have no doubt that the other platforms are overdue for a release, though.


On Fri, Apr 25, 2014 at 3:34 PM, Jesse <pu...@gmail.com> wrote:

> There are numerous changes I would like to see pushed out. Can we start
> talking about a 3.5.0 platform release?
>
>
> @purplecabbage
> risingj.com
>