You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@chromium.org> on 2014/03/13 16:38:02 UTC

Releasing Platforms Independently

I think it would be beneficial if we could release updates to platforms
independent from others. Why?
- Far easier to do one-off platform releases (e.g. quick turn-around on a
security update, quick turn around on iOS is broken on the latest Xcode)
- Platforms can release on their own schedule (big new features will get
released sooner)


This doesn't come without bumps though. I'd like to use this thread to
explore the idea and to enumerate what would have to change to get there.

Here are some things I can think of:

Cordova-docs:
- We have a version drop-down in the top-right corner.
- I think this would mean getting rid of the version drop down (or rather,
not adding new entries to it).
- Always have people pointed at "edge"
- For things that refer to specific versions, put them inline
  - E.g. like we do for upgrade guides
- When a new API is introduced & is documented, we'll have to be better at
annotating what version it showed up in.


Blog posts:
- We currently do one release announcement for all the platforms.
- I think it'll actually be a good thing to have shorter & more focused
release announcements (one post per platform)


Mobile-spec:
- This is on the way out anyway I think, with moving tests into plugins.
- Even so, not a big deal to not have this strictly versioned.


cordova-js:
 - Platforms will have cordova-js cut at different times.
   - I don't think this is a good or a bad thing.
 - JS versioning stamped at the top of the file:
   - Change to have both platform version as well as JS version available
at runtime.
   - JS version will just be a "git describe"

CLI versioning:
  - It won't make sense to version it as CadVer-SemVer anymore
    - This essentially kills off the idea of CadVer.
  - That scheme wasn't working well anyways since you can't actually depend
on the SemVer part of it in a SemVer way (you can't say
dependency=">x.x.x-0.2")
  - CadVer-SemVer, I think, is causing people to not update their tools if
they aren't ready to update their platforms.
  - With this change, we should just have CLI be SemVer only.
  - If we move platforms to NPM, we wouldn't even need to push CLI updates
with platforms.



Anything else? Please feel free to add inline here on things I've missed
out, or on things you'd be concerned about changing.

Re: Releasing Platforms Independently

Posted by luoq <lu...@polyvi.com>.
For docs, why don't you guys use yuidoc or jsduck, such js documentation tools, to manage docs? There is @since to indicate version, and rich builtin tags to use.

Furthermore, inline js documentation is much easier to maintain than a separate md doc, I believe.

It will be worse that the static markdown docs will get messed and hard to explore when there are lots of versions someday.

Thanks.


— 
Best Regards,
Qi LUO
Sent with Air

On 14 March, 2014 at 6:03:18, tommy-carlos (tommy@devgeeks.org) wrote:

+1 for docs.  

Pretty big pain point for devs.  

On 14 March 2014 at 7:01:18 am, Brian LeRoux (b@brian.io) wrote:  

I definitely love the idea of making this part of the machine move faster,  
and treating platforms as a dependency of the CLI in theory should not have  
any cross cutting impacts *unless* we decide to change the plugin  
interface. Our CLI version effectively becomes the 'Cordova' version. Docs  
needs an overhaul regardless so I see no issue there.  

How do you guys think we go about tackling this? Should we consider  
starting w/ the Docs since that seems to be the squeakiest wheel?  


On Thu, Mar 13, 2014 at 9:55 AM, Michal Mocny <mm...@chromium.org> wrote:   

