Re: [DISCUSS] Cordova-browser release
Lgtm! > On Mar 9, 2016, at 10:55 AM, Vladimir Kotikov (Akvelon) > wrote: > > Thanks, Carlos > > - > Best regards, Vladmir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Wednesday, March 9, 2016 7:24 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Cordova-browser release > > blog post looks good > >> On Wed, Mar 9, 2016 at 10:09 AM Vladimir Kotikov (Akvelon) < >> v-vlk...@microsoft.com> wrote: >> >> Friendly pinging... >> >> - >> Best regards, Vladimir >> >> -Original Message- >> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] >> Sent: Friday, March 4, 2016 5:57 PM >> To: dev@cordova.apache.org >> Subject: RE: [DISCUSS] Cordova-browser release >> >> Blog post: https://github.com/apache/cordova-docs/pull/539 >> >> Please review and comment >> >> - >> Best regards, Vladimir >> >> -----Original Message- >> From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] >> Sent: Friday, March 4, 2016 4:02 PM >> To: dev@cordova.apache.org >> Subject: RE: [DISCUSS] Cordova-browser release >> >> Hey, guys. >> >> Here is a release notes for this release: >> >> ### 4.1.0 (Mar 04, 2016) >> * CB-10788 Updated checked in node_modules >> * CB-10650 Non-index content.src causes Splashscreen to be not >> displayed on browser >> * CB-9836 Add .gitattributes to prevent CRLF line endings in repos >> * CB-9669 Browser exec should have more failsafes >> * Update to use new 'express' implementation of cordova-serve. >> * CB-9658 Improve 'cordova run browser' when browser not installed. >> * CB-9654 'cordova run browser' -> duplicate 'CTRL + C' messages. >> >> Also while testing I've found that there are some failed tests, incl. >> contacts, device, device-motion, etc. I don't think this is a blocker, >> so just FYI. >> >> - >> Best regards, Vladimir >> >> -Original Message- >> From: Carlos Santana [mailto:csantan...@gmail.com] >> Sent: Wednesday, March 2, 2016 8:37 PM >> To: dev@cordova.apache.org >> Subject: Re: [DISCUSS] Cordova-browser release >> >> +1 to ^ >> >>> On Wed, Mar 2, 2016 at 1:21 AM Steven Gill wrote: >>> >>> Yes, follow semver! >>> >>> If we can get a good track record of following semver, I'd like to >>> see us switch to ^ with our pinned platforms and plugins so minors >>> get picked up automatically. >>> >>> On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham >>> >>> wrote: >>> >>>> It's been a long time since we did a cordova-browser release, and >>>> there have been many improvements since then. Should we get a >>>> release out >>> before >>>> the next tools release? >>>> >>>> If so, what should the version be? Proper npm versioning would >>>> suggest we go with 4.1.0 (since it is more than just bug fixes), >>>> but since we currently pin ~4.0.0 in cordova-lib, that will mean >>>> people won't get it automatically, and it's very unlikely there >>>> are backward >> compat issues. >>>> Still, I guess 4.1.0 is the right thing to do. >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org >> For additional commands, e-mail: dev-h...@cordova.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] Cordova-browser release
Thanks, Carlos - Best regards, Vladmir -Original Message- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Wednesday, March 9, 2016 7:24 PM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova-browser release blog post looks good On Wed, Mar 9, 2016 at 10:09 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > Friendly pinging... > > - > Best regards, Vladimir > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Friday, March 4, 2016 5:57 PM > To: dev@cordova.apache.org > Subject: RE: [DISCUSS] Cordova-browser release > > Blog post: https://github.com/apache/cordova-docs/pull/539 > > Please review and comment > > - > Best regards, Vladimir > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Friday, March 4, 2016 4:02 PM > To: dev@cordova.apache.org > Subject: RE: [DISCUSS] Cordova-browser release > > Hey, guys. > > Here is a release notes for this release: > > ### 4.1.0 (Mar 04, 2016) > * CB-10788 Updated checked in node_modules > * CB-10650 Non-index content.src causes Splashscreen to be not > displayed on browser > * CB-9836 Add .gitattributes to prevent CRLF line endings in repos > * CB-9669 Browser exec should have more failsafes > * Update to use new 'express' implementation of cordova-serve. > * CB-9658 Improve 'cordova run browser' when browser not installed. > * CB-9654 'cordova run browser' -> duplicate 'CTRL + C' messages. > > Also while testing I've found that there are some failed tests, incl. > contacts, device, device-motion, etc. I don't think this is a blocker, > so just FYI. > > - > Best regards, Vladimir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Wednesday, March 2, 2016 8:37 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Cordova-browser release > > +1 to ^ > > On Wed, Mar 2, 2016 at 1:21 AM Steven Gill wrote: > > > Yes, follow semver! > > > > If we can get a good track record of following semver, I'd like to > > see us switch to ^ with our pinned platforms and plugins so minors > > get picked up automatically. > > > > On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham > > > > wrote: > > > > > It's been a long time since we did a cordova-browser release, and > > > there have been many improvements since then. Should we get a > > > release out > > before > > > the next tools release? > > > > > > If so, what should the version be? Proper npm versioning would > > > suggest we go with 4.1.0 (since it is more than just bug fixes), > > > but since we currently pin ~4.0.0 in cordova-lib, that will mean > > > people won't get it automatically, and it's very unlikely there > > > are backward > compat issues. > > > Still, I guess 4.1.0 is the right thing to do. > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Cordova-browser release
blog post looks good On Wed, Mar 9, 2016 at 10:09 AM Vladimir Kotikov (Akvelon) < v-vlk...@microsoft.com> wrote: > Friendly pinging... > > - > Best regards, Vladimir > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Friday, March 4, 2016 5:57 PM > To: dev@cordova.apache.org > Subject: RE: [DISCUSS] Cordova-browser release > > Blog post: https://github.com/apache/cordova-docs/pull/539 > > Please review and comment > > - > Best regards, Vladimir > > -Original Message- > From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] > Sent: Friday, March 4, 2016 4:02 PM > To: dev@cordova.apache.org > Subject: RE: [DISCUSS] Cordova-browser release > > Hey, guys. > > Here is a release notes for this release: > > ### 4.1.0 (Mar 04, 2016) > * CB-10788 Updated checked in node_modules > * CB-10650 Non-index content.src causes Splashscreen to be not displayed > on browser > * CB-9836 Add .gitattributes to prevent CRLF line endings in repos > * CB-9669 Browser exec should have more failsafes > * Update to use new 'express' implementation of cordova-serve. > * CB-9658 Improve 'cordova run browser' when browser not installed. > * CB-9654 'cordova run browser' -> duplicate 'CTRL + C' messages. > > Also while testing I've found that there are some failed tests, incl. > contacts, device, device-motion, etc. I don't think this is a blocker, so > just FYI. > > - > Best regards, Vladimir > > -Original Message- > From: Carlos Santana [mailto:csantan...@gmail.com] > Sent: Wednesday, March 2, 2016 8:37 PM > To: dev@cordova.apache.org > Subject: Re: [DISCUSS] Cordova-browser release > > +1 to ^ > > On Wed, Mar 2, 2016 at 1:21 AM Steven Gill wrote: > > > Yes, follow semver! > > > > If we can get a good track record of following semver, I'd like to see > > us switch to ^ with our pinned platforms and plugins so minors get > > picked up automatically. > > > > On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham > > wrote: > > > > > It's been a long time since we did a cordova-browser release, and > > > there have been many improvements since then. Should we get a > > > release out > > before > > > the next tools release? > > > > > > If so, what should the version be? Proper npm versioning would > > > suggest we go with 4.1.0 (since it is more than just bug fixes), but > > > since we currently pin ~4.0.0 in cordova-lib, that will mean people > > > won't get it automatically, and it's very unlikely there are backward > compat issues. > > > Still, I guess 4.1.0 is the right thing to do. > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org >
RE: [DISCUSS] Cordova-browser release
Friendly pinging... - Best regards, Vladimir -Original Message- From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] Sent: Friday, March 4, 2016 5:57 PM To: dev@cordova.apache.org Subject: RE: [DISCUSS] Cordova-browser release Blog post: https://github.com/apache/cordova-docs/pull/539 Please review and comment - Best regards, Vladimir -Original Message- From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] Sent: Friday, March 4, 2016 4:02 PM To: dev@cordova.apache.org Subject: RE: [DISCUSS] Cordova-browser release Hey, guys. Here is a release notes for this release: ### 4.1.0 (Mar 04, 2016) * CB-10788 Updated checked in node_modules * CB-10650 Non-index content.src causes Splashscreen to be not displayed on browser * CB-9836 Add .gitattributes to prevent CRLF line endings in repos * CB-9669 Browser exec should have more failsafes * Update to use new 'express' implementation of cordova-serve. * CB-9658 Improve 'cordova run browser' when browser not installed. * CB-9654 'cordova run browser' -> duplicate 'CTRL + C' messages. Also while testing I've found that there are some failed tests, incl. contacts, device, device-motion, etc. I don't think this is a blocker, so just FYI. - Best regards, Vladimir -Original Message- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Wednesday, March 2, 2016 8:37 PM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova-browser release +1 to ^ On Wed, Mar 2, 2016 at 1:21 AM Steven Gill wrote: > Yes, follow semver! > > If we can get a good track record of following semver, I'd like to see > us switch to ^ with our pinned platforms and plugins so minors get > picked up automatically. > > On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham > wrote: > > > It's been a long time since we did a cordova-browser release, and > > there have been many improvements since then. Should we get a > > release out > before > > the next tools release? > > > > If so, what should the version be? Proper npm versioning would > > suggest we go with 4.1.0 (since it is more than just bug fixes), but > > since we currently pin ~4.0.0 in cordova-lib, that will mean people > > won't get it automatically, and it's very unlikely there are backward > > compat issues. > > Still, I guess 4.1.0 is the right thing to do. > > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] Cordova-browser release
Blog post: https://github.com/apache/cordova-docs/pull/539 Please review and comment - Best regards, Vladimir -Original Message- From: Vladimir Kotikov (Akvelon) [mailto:v-vlk...@microsoft.com] Sent: Friday, March 4, 2016 4:02 PM To: dev@cordova.apache.org Subject: RE: [DISCUSS] Cordova-browser release Hey, guys. Here is a release notes for this release: ### 4.1.0 (Mar 04, 2016) * CB-10788 Updated checked in node_modules * CB-10650 Non-index content.src causes Splashscreen to be not displayed on browser * CB-9836 Add .gitattributes to prevent CRLF line endings in repos * CB-9669 Browser exec should have more failsafes * Update to use new 'express' implementation of cordova-serve. * CB-9658 Improve 'cordova run browser' when browser not installed. * CB-9654 'cordova run browser' -> duplicate 'CTRL + C' messages. Also while testing I've found that there are some failed tests, incl. contacts, device, device-motion, etc. I don't think this is a blocker, so just FYI. - Best regards, Vladimir -Original Message- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Wednesday, March 2, 2016 8:37 PM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova-browser release +1 to ^ On Wed, Mar 2, 2016 at 1:21 AM Steven Gill wrote: > Yes, follow semver! > > If we can get a good track record of following semver, I'd like to see > us switch to ^ with our pinned platforms and plugins so minors get > picked up automatically. > > On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham > wrote: > > > It's been a long time since we did a cordova-browser release, and > > there have been many improvements since then. Should we get a > > release out > before > > the next tools release? > > > > If so, what should the version be? Proper npm versioning would > > suggest we go with 4.1.0 (since it is more than just bug fixes), but > > since we currently pin ~4.0.0 in cordova-lib, that will mean people > > won't get it automatically, and it's very unlikely there are backward > > compat issues. > > Still, I guess 4.1.0 is the right thing to do. > > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
RE: [DISCUSS] Cordova-browser release
Hey, guys. Here is a release notes for this release: ### 4.1.0 (Mar 04, 2016) * CB-10788 Updated checked in node_modules * CB-10650 Non-index content.src causes Splashscreen to be not displayed on browser * CB-9836 Add .gitattributes to prevent CRLF line endings in repos * CB-9669 Browser exec should have more failsafes * Update to use new 'express' implementation of cordova-serve. * CB-9658 Improve 'cordova run browser' when browser not installed. * CB-9654 'cordova run browser' -> duplicate 'CTRL + C' messages. Also while testing I've found that there are some failed tests, incl. contacts, device, device-motion, etc. I don't think this is a blocker, so just FYI. - Best regards, Vladimir -Original Message- From: Carlos Santana [mailto:csantan...@gmail.com] Sent: Wednesday, March 2, 2016 8:37 PM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Cordova-browser release +1 to ^ On Wed, Mar 2, 2016 at 1:21 AM Steven Gill wrote: > Yes, follow semver! > > If we can get a good track record of following semver, I'd like to see > us switch to ^ with our pinned platforms and plugins so minors get > picked up automatically. > > On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham > wrote: > > > It's been a long time since we did a cordova-browser release, and > > there have been many improvements since then. Should we get a > > release out > before > > the next tools release? > > > > If so, what should the version be? Proper npm versioning would > > suggest we go with 4.1.0 (since it is more than just bug fixes), but > > since we currently pin ~4.0.0 in cordova-lib, that will mean people > > won't get it automatically, and it's very unlikely there are backward > > compat issues. > > Still, I guess 4.1.0 is the right thing to do. > > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Cordova-browser release
+1 to ^ On Wed, Mar 2, 2016 at 1:21 AM Steven Gill wrote: > Yes, follow semver! > > If we can get a good track record of following semver, I'd like to see us > switch to ^ with our pinned platforms and plugins so minors get picked up > automatically. > > On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham > wrote: > > > It's been a long time since we did a cordova-browser release, and there > > have been many improvements since then. Should we get a release out > before > > the next tools release? > > > > If so, what should the version be? Proper npm versioning would suggest we > > go with 4.1.0 (since it is more than just bug fixes), but since we > > currently pin ~4.0.0 in cordova-lib, that will mean people won't get it > > automatically, and it's very unlikely there are backward compat issues. > > Still, I guess 4.1.0 is the right thing to do. > > >
Re: [DISCUSS] Cordova-browser release
Yes, follow semver! If we can get a good track record of following semver, I'd like to see us switch to ^ with our pinned platforms and plugins so minors get picked up automatically. On Tue, Mar 1, 2016 at 7:01 PM, Tim Barham wrote: > It's been a long time since we did a cordova-browser release, and there > have been many improvements since then. Should we get a release out before > the next tools release? > > If so, what should the version be? Proper npm versioning would suggest we > go with 4.1.0 (since it is more than just bug fixes), but since we > currently pin ~4.0.0 in cordova-lib, that will mean people won't get it > automatically, and it's very unlikely there are backward compat issues. > Still, I guess 4.1.0 is the right thing to do. >
