If you refer to the git flow, the intention was not to make the process
faster, the intention was to make the process easier and to not freeze
progress on master. Both have been addressed (yes, there is a learning
curve, lets give it at least one more release to conclude, yeah?)
In order to actua
I prefer cordova-harness to cordova-app myself.
Simon Mac Donald
http://hi.im/simonmacdonald
On Thu, Mar 28, 2013 at 8:37 PM, Michal Mocny wrote:
> FWIW, I dont think thats a good idea. Will likely lead to ambiguity
> between "a cordova app" and "the cordova-app", not to mention googleability.
FWIW, I dont think thats a good idea. Will likely lead to ambiguity
between "a cordova app" and "the cordova-app", not to mention googleability.
Sorry, but I don't have any awesome suggestions, but I thought
cordova-harness was fine.
-Michal
On Thu, Mar 28, 2013 at 5:56 PM, Brian LeRoux wrote
Thanks for all your contributions & best of luck in the future!
> From: f...@adobe.com
> To: dev@cordova.apache.org
> Date: Thu, 28 Mar 2013 11:02:14 -0700
> Subject: Re: Farewell
>
> Cheers man good luck, thanks for all your hard work!
>
> On 3/28/13 9:38 AM, "Michael Brooks" wrote:
>
> >Than
cordova-app sounds good to me
On Thu, Mar 28, 2013 at 2:45 PM, Andrew Grieve wrote:
> I don't think we need to decide on an App Store name yet. Repo name sounds
> good though.
>
> On Thu, Mar 28, 2013 at 4:40 PM, Michael Brooks
> wrote:
>
>> Alright, I want to get this project started and we nee
I don't think we need to decide on an App Store name yet. Repo name sounds
good though.
On Thu, Mar 28, 2013 at 4:40 PM, Michael Brooks wrote:
> Alright, I want to get this project started and we need to settle on a
> name.
>
> No one has made a compelling argument against calling the app "Cordov
Alright, I want to get this project started and we need to settle on a name.
No one has made a compelling argument against calling the app "Cordova."
Proposed name:
- App Store name: "Cordova"
- Repository name: "cordova-app"
Here are my reasons:
1. We naturally refer to it as "The Cordova App
Fil, great work on the wiki document. Below are some feedback points.
> `build`
...
What happens when a user specifies both --debug and --release?
I'm happy as long as we decide on what happens. For the sake of ease, I
think it would be better to just fail.
This brings up the question of exi
Hey
I'm wondering if we should just tag 2.6.0 on the long-lived branch? I
feel like we've taken too long with the RC process, and we really need
to re-evaluate this process, since it's just as slow, if not slower
than the old process.
Thoughts?
Joe
Hi All,
I am working on a set of plugins for Eclipse that will eventually be part
of the JBoss IDE. I seem to have similar requirements to cordova-cli and
noticed that some of the things that are planned for cli is well aligned
with our plans. So I am hoping to contribute as much as I can.
We also
Tagging iOS. Although there were a few fix commits after the initial rc1
tag. No biggie if no one downloaded it, but I'd rather do a new tag next
time for this situation (since this fix is not critical for iOS).
On Wed, Mar 27, 2013 at 1:26 PM, Filip Maj wrote:
> JS is re-tagged and the 2.6.0rc
Thank you, good pseudocode.
I might add:
addEventListener('merge', function(from, to) {
if ((from == 'master' && to == '2.6.x') ||
(from == '2.6.x' && to == 'master')) {
throw new Error("No! Bad kitty.");
}
});
On Thu, Mar 28, 2013 at 12:54 PM, James Jong wrote:
> commitToBr
Cheers man good luck, thanks for all your hard work!
On 3/28/13 9:38 AM, "Michael Brooks" wrote:
>Thanks Markus for all your work, help, and advice! Best of luck in the
>future and feel free to chime-in whenever you can!
>
>Michael
>
>On Thu, Mar 28, 2013 at 9:20 AM, Brian LeRoux wrote:
>
>> Th
commitToBranch('master');
if (inReleaseMode && commitFixesRegression) {
cherryPickCommit('CB-').from('master').into('releaseBranch');
}
-James Jong
On Mar 28, 2013, at 11:07 AM, Michal Mocny wrote:
> We create branch when we decide to cut a release. This is the cut off for
> features.
Thanks Markus for all your work, help, and advice! Best of luck in the
future and feel free to chime-in whenever you can!
Michael
On Thu, Mar 28, 2013 at 9:20 AM, Brian LeRoux wrote:
> Thanks so much and don't be stranger Markus! Let us know if ever you
> need our help.
>
> On Thu, Mar 28, 2013
Thanks so much and don't be stranger Markus! Let us know if ever you
need our help.
On Thu, Mar 28, 2013 at 8:38 AM, Lorin Beer wrote:
> thanks for your hard work, and good luck in your future endeavours!
>
>
>
> On Thu, Mar 28, 2013 at 7:30 AM, Anis KADRI wrote:
>
>> Thanks for your contributio
thanks for your hard work, and good luck in your future endeavours!
On Thu, Mar 28, 2013 at 7:30 AM, Anis KADRI wrote:
> Thanks for your contributions and good luck to you Markus!
>
>
> On Thu, Mar 28, 2013 at 7:21 AM, Leutwyler, Markus
> wrote:
>
> > Today is my last day of work at HP as my R
We create branch when we decide to cut a release. This is the cut off for
features.
At that point, ALL commits continue on master, however, any regression
fixes we want are cherry picked into release branches.
This way, there is no confusion for contributors. All work is always done
on master,
Why aren't we merging them again? I don't remember the reasoning for that.
I'll cherry pick the changes into master today, although I don't remember
us deciding on not merging when we do a release. This seems kind-of weird.
On Mar 28, 2013 6:04 AM, "Braden Shepherdson" wrote:
> I think I saw a b
Thanks for your contributions and good luck to you Markus!
On Thu, Mar 28, 2013 at 7:21 AM, Leutwyler, Markus
wrote:
> Today is my last day of work at HP as my Role in Developer Relations here
> in Europe is ending this month.
> I'm in the process of moving stewardship of Phonegap/Cordova for (O
Yeah - if they require a call to exec(), then they have to be async.
On Thu, Mar 28, 2013 at 8:29 AM, Simon MacDonald
wrote:
> Yeah, I too think they could easily be sync methods. The only thing that
> I'd be concerned about is if there still is a limitation on iOS where it
> can't produce sync
Today is my last day of work at HP as my Role in Developer Relations here in
Europe is ending this month.
I'm in the process of moving stewardship of Phonegap/Cordova for (Open) webOS
to someone at LG.
Glad to have been part and to have the chance to contribute to such an
important Open Source
I think I saw a bunch of git commit messages go by that were committing
things to 2.6.x.
Remember that the intended flow is that things get committed to master and
then cherry-picked into 2.6.x if they're critical fixes.
We WILL NOT ever merge master and 2.6.x in either direction, so commits
that
Yeah, I too think they could easily be sync methods. The only thing that
I'd be concerned about is if there still is a limitation on iOS where it
can't produce sync results. If that is the case I'd stay with a consistent
API over sync returns.
Simon Mac Donald
http://hi.im/simonmacdonald
On Wed
24 matches
Mail list logo