> On Thu, Mar 13, 2014 at 11:38 AM, Andrew Grieve <agrieve@chromium.org  
> >wrote:  
>  
> > I think it would be beneficial if we could release updates to platforms  
> > independent from others. Why?  
> > - Far easier to do one-off platform releases (e.g. quick turn-around on a  
> > security update, quick turn around on iOS is broken on the latest Xcode)  
> > - Platforms can release on their own schedule (big new features will get  
> > released sooner)  
> >  
> >  
> > This doesn't come without bumps though. I'd like to use this thread to  
> > explore the idea and to enumerate what would have to change to get there.  
> >  
> > Here are some things I can think of:  
> >  
> > Cordova-docs:  
> > - We have a version drop-down in the top-right corner.  
> > - I think this would mean getting rid of the version drop down (or  
> rather,  
> > not adding new entries to it).  
> > - Always have people pointed at "edge"  
> > - For things that refer to specific versions, put them inline  
> > - E.g. like we do for upgrade guides  
> > - When a new API is introduced & is documented, we'll have to be better  
> at  
> > annotating what version it showed up in.  
> >  
>  
> Huge +1. This is a bit of an effort, sure, but every single damn time I  
> search for a cordova question I end up on docs for cordova 2.3 or  
> something, the version switcher takes me to home, and manually editing for  
> "edge" doesn't always match urls.  
>  
>  
> >  
> >  
> > Blog posts:  
> > - We currently do one release announcement for all the platforms.  
> > - I think it'll actually be a good thing to have shorter & more focused  
> > release announcements (one post per platform)  
> >  
>  
> I'm fine with this, but I do still think we want some special outlet to be  
> "louder" about larger changes much like we have been with monthly cadence  
> releases.  
>  
>  
> >  
> >  
> > Mobile-spec:  
> > - This is on the way out anyway I think, with moving tests into plugins.  
> > - Even so, not a big deal to not have this strictly versioned.  
>  
>  
> >  
> > cordova-js:  
> > - Platforms will have cordova-js cut at different times.  
> > - I don't think this is a good or a bad thing.  
> > - JS versioning stamped at the top of the file:  
> > - Change to have both platform version as well as JS version available  
> > at runtime.  
> > - JS version will just be a "git describe"  
> >  
> > CLI versioning:  
> > - It won't make sense to version it as CadVer-SemVer anymore  
> > - This essentially kills off the idea of CadVer.  
> > - That scheme wasn't working well anyways since you can't actually  
> depend  
> > on the SemVer part of it in a SemVer way (you can't say  
> > dependency=">x.x.x-0.2")  
> > - CadVer-SemVer, I think, is causing people to not update their tools  
> if  
> > they aren't ready to update their platforms.  
> > - With this change, we should just have CLI be SemVer only.  
> > - If we move platforms to NPM, we wouldn't even need to push CLI  
> updates  
> > with platforms.  
> >  
>  
> This is another huge benefit, I think.  
>  
>  
> >  
> >  
> >  
> > Anything else? Please feel free to add inline here on things I've missed  
> > out, or on things you'd be concerned about changing.  
> >  
>  
> Thanks for going over this. Sounds to me like this is almost entirely  
> upside.  
>  


Re: Releasing Platforms Independently

Posted by tommy-carlos williams <to...@devgeeks.org>.
+1 for docs.

Pretty big pain point for devs.

On 14 March 2014 at 7:01:18 am, Brian LeRoux (b@brian.io) wrote:

I definitely love the idea of making this part of the machine move faster, 
and treating platforms as a dependency of the CLI in theory should not have 
any cross cutting impacts *unless* we decide to change the plugin 
interface. Our CLI version effectively becomes the 'Cordova' version. Docs 
needs an overhaul regardless so I see no issue there. 

How do you guys think we go about tackling this? Should we consider 
starting w/ the Docs since that seems to be the squeakiest wheel? 


On Thu, Mar 13, 2014 at 9:55 AM, Michal Mocny <mm...@chromium.org> wrote: 

> On Thu, Mar 13, 2014 at 11:38 AM, Andrew Grieve <agrieve@chromium.org 
> >wrote: 
> 
> > I think it would be beneficial if we could release updates to platforms 
> > independent from others. Why? 
> > - Far easier to do one-off platform releases (e.g. quick turn-around on a 
> > security update, quick turn around on iOS is broken on the latest Xcode) 
> > - Platforms can release on their own schedule (big new features will get 
> > released sooner) 
> > 
> > 
> > This doesn't come without bumps though. I'd like to use this thread to 
> > explore the idea and to enumerate what would have to change to get there. 
> > 
> > Here are some things I can think of: 
> > 
> > Cordova-docs: 
> > - We have a version drop-down in the top-right corner. 
> > - I think this would mean getting rid of the version drop down (or 
> rather, 
> > not adding new entries to it). 
> > - Always have people pointed at "edge" 
> > - For things that refer to specific versions, put them inline 
> > - E.g. like we do for upgrade guides 
> > - When a new API is introduced & is documented, we'll have to be better 
> at 
> > annotating what version it showed up in. 
> > 
> 
> Huge +1. This is a bit of an effort, sure, but every single damn time I 
> search for a cordova question I end up on docs for cordova 2.3 or 
> something, the version switcher takes me to home, and manually editing for 
> "edge" doesn't always match urls. 
> 
> 
> > 
> > 
> > Blog posts: 
> > - We currently do one release announcement for all the platforms. 
> > - I think it'll actually be a good thing to have shorter & more focused 
> > release announcements (one post per platform) 
> > 
> 
> I'm fine with this, but I do still think we want some special outlet to be 
> "louder" about larger changes much like we have been with monthly cadence 
> releases. 
> 
> 
> > 
> > 
> > Mobile-spec: 
> > - This is on the way out anyway I think, with moving tests into plugins. 
> > - Even so, not a big deal to not have this strictly versioned. 
> 
> 
> > 
> > cordova-js: 
> > - Platforms will have cordova-js cut at different times. 
> > - I don't think this is a good or a bad thing. 
> > - JS versioning stamped at the top of the file: 
> > - Change to have both platform version as well as JS version available 
> > at runtime. 
> > - JS version will just be a "git describe" 
> > 
> > CLI versioning: 
> > - It won't make sense to version it as CadVer-SemVer anymore 
> > - This essentially kills off the idea of CadVer. 
> > - That scheme wasn't working well anyways since you can't actually 
> depend 
> > on the SemVer part of it in a SemVer way (you can't say 
> > dependency=">x.x.x-0.2") 
> > - CadVer-SemVer, I think, is causing people to not update their tools 
> if 
> > they aren't ready to update their platforms. 
> > - With this change, we should just have CLI be SemVer only. 
> > - If we move platforms to NPM, we wouldn't even need to push CLI 
> updates 
> > with platforms. 
> > 
> 
> This is another huge benefit, I think. 
> 
> 
> > 
> > 
> > 
> > Anything else? Please feel free to add inline here on things I've missed 
> > out, or on things you'd be concerned about changing. 
> > 
> 
> Thanks for going over this. Sounds to me like this is almost entirely 
> upside. 
> 


Re: Releasing Platforms Independently

Posted by Brian LeRoux <b...@brian.io>.
I definitely love the idea of making this part of the machine move faster,
and treating platforms as a dependency of the CLI in theory should not have
any cross cutting impacts *unless* we decide to change the plugin
interface. Our CLI version effectively becomes the 'Cordova' version. Docs
needs an overhaul regardless so I see no issue there.

How do you guys think we go about tackling this? Should we consider
starting w/ the Docs since that seems to be the squeakiest wheel?


On Thu, Mar 13, 2014 at 9:55 AM, Michal Mocny <mm...@chromium.org> wrote:

> On Thu, Mar 13, 2014 at 11:38 AM, Andrew Grieve <agrieve@chromium.org
> >wrote:
>
> > I think it would be beneficial if we could release updates to platforms
> > independent from others. Why?
> > - Far easier to do one-off platform releases (e.g. quick turn-around on a
> > security update, quick turn around on iOS is broken on the latest Xcode)
> > - Platforms can release on their own schedule (big new features will get
> > released sooner)
> >
> >
> > This doesn't come without bumps though. I'd like to use this thread to
> > explore the idea and to enumerate what would have to change to get there.
> >
> > Here are some things I can think of:
> >
> > Cordova-docs:
> > - We have a version drop-down in the top-right corner.
> > - I think this would mean getting rid of the version drop down (or
> rather,
> > not adding new entries to it).
> > - Always have people pointed at "edge"
> > - For things that refer to specific versions, put them inline
> >   - E.g. like we do for upgrade guides
> > - When a new API is introduced & is documented, we'll have to be better
> at
> > annotating what version it showed up in.
> >
>
> Huge +1.  This is a bit of an effort, sure, but every single damn time I
> search for a cordova question I end up on docs for cordova 2.3 or
> something, the version switcher takes me to home, and manually editing for
> "edge" doesn't always match urls.
>
>
> >
> >
> > Blog posts:
> > - We currently do one release announcement for all the platforms.
> > - I think it'll actually be a good thing to have shorter & more focused
> > release announcements (one post per platform)
> >
>
> I'm fine with this, but I do still think we want some special outlet to be
> "louder" about larger changes much like we have been with monthly cadence
> releases.
>
>
> >
> >
> > Mobile-spec:
> > - This is on the way out anyway I think, with moving tests into plugins.
> > - Even so, not a big deal to not have this strictly versioned.
>
>
> >
> > cordova-js:
> >  - Platforms will have cordova-js cut at different times.
> >    - I don't think this is a good or a bad thing.
> >  - JS versioning stamped at the top of the file:
> >    - Change to have both platform version as well as JS version available
> > at runtime.
> >    - JS version will just be a "git describe"
> >
> > CLI versioning:
> >   - It won't make sense to version it as CadVer-SemVer anymore
> >     - This essentially kills off the idea of CadVer.
> >   - That scheme wasn't working well anyways since you can't actually
> depend
> > on the SemVer part of it in a SemVer way (you can't say
> > dependency=">x.x.x-0.2")
> >   - CadVer-SemVer, I think, is causing people to not update their tools
> if
> > they aren't ready to update their platforms.
> >   - With this change, we should just have CLI be SemVer only.
> >   - If we move platforms to NPM, we wouldn't even need to push CLI
> updates
> > with platforms.
> >
>
> This is another huge benefit, I think.
>
>
> >
> >
> >
> > Anything else? Please feel free to add inline here on things I've missed
> > out, or on things you'd be concerned about changing.
> >
>
> Thanks for going over this.  Sounds to me like this is almost entirely
> upside.
>

Re: Releasing Platforms Independently

Posted by Michal Mocny <mm...@chromium.org>.
On Thu, Mar 13, 2014 at 11:38 AM, Andrew Grieve <ag...@chromium.org>wrote:

> I think it would be beneficial if we could release updates to platforms
> independent from others. Why?
> - Far easier to do one-off platform releases (e.g. quick turn-around on a
> security update, quick turn around on iOS is broken on the latest Xcode)
> - Platforms can release on their own schedule (big new features will get
> released sooner)
>
>
> This doesn't come without bumps though. I'd like to use this thread to
> explore the idea and to enumerate what would have to change to get there.
>
> Here are some things I can think of:
>
> Cordova-docs:
> - We have a version drop-down in the top-right corner.
> - I think this would mean getting rid of the version drop down (or rather,
> not adding new entries to it).
> - Always have people pointed at "edge"
> - For things that refer to specific versions, put them inline
>   - E.g. like we do for upgrade guides
> - When a new API is introduced & is documented, we'll have to be better at
> annotating what version it showed up in.
>

Huge +1.  This is a bit of an effort, sure, but every single damn time I
search for a cordova question I end up on docs for cordova 2.3 or
something, the version switcher takes me to home, and manually editing for
"edge" doesn't always match urls.


>
>
> Blog posts:
> - We currently do one release announcement for all the platforms.
> - I think it'll actually be a good thing to have shorter & more focused
> release announcements (one post per platform)
>

I'm fine with this, but I do still think we want some special outlet to be
"louder" about larger changes much like we have been with monthly cadence
releases.


>
>
> Mobile-spec:
> - This is on the way out anyway I think, with moving tests into plugins.
> - Even so, not a big deal to not have this strictly versioned.


>
> cordova-js:
>  - Platforms will have cordova-js cut at different times.
>    - I don't think this is a good or a bad thing.
>  - JS versioning stamped at the top of the file:
>    - Change to have both platform version as well as JS version available
> at runtime.
>    - JS version will just be a "git describe"
>
> CLI versioning:
>   - It won't make sense to version it as CadVer-SemVer anymore
>     - This essentially kills off the idea of CadVer.
>   - That scheme wasn't working well anyways since you can't actually depend
> on the SemVer part of it in a SemVer way (you can't say
> dependency=">x.x.x-0.2")
>   - CadVer-SemVer, I think, is causing people to not update their tools if
> they aren't ready to update their platforms.
>   - With this change, we should just have CLI be SemVer only.
>   - If we move platforms to NPM, we wouldn't even need to push CLI updates
> with platforms.
>

This is another huge benefit, I think.


>
>
>
> Anything else? Please feel free to add inline here on things I've missed
> out, or on things you'd be concerned about changing.
>

Thanks for going over this.  Sounds to me like this is almost entirely
upside.

Re: Releasing Platforms Independently

Posted by Steven Gill <st...@gmail.com>.
I can look into doing this post apachecon.


On Mon, Mar 17, 2014 at 8:49 PM, Andrew Grieve <ag...@chromium.org> wrote:

> Awesome to hear enthusiasm here! :)
>
> So... any volunteers to
> a) Make a proposal to *how* to change the docs, and
> b) Code up docs changes?
>
>
> On Mon, Mar 17, 2014 at 11:38 PM, Michal Mocny <mm...@chromium.org>
> wrote:
>
> > On Fri, Mar 14, 2014 at 1:02 PM, Shazron <sh...@gmail.com> wrote:
> >
> > > +1. especially for moving testing away from the mobile-spec monolith.
> > >
> > > Recently I discovered a bug
> > > https://issues.apache.org/jira/browse/CB-6225that caused some pain for
> > > users. Since it was all tested in mobile-spec and
> > > it wasn't tested individually, it could not have been discovered (new
> > Media
> > > plugin has a new dependency on File -- when installed in mob-spec, all
> > > plugins are installed). Having separate tests running in isolation
> would
> > > have better discovered this.
> > >
> >
> > In full fairness, tests bundled with plugins would still rely on you to
> > create an independent cordova project with each plugin to properly catch
> > this case.  The more common case is a single workspace with all plugins
> > installed, since thats a lot easier.
> >
> > Should probably add a step to CI that tests in independent workspaces (do
> > we have JIRA issues for CI?  Theres no official set of CI tests for
> apache
> > yet).
> >
> >
> > >
> > >
> > > On Thu, Mar 13, 2014 at 8:38 AM, Andrew Grieve <ag...@chromium.org>
> > > wrote:
> > >
> > > > I think it would be beneficial if we could release updates to
> platforms
> > > > independent from others. Why?
> > > > - Far easier to do one-off platform releases (e.g. quick turn-around
> > on a
> > > > security update, quick turn around on iOS is broken on the latest
> > Xcode)
> > > > - Platforms can release on their own schedule (big new features will
> > get
> > > > released sooner)
> > > >
> > > >
> > > > This doesn't come without bumps though. I'd like to use this thread
> to
> > > > explore the idea and to enumerate what would have to change to get
> > there.
> > > >
> > > > Here are some things I can think of:
> > > >
> > > > Cordova-docs:
> > > > - We have a version drop-down in the top-right corner.
> > > > - I think this would mean getting rid of the version drop down (or
> > > rather,
> > > > not adding new entries to it).
> > > > - Always have people pointed at "edge"
> > > > - For things that refer to specific versions, put them inline
> > > >   - E.g. like we do for upgrade guides
> > > > - When a new API is introduced & is documented, we'll have to be
> better
> > > at
> > > > annotating what version it showed up in.
> > > >
> > > >
> > > > Blog posts:
> > > > - We currently do one release announcement for all the platforms.
> > > > - I think it'll actually be a good thing to have shorter & more
> focused
> > > > release announcements (one post per platform)
> > > >
> > > >
> > > > Mobile-spec:
> > > > - This is on the way out anyway I think, with moving tests into
> > plugins.
> > > > - Even so, not a big deal to not have this strictly versioned.
> > > >
> > > >
> > > > cordova-js:
> > > >  - Platforms will have cordova-js cut at different times.
> > > >    - I don't think this is a good or a bad thing.
> > > >  - JS versioning stamped at the top of the file:
> > > >    - Change to have both platform version as well as JS version
> > available
> > > > at runtime.
> > > >    - JS version will just be a "git describe"
> > > >
> > > > CLI versioning:
> > > >   - It won't make sense to version it as CadVer-SemVer anymore
> > > >     - This essentially kills off the idea of CadVer.
> > > >   - That scheme wasn't working well anyways since you can't actually
> > > depend
> > > > on the SemVer part of it in a SemVer way (you can't say
> > > > dependency=">x.x.x-0.2")
> > > >   - CadVer-SemVer, I think, is causing people to not update their
> tools
> > > if
> > > > they aren't ready to update their platforms.
> > > >   - With this change, we should just have CLI be SemVer only.
> > > >   - If we move platforms to NPM, we wouldn't even need to push CLI
> > > updates
> > > > with platforms.
> > > >
> > > >
> > > >
> > > > Anything else? Please feel free to add inline here on things I've
> > missed
> > > > out, or on things you'd be concerned about changing.
> > > >
> > >
> >
>

Re: Releasing Platforms Independently

Posted by Andrew Grieve <ag...@chromium.org>.
Awesome to hear enthusiasm here! :)

So... any volunteers to
a) Make a proposal to *how* to change the docs, and
b) Code up docs changes?


On Mon, Mar 17, 2014 at 11:38 PM, Michal Mocny <mm...@chromium.org> wrote:

> On Fri, Mar 14, 2014 at 1:02 PM, Shazron <sh...@gmail.com> wrote:
>
> > +1. especially for moving testing away from the mobile-spec monolith.
> >
> > Recently I discovered a bug
> > https://issues.apache.org/jira/browse/CB-6225that caused some pain for
> > users. Since it was all tested in mobile-spec and
> > it wasn't tested individually, it could not have been discovered (new
> Media
> > plugin has a new dependency on File -- when installed in mob-spec, all
> > plugins are installed). Having separate tests running in isolation would
> > have better discovered this.
> >
>
> In full fairness, tests bundled with plugins would still rely on you to
> create an independent cordova project with each plugin to properly catch
> this case.  The more common case is a single workspace with all plugins
> installed, since thats a lot easier.
>
> Should probably add a step to CI that tests in independent workspaces (do
> we have JIRA issues for CI?  Theres no official set of CI tests for apache
> yet).
>
>
> >
> >
> > On Thu, Mar 13, 2014 at 8:38 AM, Andrew Grieve <ag...@chromium.org>
> > wrote:
> >
> > > I think it would be beneficial if we could release updates to platforms
> > > independent from others. Why?
> > > - Far easier to do one-off platform releases (e.g. quick turn-around
> on a
> > > security update, quick turn around on iOS is broken on the latest
> Xcode)
> > > - Platforms can release on their own schedule (big new features will
> get
> > > released sooner)
> > >
> > >
> > > This doesn't come without bumps though. I'd like to use this thread to
> > > explore the idea and to enumerate what would have to change to get
> there.
> > >
> > > Here are some things I can think of:
> > >
> > > Cordova-docs:
> > > - We have a version drop-down in the top-right corner.
> > > - I think this would mean getting rid of the version drop down (or
> > rather,
> > > not adding new entries to it).
> > > - Always have people pointed at "edge"
> > > - For things that refer to specific versions, put them inline
> > >   - E.g. like we do for upgrade guides
> > > - When a new API is introduced & is documented, we'll have to be better
> > at
> > > annotating what version it showed up in.
> > >
> > >
> > > Blog posts:
> > > - We currently do one release announcement for all the platforms.
> > > - I think it'll actually be a good thing to have shorter & more focused
> > > release announcements (one post per platform)
> > >
> > >
> > > Mobile-spec:
> > > - This is on the way out anyway I think, with moving tests into
> plugins.
> > > - Even so, not a big deal to not have this strictly versioned.
> > >
> > >
> > > cordova-js:
> > >  - Platforms will have cordova-js cut at different times.
> > >    - I don't think this is a good or a bad thing.
> > >  - JS versioning stamped at the top of the file:
> > >    - Change to have both platform version as well as JS version
> available
> > > at runtime.
> > >    - JS version will just be a "git describe"
> > >
> > > CLI versioning:
> > >   - It won't make sense to version it as CadVer-SemVer anymore
> > >     - This essentially kills off the idea of CadVer.
> > >   - That scheme wasn't working well anyways since you can't actually
> > depend
> > > on the SemVer part of it in a SemVer way (you can't say
> > > dependency=">x.x.x-0.2")
> > >   - CadVer-SemVer, I think, is causing people to not update their tools
> > if
> > > they aren't ready to update their platforms.
> > >   - With this change, we should just have CLI be SemVer only.
> > >   - If we move platforms to NPM, we wouldn't even need to push CLI
> > updates
> > > with platforms.
> > >
> > >
> > >
> > > Anything else? Please feel free to add inline here on things I've
> missed
> > > out, or on things you'd be concerned about changing.
> > >
> >
>

Re: Releasing Platforms Independently

Posted by Michal Mocny <mm...@chromium.org>.
On Fri, Mar 14, 2014 at 1:02 PM, Shazron <sh...@gmail.com> wrote:

> +1. especially for moving testing away from the mobile-spec monolith.
>
> Recently I discovered a bug
> https://issues.apache.org/jira/browse/CB-6225that caused some pain for
> users. Since it was all tested in mobile-spec and
> it wasn't tested individually, it could not have been discovered (new Media
> plugin has a new dependency on File -- when installed in mob-spec, all
> plugins are installed). Having separate tests running in isolation would
> have better discovered this.
>

In full fairness, tests bundled with plugins would still rely on you to
create an independent cordova project with each plugin to properly catch
this case.  The more common case is a single workspace with all plugins
installed, since thats a lot easier.

Should probably add a step to CI that tests in independent workspaces (do
we have JIRA issues for CI?  Theres no official set of CI tests for apache
yet).


>
>
> On Thu, Mar 13, 2014 at 8:38 AM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > I think it would be beneficial if we could release updates to platforms
> > independent from others. Why?
> > - Far easier to do one-off platform releases (e.g. quick turn-around on a
> > security update, quick turn around on iOS is broken on the latest Xcode)
> > - Platforms can release on their own schedule (big new features will get
> > released sooner)
> >
> >
> > This doesn't come without bumps though. I'd like to use this thread to
> > explore the idea and to enumerate what would have to change to get there.
> >
> > Here are some things I can think of:
> >
> > Cordova-docs:
> > - We have a version drop-down in the top-right corner.
> > - I think this would mean getting rid of the version drop down (or
> rather,
> > not adding new entries to it).
> > - Always have people pointed at "edge"
> > - For things that refer to specific versions, put them inline
> >   - E.g. like we do for upgrade guides
> > - When a new API is introduced & is documented, we'll have to be better
> at
> > annotating what version it showed up in.
> >
> >
> > Blog posts:
> > - We currently do one release announcement for all the platforms.
> > - I think it'll actually be a good thing to have shorter & more focused
> > release announcements (one post per platform)
> >
> >
> > Mobile-spec:
> > - This is on the way out anyway I think, with moving tests into plugins.
> > - Even so, not a big deal to not have this strictly versioned.
> >
> >
> > cordova-js:
> >  - Platforms will have cordova-js cut at different times.
> >    - I don't think this is a good or a bad thing.
> >  - JS versioning stamped at the top of the file:
> >    - Change to have both platform version as well as JS version available
> > at runtime.
> >    - JS version will just be a "git describe"
> >
> > CLI versioning:
> >   - It won't make sense to version it as CadVer-SemVer anymore
> >     - This essentially kills off the idea of CadVer.
> >   - That scheme wasn't working well anyways since you can't actually
> depend
> > on the SemVer part of it in a SemVer way (you can't say
> > dependency=">x.x.x-0.2")
> >   - CadVer-SemVer, I think, is causing people to not update their tools
> if
> > they aren't ready to update their platforms.
> >   - With this change, we should just have CLI be SemVer only.
> >   - If we move platforms to NPM, we wouldn't even need to push CLI
> updates
> > with platforms.
> >
> >
> >
> > Anything else? Please feel free to add inline here on things I've missed
> > out, or on things you'd be concerned about changing.
> >
>

Re: Releasing Platforms Independently

Posted by Shazron <sh...@gmail.com>.
+1. especially for moving testing away from the mobile-spec monolith.

Recently I discovered a bug
https://issues.apache.org/jira/browse/CB-6225that caused some pain for
users. Since it was all tested in mobile-spec and
it wasn't tested individually, it could not have been discovered (new Media
plugin has a new dependency on File -- when installed in mob-spec, all
plugins are installed). Having separate tests running in isolation would
have better discovered this.


On Thu, Mar 13, 2014 at 8:38 AM, Andrew Grieve <ag...@chromium.org> wrote:

> I think it would be beneficial if we could release updates to platforms
> independent from others. Why?
> - Far easier to do one-off platform releases (e.g. quick turn-around on a
> security update, quick turn around on iOS is broken on the latest Xcode)
> - Platforms can release on their own schedule (big new features will get
> released sooner)
>
>
> This doesn't come without bumps though. I'd like to use this thread to
> explore the idea and to enumerate what would have to change to get there.
>
> Here are some things I can think of:
>
> Cordova-docs:
> - We have a version drop-down in the top-right corner.
> - I think this would mean getting rid of the version drop down (or rather,
> not adding new entries to it).
> - Always have people pointed at "edge"
> - For things that refer to specific versions, put them inline
>   - E.g. like we do for upgrade guides
> - When a new API is introduced & is documented, we'll have to be better at
> annotating what version it showed up in.
>
>
> Blog posts:
> - We currently do one release announcement for all the platforms.
> - I think it'll actually be a good thing to have shorter & more focused
> release announcements (one post per platform)
>
>
> Mobile-spec:
> - This is on the way out anyway I think, with moving tests into plugins.
> - Even so, not a big deal to not have this strictly versioned.
>
>
> cordova-js:
>  - Platforms will have cordova-js cut at different times.
>    - I don't think this is a good or a bad thing.
>  - JS versioning stamped at the top of the file:
>    - Change to have both platform version as well as JS version available
> at runtime.
>    - JS version will just be a "git describe"
>
> CLI versioning:
>   - It won't make sense to version it as CadVer-SemVer anymore
>     - This essentially kills off the idea of CadVer.
>   - That scheme wasn't working well anyways since you can't actually depend
> on the SemVer part of it in a SemVer way (you can't say
> dependency=">x.x.x-0.2")
>   - CadVer-SemVer, I think, is causing people to not update their tools if
> they aren't ready to update their platforms.
>   - With this change, we should just have CLI be SemVer only.
>   - If we move platforms to NPM, we wouldn't even need to push CLI updates
> with platforms.
>
>
>
> Anything else? Please feel free to add inline here on things I've missed
> out, or on things you'd be concerned about changing.
>

RE: Releasing Platforms Independently

Posted by Jonathan Bond-Caron <jb...@gdesolutions.com>.
On Thu Mar 13 11:38 AM, Andrew Grieve wrote:
> I think it would be beneficial if we could release updates to platforms
> independent from others. Why?
> - Far easier to do one-off platform releases (e.g. quick turn-around on a security
> update, quick turn around on iOS is broken on the latest Xcode)
> - Platforms can release on their own schedule (big new features will get released
> sooner)
> 

+1

> 
> cordova-js:
>  - Platforms will have cordova-js cut at different times.
>    - I don't think this is a good or a bad thing.
>  - JS versioning stamped at the top of the file:
>    - Change to have both platform version as well as JS version available at
> runtime.
>    - JS version will just be a "git describe"
> 

I've been thinking we could go a step further and break out 'platforms' into two parts:
- platform engine (build, run, emulate tooling) 
- platform runtime (webview, cordova-js, the stuff needed by web app)

<engine> tags in plugin.xml are really only about checking the tooling at install time, from what I understand