Re: too long to package a release?

[Michael Brooks]

Before we move forward, I have a few questions about the "no master"
approach.

There is *no* master branch, so that community-driven pull requests will be
> forced to think about which branch to request against.


- Andrew, can you cite other projects that do not use a master branch?

- On Github, you must have a default branch. If not master, it must be
something else. So, users are not forced to think about the branch to send
a pull request again... they will likely just use the default.

- Why is the "stable" branch not just "master"?

Thanks,
Michael

On Wed, Jan 23, 2013 at 11:25 AM, Brian LeRoux  wrote:

> I'm liking it. Start in 2.5?
>
> On Wed, Jan 23, 2013 at 1:19 PM, Filip Maj  wrote:
> > Looks great Andrew!
> >
> > If everyone's on board, how are we going to test run this? Flip a switch
> > at a certain point, give it a shot with one repo for one RC?
> >
> > On 1/22/13 12:29 PM, "Andrew Grieve"  wrote:
> >
> >>Braden, you're right. I've now done some local playing around in git, and
> >>have an updated proposal that uses merges instead of deleting branches.
> >>PTAL:
> >>
> >>Cordova repositories have three main branches:
> >>1. stable
> >>2. next
> >>3. dev
> >>
> >>Topic branches also exist for collaborating on features, or for
> >>code-review
> >>purposes.
> >>
> >>There is *no* master branch, so that community-driven pull requests will
> >>be
> >>forced to think about which branch to request against.
> >>
> >>1. The "stable" branch.
> >> - Sits at the latest stable release of cordova
> >> - This changes only when doing fast-forward merges from "next"
> >>
> >>2. The "next" branch.
> >> - This branch is used only when in the process of doing a release.
> >> - All tags (both stable and RC) are done on this branch.
> >> - All release-candidate bug-fixes are done on this branch.
> >>
> >>3. The "dev" branch.
> >>  - This is where non-release-candidate commits are done
> >>  - This is where topic-branches are merged into.
> >>
> >>Cutting a release:
> >>1. git checkout next && git merge --ff-only dev
> >>2. Test test test!
> >>3. Fix bugs by committing them directly to "next" and then doing a non-ff
> >>merge of next into dev
> >>4. Tag release candidate
> >>5. Repeat steps 2-4 as necessary
> >>6. Tag the release
> >>7. Create distribution .zip file
> >>8. Test one last time using the dist files
> >>9. git checkout stable && git merge --ff-only next
> >>
> >>
> >>
> >>On Tue, Jan 22, 2013 at 1:59 PM, Braden Shepherdson
> >>wrote:
> >>
> >>> I think deleting and recreating branches with the same name can cause
> >>> badness in git[1] because of remotes. It's not really the same branch
> in
> >>> terms of commits, and git thinks that your old stable and the new
> stable
> >>> differ by all of each of their commits. Tags can be moved arbitrarily,
> >>>so I
> >>> think stable makes sense as a tag. I'm not sure about how best to
> handle
> >>> next.
> >>>
> >>> [1]
> >>>
> >>>
> http://stackoverflow.com/questions/11844581/git-delete-and-recreate-branc
> >>>h
> >>>
> >>>
> >>> On Tue, Jan 22, 2013 at 11:31 AM, Andrew Grieve  >>> >wrote:
> >>>
> >>> > Michal's attending hackathons for the week, and I'm not sure we need
> >>>to
> >>> do
> >>> > a hang-out for this, as I think we really are quite close to
> resolving
> >>> > this. I'd really like to resolve this ASAP so that we don't need to
> >>>have
> >>> a
> >>> > code-freeze for this release.
> >>> >
> >>> > Here's a proposal:
> >>> >
> >>> > Cordova repositories have three main branches:
> >>> > 1. stable
> >>> > 2. next
> >>> > 3. dev
> >>> >
> >>> > Topic branches also exist for collaborating on features, or for
> >>> code-review
> >>> > purposes.
> >>> >
> >>> > There is *no* master branch, so that community-driven pull requests
> >>>will
> >>> be
> >>> > forced to think about which branch to request against.
> >>> >
> >>> > 1. The "stable" branch.
> >>> >  - Sits at the latest stable release of cordova
> >>> >  - No one ever commits to the "stable" branch. It exists only as a
> >>> > short-cut for checking out the latest stable tag.
> >>> >
> >>> > 2. The "next" branch.
> >>> >  - This branch exists only when in the process of doing a release.
> >>> >  - All tags (both stable and RC) are done on this branch.
> >>> >  - When a stable tag is done:
> >>> > - The existing "stable" branch is deleted
> >>> > - A new "stable" branch is created from "next".
> >>> > - The "next" branch is deleted.
> >>> >
> >>> > 3. The "dev" branch.
> >>> >   - This is where all commits are done
> >>> >   - This is where topic-branches are merged into.
> >>> >
> >>> > Cutting a release:
> >>> > 1. Create "next" from the HEAD of "dev"
> >>> > 2. Test test test!
> >>> > 3. Fix bugs by committing them to "dev" and then cherry-picking them
> >>>into
> >>> > "next"
> >>> > 4. Tag release candidate
> >>> > 5. Repeat steps 2-4 as necessary
> >>> > 6. Tag the release
> >>> > 7. Create distribution .zip file
> >>> > 8. Test one last time using the dist files
> >>> > 

Re: Getting Started

[Michael Brooks]

Welcome to the community Matt, it's awesome to hear from you again!

I imagine Becky would be excited to have your support. Feel free to chime
in on the thread.

Michael

On Wed, Jan 23, 2013 at 11:04 AM, Matt Lantz  wrote:

> Hey all,
>
> Sorry I've yet to introduce myself, I'm Matt Lantz a former RIM guy who
> worked with Gord and learned some of the details of Cordova from him. I've
> met a couple other folks on the team, and I'm looking to get back into the
> project. I made a couple small contributions under the tutelage of Gord but
> I'm looking to do more.
>
> In response to the documentation discussion that Brian and Becky recently
> commented on I would be delighted to help out with that part of the project
> if I can. I agree that the audience looking to utilize Cordova and its
> children is broad and I myself have a hard time keeping up with you guys.
>
> Thanks,
>
> Matt
>
>
>

[jira] [Resolved] (CB-2266) Tag Docs

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-2266.


Resolution: Fixed

Tagged 2.4.0rc1 [Commit 
f52c21|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=f52c2140328e702b3015ba5af44b0da92bb5c941]

> Tag Docs
> 
>
> Key: CB-2266
> URL: https://issues.apache.org/jira/browse/CB-2266
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Docs
>Reporter: Filip Maj
>    Assignee: Michael Brooks
> Fix For: 2.4.0
>
>
> After all platforms have been tagged, the docs can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Intro + First contribution

[Michael Brooks]

Welcome Yaniv!

Another opportunity for contribution is to review and revise our
ContributorWorkflow [1] article. It's often hard for us to review our
getting started documentation, because it's easy to forget the steps
involved. Having new contributors edit these articles and fill in the
missing gaps is extremely helpful.

[1] http://wiki.apache.org/cordova/ContributorWorkflow

Michael

On Mon, Jan 21, 2013 at 7:34 AM, Andrew Grieve  wrote:

> Hi Yaniv!
>
> Very excited to see new contributors! I think what you propose sounds
> great.
>
> If you haven't seen it yet, be sure to give this wiki page a read through:
> http://wiki.apache.org/cordova/ContributorWorkflow
>
> You'll need to sign an ICLA before committing any code.
>
> Had a look at your commits, and they seem good to me :). You're right in
> that the first step is to create JIRA issues for them, and mark the as "fix
> for 2.4" so that we can use them for release notes and tracking purposes.
>
> Andrew
>
>
>
>
>
>
> On Mon, Jan 21, 2013 at 4:41 AM, Yaniv De Ridder 
> wrote:
>
> > Hi,
> >
> > I would like to contribute to Cordova, more precisely to the iOS side of
> > it but first of all let me present myself.
> >
> > I'm a computer scientist at Adobe in the Experience Design team mainly
> > working on seed-products and researches. For more information you can
> look
> > at my linkedIn profile: http://www.linkedin.com/in/yderidder.
> >
> > Recently for one of our project, we extensively used Cordova to produce
> an
> > iOS app using web technologies and we ended up writing a bunch of native
> > plugins which I think would be valuable contributions.
> >
> > I already started to factor out some of the enhancements we did into a
> > fork of the cordova-ios github repo which you can find here:
> > https://github.com/yderidde/cordova-ios/
> >
> > My first contribution is related to the splash screen in iOS:
> >
> > -  Splash-Screen Fade IN/OUT feature
> > The first commit is about adding the ability to fade in and out the
> splash
> > screen. It uses 2 new properties in the xml config file:
> > 'FadeSplashScreen' a boolean to enable or disable the fading.
> > 'FadeSplashScreenDuration' a float, which is the duration of the fade in
> > seconds.
> >
> >
> https://github.com/yderidde/cordova-ios/commit/42ab472a29efd5f3568d83252357dbfabc0c3575
> >
> > - Cordova splash-screen enhancement with smooth iOS-like rotation on
> > re-orientation
> > The second commit is about nice and smooth rotation transition while the
> > splash is still visible and reorienting the device. Before it was
> abruptly
> > switching the image when the orientation changed which was not very
> > iOS-like. I basically re-wrote the entire routine which to me looks
> simpler
> > and 'just works'. This said, the previous routine seemed complex to me
> and
> > I couldn't really understand why. So I hope that I didn't introduce a
> > regression here.
> >
> >
> https://github.com/yderidde/cordova-ios/commit/8e0069d2fb689d11eed7d1e3b6b62a0a2b9c6b30
> >
> > While I'm at it, I can also probably look at these 2 issues related to
> the
> > splash screen in iOS:
> > https://issues.apache.org/jira/browse/CB-2220
> > https://issues.apache.org/jira/browse/CB-1505
> >
> > ---
> > I believe at this point, the next step would be to open an issue for each
> > on Jira ? and start getting some feedback from you guys before I do a
> pull
> > request.
> >
> >
> > Cheers,
> > /yaniv
> >
>

Re: Can we talk about large features before they arrive in master?

[Michael Brooks]

>
> Here's a draft for a new "Committing Your Own Changes:" section on
> http://wiki.apache.org/cordova/CommitterWorkflow


Great draft Andrew. It reads well.

Outsider observation/note: probably useful for step 4 to tie into the CI -
> getting the pull request to notify Fil's CI project.


It would be nice to run a smoke test against the CI server. I'm unsure
whether medic currently supports branches or only runs against master.

On Tue, Jan 22, 2013 at 10:57 AM, Andrew Lunny  wrote:

> Outsider observation/note: probably useful for step 4 to tie into the CI -
> getting the pull request to notify Fil's CI project.
>
> On 22 January 2013 10:53, Andrew Grieve  wrote:
>
> > Here's a draft for a new "Committing Your Own Changes:" section on
> > http://wiki.apache.org/cordova/CommitterWorkflow
> >
> > Step 1: Mail the Mailing-list
> >   - This is required if:
> > - Your change will add/remove/change any public Cordova APIs.
> > - You suspect that your change has a chance of being controversial
> > - You would like feedback before you begin.
> >
> > When possible, try to phrase things in the form of a proposal. If no one
> > objects (within a workday or two), then consider yourself to have Lazy
> > Consensus  >.
> >
> > Step 2: Ensure there is a JIRA issue.
> >   - JIRA issues are used for both new features and for bugs.
> >   - The "Fix For" field is used for the purpose of Release Notes.
> >   - The issues are also used to track which commits / topic branches are
> > related to them.
> >
> > Step 3: Create a topic branch
> >   - Using a public topic branch is necessary only when either:
> >  1. you would like to collaborate on the feature
> >  2. you would like feedback on your code before committing
> >   - For small bugfixes, public topic branches are not required.
> >   - Note: You should never rebase a public topic branch!
> >
> > Step 4: Ask for a code review
> >   - If you are using a public topic branch, then you should ask for a
> code
> > review when you consider it to be complete.
> >   - For now, use a github pull request. Soon, use reviews.apache.org.
> >   - Email the ML so that anyone who is available can have a look at your
> > code. If you have someone in particular that you would like approval
> from,
> > be sure to add them in the To: of your email.
> >   - Again, sometimes this will end with a Lazy
> > Consensus
> > .
> >
> > Step 5: Merge your change
> >   - Once your topic branch is tested & working, it's time to merge it.
> Use
> > the following workflow:
> >
> > git checkout master
> > git pull apache master
> > git checkout topic_branch
> > git checkout -b to_be_merged
> > git rebase master -i
> > ...
> > git checkout master
> > git merge --ff-only to_be_merged
> > git push apache master
> > git branch -d to_be_merged
> > git branch -D topic_branch
> > git push apache :topic_branch
> >
> > The rebase -i step is your chance to clean up the commit messages and to
> > combine small commits when appropriate. For example:
> > Commit A: Implemented RockOn feature (CB-1234)
> > Commit B: Added tests for RockOn (CB-1234)
> > Commit C: Fixed RockOn not working with empty strings
> > Commit D: Renamed RockOn to JustRock
> > Commit E: Refactor MainFeature to make use of JustRock.
> >
> > In this case, it would be appropriate to combine commits A-D into a
> single
> > commit, or at least commits A & C. Having a smaller number of commits
> when
> > merging makes it easier for others to comprehend the diff commits, and
> also
> > makes it easier to roll-back commits should the need arise. For JS
> commits,
> > prefix the message with [platform] so that it's clear who should take
> > interest in the commit. For all commits, be sure to include the JIRA
> issue
> > number / URL.
> >
> >
> > On Tue, Jan 22, 2013 at 1:19 PM, Braden Shepherdson  > >wrote:
> >
> > > Code reviews will generally sound good to Googlers, so long as we can
> > keep
> > > the turnaround down. It definitely keeps our code quality high on
> > internal
> > > projects, even if it is sometimes a pain to have to wait for a response
> > and
> > > do your own reviews. I've asked Michal and Andrew for over-the-shoulder
> > iOS
> > > reviews in the past, since I'm new to that platform.
> > >
> > > I also want to apologize for the trouble with the ArrayBuffers on
> > Android.
> > > I was running into the bug with navigating in mobile-spec causing
> > > deviceready not to fire, and had just changed my start page to the
> binary
> > > echo test Michal wrote. It started working, so I cleaned up my
> debugging
> > > and pushed. That was premature, since I broke some of the tests and
> > hadn't
> > > run the automatic tests. Gomen nasai.
> > >
> > >
> > > Braden
> > >
> > > On Tue, Jan 22, 2013 at 10:59 AM, Andrew Grieve  > > >wrote:
> > >
> > > > ReviewBoard seems like a great fit to me! Let's try it 

[jira] [Resolved] (CB-2246) Tag Hello World App

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-2246.


Resolution: Fixed

Tagged [commit 
c930c1|https://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;a=commit;h=c930c1e6522cd8d0ba2a8634153b18845aae5f2d]

> Tag Hello World App
> ---
>
> Key: CB-2246
> URL: https://issues.apache.org/jira/browse/CB-2246
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: App Hello World
>Reporter: Filip Maj
>    Assignee: Michael Brooks
> Fix For: 2.4.0
>
>
> Tag sample application so that each platform can cut a copy of the 
> application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: docs on cordova.apache.org

[Michael Brooks]

>
> I've got Jenkins running locally, pulling from cordova-docs, polling daily,
> and generating the docs. But the SVN Publisher doesn't seem to work:
> https://wiki.jenkins-ci.org/display/JENKINS/SVN+Publisher (I tested it on
> another SVN repo, not Apache's) -- reports success but nothing is uploaded.
> This could be a solution in the interim if I could get the publisher to


Well, it's an interesting experiment. I don't have the time to look into it
now, but
as I said I'm working to free up February for the documentation update.
I'll pick
your brain about the Jenkins stuff then. Thanks for looking into it.

which by the way, the whole tree right now is over
> 300MB. en/edge right now is only 7MB


That's not a big concern. The rewrite of the documentation will only
version the
latest. This will make internationalization contributions more confusing,
since
most update older version of Apache Cordova, but we can solve that with...
documentation.

On Wed, Jan 16, 2013 at 10:04 AM, Shazron  wrote:

> I've got Jenkins running locally, pulling from cordova-docs, polling daily,
> and generating the docs. But the SVN Publisher doesn't seem to work:
> https://wiki.jenkins-ci.org/display/JENKINS/SVN+Publisher (I tested it on
> another SVN repo, not Apache's) -- reports success but nothing is uploaded.
> This could be a solution in the interim if I could get the publisher to
> actually publish -- which by the way, the whole tree right now is over
> 300MB. en/edge right now is only 7MB.
>
>
> On Mon, Jan 14, 2013 at 9:32 AM, Shazron  wrote:
>
> > I agree with Ross that it should be on Apache's servers and not somewhere
> > else (like Amazon S3). At most some dev could locally install Jenkins and
> > run a CI server with a script that can auto update the SVN repo (using
> > their creds), or something - until we can get a permanent solution
> >
> >
> > On Mon, Jan 14, 2013 at 9:22 AM, Michael Brooks <
> mich...@michaelbrooks.ca>wrote:
> >
> >> @Andrew I was thinking S3 so that a service can auto-update on each
> >> commit.
> >> From Yohei's experience with the cordova.apache.org SVN setup, it looks
> >> like automating that is a headache.
> >>
> >> Michael
> >>
> >> On Mon, Jan 14, 2013 at 9:16 AM, Andrew Grieve 
> >> wrote:
> >>
> >> > cordova.io is a bunch of redirects. Do you mean to have
> >> > docs.cordova.ioredirect to
> >> > cordova.apache.org/docs (or something similar)
> >> >
> >> >
> >> > On Mon, Jan 14, 2013 at 12:13 PM, Michael Brooks
> >> > wrote:
> >> >
> >> > > Hi Marcel,
> >> > >
> >> > > I've got this one my roadmap of tasks.
> >> > >
> >> > > The short-term goal is to have http://docs.cordova.io host our
> >> > > documentation and we'll link to it off http://cordova.io.
> >> > >
> >> > > The longer-term goal is to have the generator and possibly templates
> >> > > decoupled from the documentation. At that time, we'll redesign the
> >> > > http://docs.cordova.io to use the http://cordova.io site design.
> >> > >
> >> > > My plan is to start this work on February 1st and have it completed
> >> for
> >> > the
> >> > > next board report.
> >> > >
> >> > > Michael
> >> > >
> >> > > On Mon, Jan 14, 2013 at 8:52 AM, Ross Gardler <
> >> > rgard...@opendirective.com
> >> > > >wrote:
> >> > >
> >> > > > It not only makes sense I would consider it a priority. Having the
> >> only
> >> > > > source of docs on a third party website is a no-go as far as I'm
> >> > > concerned.
> >> > > > I raised this issue during incubation and was assured it was a
> >> > > transitional
> >> > > > thing.
> >> > > >
> >> > > > Ross
> >> > > >
> >> > > > Sent from a mobile device, please excuse mistakes and brevity
> >> > > > On 14 Jan 2013 08:44, "Marcel Kinard"  wrote:
> >> > > >
> >> > > > > Would it make sense to host a copy of the docs on
> >> cordova.apache.org
> >> > ?
> >> > > > > Other Apache projects have their docs online at their
> >> apache.orgsite.
> >> > > > >
> >> > > > > A couple possibilities:
> >> > > > > 1) build the html files and zip them up, so a consumer needs to
> >> only
> >> > > > > download and unzip and point their browser at their local
> offline
> >> > copy.
> >> > > > > 2) build the html files and post them unpacked to
> >> > cordova.apache.orgso
> >> > > > > they can be browsed directly without a zip or src download.
> >> > > > >
> >> > > > > My initial suggestion is to do both: something like
> >> /docs/download to
> >> > > > hold
> >> > > > > the zip files and /docs/browse to have the tree starting with
> >> > > index.html.
> >> > > > >
> >> > > > > Or would it be better to host it in www.apache.org/dist/cordova
> ?
> >> > > > >
> >> > > > > I am willing to do the initial setup and load.
> >> > > > >
> >> > > > > Comments?
> >> > > > >
> >> > > > > -- Marcel Kinard
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> >
> >
>

Re: too long to package a release?

[Michael Brooks]

>
> My ideal here is to get to a point where there is something, whatever
> it is, that we want to denote as a release. That something should not
> require a whole bunch of coordination. There should be a working
> branch, whatever we call it, ready for a tag and nothing else on any
> arbitrary date to be considered a release. Does that make sense?


Now's my chance to loop back to the other discussion point of this thread.
Building a release should be automated and I'd like to propose that we
introduce another script:

./bin/dist 

I would go as far as I require any platform wanting to be included in a
release
to include the distribution script. For what it's worth, BlackBerry has had
this
script for over two years.

Ideally, we should also standardize how to install any dev environment
dependencies. In my mind, it would make sense to require a script similar to
the UNIX ./configure to install and/or verify any developer dependencies.

To do an Apache Cordova release, we following steps similar to:

Each platform
Checkout stable git branch
$ ./configure
$ ./bin/dist 
 Zip everything up

On Mon, Jan 14, 2013 at 2:34 PM, Brian LeRoux  wrote:

> I think its basically the same except cherry picking not necessary.
> (But I've been known to be very wrong so take that with a grain of
> salt!)
>
> You work on a Feature branch. It gets rolled into Dev as needed so
> others can merge / collaborate on said feature. When it feels right
> instead of merging a large set of potentially breaking commits to
> Unstable the dev working on said feature just merges that feature.
> This would require more responsibility for the committer to keep track
> of their feature branches which I could see as being more overhead.
>
> My ideal here is to get to a point where there is something, whatever
> it is, that we want to denote as a release. That something should not
> require a whole bunch of coordination. There should be a working
> branch, whatever we call it, ready for a tag and nothing else on any
> arbitrary date to be considered a release. Does that make sense?
>
>
>
> On Mon, Jan 14, 2013 at 2:18 PM, Andrew Grieve 
> wrote:
> > Could you elaborate on what the workflow would be if we merged only from
> > Feature branches?
> >
> > On Mon, Jan 14, 2013 at 5:14 PM, Brian LeRoux  wrote:
> >
> >> So, what if Canonical branches only received merges from Feature
> >> branches...?
> >>
> >> On Mon, Jan 14, 2013 at 2:02 PM, Andrew Grieve 
> >> wrote:
> >> > On Mon, Jan 14, 2013 at 4:54 PM, Filip Maj  wrote:
> >> >
> >> >>
> >> >> >But do Canonical branches merge into each other? I'm thinking no.
> >> >>
> >> >> My understanding:
> >> >>
> >> >> - work goes into feature branches
> >> >> - when contributor(s) deem feature is ready, merge into Unstable,
> which
> >> >> then gets vetted (test!)
> >> >> - at some point unstable merges into Next
> >> >> - when tagging, we merge Next into Stable and tag
> >> >>
> >> >
> >> > That's my understanding as well.
> >> >
> >> > The "At some point" part would be when we say "hey, let's start
> working
> >> on
> >> > cutting a release", which should align with the wiki's
> >> > RoadMap (which
> >> > targeted 2.3 for November, whoops!).
> >> >
> >> >
> >> >>
> >> >> Would be different for bug fixes or other maintenance-type commits
> too,
> >> >> ya? Those would be directly into Next.
> >> >>
> >> > It might cause headaches to commit bug-fixes into Next when it comes
> time
> >> > to merge Unstable -> Next.
> >> >
> >> >
> >> >>
> >> >> Finally, what about hot fixes / patch releases? Branch off the tag in
> >> >> Stable and put hot patch work into there?
> >> >>
> >> > Agree. I think the flow here should be to commit change to Unstable
> and
> >> > then cherry-pick it into a branch off the tag (when feasible).
> >>
>

Re: [FYI] call for cordova devs to participate in phonegap day event in july

[Michael Brooks]

Please come! Submit talks and meet the people using your code!

On Fri, Jan 11, 2013 at 3:46 PM, Brian LeRoux  wrote:

> http://goo.gl/fYW3J
>

Re: A little late butŠ welcome Marcel!

[Michael Brooks]

Welcome Marcel!

On Fri, Jan 11, 2013 at 4:03 PM, Filip Maj  wrote:

> Marcel got voted in as a committer and PMC member for Apache Cordova last
> week. Marcel did a ton of work on this project across a few platforms
> leading up to his voting in.
>
> Marcel: congratulations and thank you for all your efforts to date!
>
>

Re: docs on cordova.apache.org

[Michael Brooks]

@Andrew I was thinking S3 so that a service can auto-update on each commit.
>From Yohei's experience with the cordova.apache.org SVN setup, it looks
like automating that is a headache.

Michael

On Mon, Jan 14, 2013 at 9:16 AM, Andrew Grieve  wrote:

> cordova.io is a bunch of redirects. Do you mean to have
> docs.cordova.ioredirect to
> cordova.apache.org/docs (or something similar)
>
>
> On Mon, Jan 14, 2013 at 12:13 PM, Michael Brooks
> wrote:
>
> > Hi Marcel,
> >
> > I've got this one my roadmap of tasks.
> >
> > The short-term goal is to have http://docs.cordova.io host our
> > documentation and we'll link to it off http://cordova.io.
> >
> > The longer-term goal is to have the generator and possibly templates
> > decoupled from the documentation. At that time, we'll redesign the
> > http://docs.cordova.io to use the http://cordova.io site design.
> >
> > My plan is to start this work on February 1st and have it completed for
> the
> > next board report.
> >
> > Michael
> >
> > On Mon, Jan 14, 2013 at 8:52 AM, Ross Gardler <
> rgard...@opendirective.com
> > >wrote:
> >
> > > It not only makes sense I would consider it a priority. Having the only
> > > source of docs on a third party website is a no-go as far as I'm
> > concerned.
> > > I raised this issue during incubation and was assured it was a
> > transitional
> > > thing.
> > >
> > > Ross
> > >
> > > Sent from a mobile device, please excuse mistakes and brevity
> > > On 14 Jan 2013 08:44, "Marcel Kinard"  wrote:
> > >
> > > > Would it make sense to host a copy of the docs on cordova.apache.org
> ?
> > > > Other Apache projects have their docs online at their apache.orgsite.
> > > >
> > > > A couple possibilities:
> > > > 1) build the html files and zip them up, so a consumer needs to only
> > > > download and unzip and point their browser at their local offline
> copy.
> > > > 2) build the html files and post them unpacked to
> cordova.apache.orgso
> > > > they can be browsed directly without a zip or src download.
> > > >
> > > > My initial suggestion is to do both: something like /docs/download to
> > > hold
> > > > the zip files and /docs/browse to have the tree starting with
> > index.html.
> > > >
> > > > Or would it be better to host it in www.apache.org/dist/cordova?
> > > >
> > > > I am willing to do the initial setup and load.
> > > >
> > > > Comments?
> > > >
> > > > -- Marcel Kinard
> > > >
> > >
> >
>

Re: Regarding inAppPurchase functionality implementation

[Michael Brooks]

Hello Rajeev,

We encourage PhoneGap questions to be posted on the PhoneGap Google Groups
[1].

The Apache Cordova mailing list is more centered around contributing to
Apache Cordova and less around support.

Congrats on the big upgrade from 1.3.0-2.3.0. That's no small step. A quick
search shows that the PhoneGap Plugin Repository has an InApp Purchase
plugin [2] updated for Cordova/PhoneGap 2.2.0. In your above message, you
did not mention what platform you are using but typically "in app purchase"
is iOS terminology, so I'm guessing you're looking for the iOS plugin.

If you have any further questions, please post them to the PhoneGap Google
Groups [1]. You will find an active community there.

Cheers,
Michael

[1] https://groups.google.com/forum/?fromgroups#!forum/phonegap
[2]
https://github.com/phonegap/phonegap-plugins/tree/master/iOS/InAppPurchaseManager

On Mon, Jan 14, 2013 at 5:18 AM, Rajeev Kumar  wrote:

> Hello,
>
> " I hope you are doing great !"
>
> I have implemented the inAppPurchase functionality with phoneGap 1.3.0 and
> its working fine but last few days i have update the phoneGap 1.3.0 to
> Cordova 2.3.0 and also update all library and plugins but my inAppPurchase
> functionality not working so could you possible to provide the simple code
> of inAppPurchase that is help for me.
>
> Regards
> RAjeev.

Re: docs on cordova.apache.org

[Michael Brooks]

Hi Marcel,

I've got this one my roadmap of tasks.

The short-term goal is to have http://docs.cordova.io host our
documentation and we'll link to it off http://cordova.io.

The longer-term goal is to have the generator and possibly templates
decoupled from the documentation. At that time, we'll redesign the
http://docs.cordova.io to use the http://cordova.io site design.

My plan is to start this work on February 1st and have it completed for the
next board report.

Michael

On Mon, Jan 14, 2013 at 8:52 AM, Ross Gardler wrote:

> It not only makes sense I would consider it a priority. Having the only
> source of docs on a third party website is a no-go as far as I'm concerned.
> I raised this issue during incubation and was assured it was a transitional
> thing.
>
> Ross
>
> Sent from a mobile device, please excuse mistakes and brevity
> On 14 Jan 2013 08:44, "Marcel Kinard"  wrote:
>
> > Would it make sense to host a copy of the docs on cordova.apache.org?
> > Other Apache projects have their docs online at their apache.org site.
> >
> > A couple possibilities:
> > 1) build the html files and zip them up, so a consumer needs to only
> > download and unzip and point their browser at their local offline copy.
> > 2) build the html files and post them unpacked to cordova.apache.org so
> > they can be browsed directly without a zip or src download.
> >
> > My initial suggestion is to do both: something like /docs/download to
> hold
> > the zip files and /docs/browse to have the tree starting with index.html.
> >
> > Or would it be better to host it in www.apache.org/dist/cordova?
> >
> > I am willing to do the initial setup and load.
> >
> > Comments?
> >
> > -- Marcel Kinard
> >
>

Re: commit messages for newbies

[Michael Brooks]

Looks really good, nice work!

On Fri, Jan 11, 2013 at 9:59 AM, Marcel Kinard  wrote:

> Good points, Michael.
>
> Done. Please tweak further where desired. http://wiki.apache.org/**
> cordova/ContributorWorkflow<http://wiki.apache.org/cordova/ContributorWorkflow>
>
> -- Marcel
>
>
> On 1/10/2013 2:23 PM, Michael Brooks wrote:
>
>> @Marcel nice work, I agree we should add this to the wiki article.
>>
>> One note is that I believe you should have an empty line between the
>> summary and detailed body.
>>
>> The Pro Git Books [1] summaries the git messages templates as:
>>
>> Short (50 chars or less) summary of changes
>>
>> More detailed explanatory text, if necessary.  Wrap it to about 72
>> characters or so.  In some contexts, the first line is treated as the
>> subject of an email and the rest of the text as the body.  The blank
>> line separating the summary from the body is critical (unless you omit
>> the body entirely); tools like rebase can get confused if you run the
>> two together.
>>
>> Further paragraphs come after blank lines.
>>
>>   - Bullet points are okay, too
>>
>>   - Typically a hyphen or asterisk is used for the bullet, preceded by a
>> single space, with blank lines in between, but conventions vary here
>>
>>
>> @Josh
>>
>> I think short commit messages and multiple tiny commits are fine (and
>> good). For me, the most important part of the commit message is a
>> reference
>> to the issue that it is related to. For example, "[CB-1287] Rename such
>> and
>> such." The issue reference groups all of the tiny commits into a common
>> task.
>>
>> [1] 
>> http://git-scm.com/book/ch5-2.**html#Commit-Guidelines<http://git-scm.com/book/ch5-2.html#Commit-Guidelines>
>>
>>

[jira] [Assigned] (CB-2203) CordovaLib and upgrading instructions for iOS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks reassigned CB-2203:
--

Assignee: Shazron Abdullah  (was: Michael Brooks)

> CordovaLib and upgrading instructions for iOS
> -
>
> Key: CB-2203
> URL: https://issues.apache.org/jira/browse/CB-2203
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Docs
>Affects Versions: 2.3.0
>Reporter: Jacob Weber
>Assignee: Shazron Abdullah
>Priority: Minor
>
> In the "Upgrading Cordova iOS" guide, it seems to be assuming the old project 
> format, where CordovaLib was in a shared directory rather than in the 
> project's directory. As I understand it, this changed with issue #CB-1526.
> Step 1 says to extract Cordova to a permanent location. And there's nothing 
> in there about updating your project's copy of CordovaLib to the latest 
> version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Blog Points out Cordova's Weak Spots

[Michael Brooks]

It's a good article that's written in an honest and fair tone.

Personally, I've felt a lot of pain-points that he's mentioned. While
fixing UX / UI performance issues, I've often lost track of what I set out
to create - an app.

However, one important point that I continually keep in mind is that the
web has came an incredibly long way in a short-time. In the past two years
alone, we've seen web applications become incredibly rich. Yes, they aren't
on par with native applications but the gap is narrowing quickly. I see the
"native vs web" debate playing out similar to the "compiled vs interpreted"
language debate that happened six or seven years ago.

Michael

On Thu, Jan 10, 2013 at 12:31 PM, Michal Mocny  wrote:

> Not sure your analogy works as expected ;)
> http://www.youtube.com/watch?v=dmP_t4_lpzo
>
>
> On Thu, Jan 10, 2013 at 2:50 PM, Shazron  wrote:
>
> > Not to mention, UIWebView is hobbled with a slower engine. Sometimes we
> do
> > get a Michael Schumacher driving a Toyota Corolla, and it's a good
> > middle-of-the-pack effort, but there's no way he can overtake a Homer
> > Simpson in a Ferrari engine. That's why we are all here, trying to make
> the
> > WebView a Ferrari...
> >
> >
> > On Thu, Jan 10, 2013 at 10:41 AM, Brian LeRoux  wrote:
> >
> > > Articles like these are tricky b/c of the YMMV factor. Its very well
> > > proven that good apps, even completely native feeling apps, *can* be
> > > built but frankly not every developer is up to that task.
> > >
> > > It certainly isn't in our mandate to prescribe web development
> practices
> > > either.
> > >
> > >
> > > On Thu, Jan 10, 2013 at 10:29 AM, Andrew Grieve 
> > > wrote:
> > > >
> > >
> >
> http://engblog.polyvore.com/2012/12/web-developer-admits-objective-c-html.html?m=1
> > > >
> > > > I think I agree with the author. I do still believe the mobile web
> will
> > > be
> > > > better in the future though :)
> > >
> >
>

Re: collecting mobile-spec test results and generating reports

[Michael Brooks]

Great discussion point Marcel!

As Fil has mentioned, we've started some of this work and it aligns very
closely with your described solution.

At the moment, Medic is wired up to our device wall, but I see it extending
well beyond that. I would love to see the day where Apache Cordova
committers can `npm install -g cordova-medic` and run medic locally. As
commits are made to the Apache Cordova projects, your local devices will
automatically run mobile-spec against the latest changes and report back to
the CouchDB instance. In other words, a de-centralized continuous
integration service.

Michael

On Thu, Jan 10, 2013 at 9:58 AM, Filip Maj  wrote:

> Hey Marcel, I am working towards that continuous integration vision.
>
> github.com/filmaj/medic
>
> It is a node process that builds the latest commits coming into android,
> iOS + BlackBerry repos, pairs them with mobile-spec, scans for
> connected/nearby devices, and deploys the mobile-spec app to those
> devices. It modifies mobile-spec so that all test results are sent off to
> a couchdb server. There is a "dashboard" script you can run that is a
> little node server that aggregates test results from this couchdb server
> and displays. The dashboard is also live here:
>
> http://cordova.medic.jit.su/
>
>
> Currently the Adobe Vancouver office device wall has this setup running on
> it (actually, not at this EXACT time but hopefully be back online by
> tomorrow :) ). Very recently the gitpubsub service over at Apache went
> live (try running curl http://urd.zones.apache.org:2069/json) which
> broadcasts all git commits going into all apache git repos. I am in the
> process of wiring up medic to that new service to pick out cordova commits
> as-they-happen.
>
> The idea is, at least now, that this is a setup that we can distribute to
> almost anyone and have them submit tests to our centralized server. So, a
> mobile, distributed CI setup, if you will. It's a lot of fun to play with!
>
> The couchdb server at this point is an Adobe EC2 instance. I haven't set
> up any special permissions (I think it's still in Admin Party mode) so if
> we were to publicize that server I'd have to set it up so that, at the
> minimum, no one can delete test results :)
>
> Overall, though, I like your idea of the opt-in submission button. Would
> love to see that in mobile spec. Also I'd love feedback on medic!
>
> Cheers,
> Fil
>
> On 1/10/13 8:30 AM, "Marcel Kinard"  wrote:
>
> >Here is something I feel is important and I wanted to see what you think.
> >
> >Problem definition: Cordova is a bit unique in that it not only has to
> >deal with running on a large number of permutations of device models and
> >device OS's, but the testing is started manually by a large number of
> >people using devices in their desk drawer, it is very decentralized. My
> >fear is that there are invisible holes and dups in our testing at the
> >end of a release. Thus we are releasing code for environments we didn't
> >test, but perhaps could have tested. And are we really running both the
> >automatic and manual tests in mobile-spec, or just the automatic tests?
> >In a more generalized perspective, we don't have good visibility to what
> >environments on which tests ran, and visibility to test failures as we
> >evaluate release readiness, other than a few comments on the dev mailing
> >list.
> >
> >Proposed solution: mobile-spec is a reasonably good test suite. But the
> >test results never leave the device. So the suggestion is to add a
> >"Submit test results" button throughout mobile-spec (at each place where
> >test results are generated) that would be an opt-in mechanism to get the
> >pass/fail test results off the device. Included in the submission with
> >the test results would be a bit of metadata, such as the device make and
> >model and OS version, Cordova version, etc. The submission would get
> >posted to a centralized db somewhere. A web-based query could be run
> >against the db to list the submitted results, with the intention to
> >understand which environments have been tested for a particular Cordova
> >version, which tests ran, and which tests failed/succeeded.
> >
> >It should be opt-in instead of opt-out because we generally don't want
> >test results from a developer that is working on a new feature in the
> >middle of a dev cycle. The intent here is to capture tests from rc's and
> >similar as we approach the end of a release. It's about evaluating
> >release readiness. Maybe in the long term we want to evaluate release
> >readiness all the way through a release, but that's not the short-term
> >intention here.
> >
> >I love the vision of continuous integration test, and see this proposal
> >as a first step towards that.
> >
> >Start shooting holes: Reply with what you think. Before we dive into
> >where the db should be hosted and a wire protocol for the submission, at
> >a high level do you agree with the problem definition and do you have
> >any other ideas/comments on a

Re: commit messages for newbies

[Michael Brooks]

@Marcel nice work, I agree we should add this to the wiki article.

One note is that I believe you should have an empty line between the
summary and detailed body.

The Pro Git Books [1] summaries the git messages templates as:

Short (50 chars or less) summary of changes

More detailed explanatory text, if necessary.  Wrap it to about 72
characters or so.  In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body.  The blank
line separating the summary from the body is critical (unless you omit
the body entirely); tools like rebase can get confused if you run the
two together.

Further paragraphs come after blank lines.

 - Bullet points are okay, too

 - Typically a hyphen or asterisk is used for the bullet, preceded by a
   single space, with blank lines in between, but conventions vary here


@Josh

I think short commit messages and multiple tiny commits are fine (and
good). For me, the most important part of the commit message is a reference
to the issue that it is related to. For example, "[CB-1287] Rename such and
such." The issue reference groups all of the tiny commits into a common
task.

[1] http://git-scm.com/book/ch5-2.html#Commit-Guidelines

On Thu, Jan 10, 2013 at 9:11 AM, Josh Soref  wrote:

> Marcel wrote:
> > A note about commit messages: you are highly encouraged to describe your
> > commit with enough detail for someone else to understand it. In doing
> > so, your commit message can consist of multiple lines. However, it also
> > is highly encouraged that the first line of your commit message not
> > exceed 40 characters. This is because some of the tooling that sits on
> > top of git (such as the httpd apps that let you browse the repo) assume
> > that the first line is top-level summary that is 40 characters or less.
> > Thus there will be highlighting and truncating of the commit message
> > using these assumptions, and it will look weird if these assumptions are
> > not kept. For example, here is a good example of a commit message:
>
> What should a contributor do if they're sending a bunch of changes which
> they'd like someone else to fold/resummarize as the merger wishes?
>
> Note that I'm talking about sending dozens of tiny commits (I've probably
> sent hundreds at this point to Cordova in fact). While I appreciate (and
> really want) good commit messages for certain classes of things, if you
> make the overhead for me too high, I can assure you that there are other
> projects to which I can allocate my spare time instead.
>
> -
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>

Re: Iframe security

[Michael Brooks]

Good call Brian.

The PhoneGap wiki is meant to act as a staging ground for documentation
that could eventually make it's way into our officially supported Apache
Cordova documentation.

Michael

On Wed, Jan 9, 2013 at 1:55 PM, Brian LeRoux  wrote:

> Some of this could be re-purposed there:
> https://github.com/phonegap/phonegap/wiki/Platform-Security
>
> On Wed, Jan 9, 2013 at 1:41 PM, Michael Brooks 
> wrote:
> > Let's just create a parent section called "Security", with sub-articles
> of
> > "Domain Whitelist" and "iFrame Security" (or whatever we call the
> untrusted
> > content article).
> >
> > On Wed, Jan 9, 2013 at 6:01 AM, Andrew Grieve 
> wrote:
> >
> >> https://issues.apache.org/jira/browse/CB-2179
> >>
> >> On Tue, Jan 8, 2013 at 2:56 PM, Andrew Grieve 
> >> wrote:
> >>
> >> > Looking at docs.cordova.io, I'm thinking it might make sense to
> change
> >> > "Domain Whitelist Guide" -> "Security & Whitelist Guide" and then add
> a
> >> > section to it about the dangers of embedding untrusted content. SG?
> I'll
> >> > create a JIRA issue for it.
> >> >
> >>
>

[jira] [Commented] (CB-2179) Warn developers about including third-party content in their apps.

[Michael Brooks (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549043#comment-13549043
 ] 

Michael Brooks commented on CB-2179:


My vote would be to create a parent section called "Security", with 
sub-articles of "Domain Whitelist" and "iFrame Security" (or whatever we call 
the untrusted content article).

> Warn developers about including third-party content in their apps.
> --
>
> Key: CB-2179
> URL: https://issues.apache.org/jira/browse/CB-2179
> Project: Apache Cordova
>  Issue Type: Bug
>  Components: Docs
>Reporter: Andrew Grieve
>Assignee: Andrew Grieve
>Priority: Minor
> Fix For: 2.4.0
>
>
> We expose our native APIs to iframes as well as top-level content, so we 
> should warn against using iframes for third-party code.
> Might make sense to change "Domain Whitelist Guide" -> "Security & Whitelist 
> Guide" and then add a section to it about the dangers of embedding untrusted 
> content.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Iframe security

[Michael Brooks]

Let's just create a parent section called "Security", with sub-articles of
"Domain Whitelist" and "iFrame Security" (or whatever we call the untrusted
content article).

On Wed, Jan 9, 2013 at 6:01 AM, Andrew Grieve  wrote:

> https://issues.apache.org/jira/browse/CB-2179
>
> On Tue, Jan 8, 2013 at 2:56 PM, Andrew Grieve 
> wrote:
>
> > Looking at docs.cordova.io, I'm thinking it might make sense to change
> > "Domain Whitelist Guide" -> "Security & Whitelist Guide" and then add a
> > section to it about the dangers of embedding untrusted content. SG? I'll
> > create a JIRA issue for it.
> >
>

[jira] [Resolved] (CB-2151) Tag Docs

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-2151.


Resolution: Fixed

> Tag Docs
> 
>
> Key: CB-2151
> URL: https://issues.apache.org/jira/browse/CB-2151
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Docs
>Reporter: Filip Maj
>    Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> After all platforms have been tagged, the docs can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CB-2151) Tag Docs

[Michael Brooks (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543501#comment-13543501
 ] 

Michael Brooks commented on CB-2151:


[Commit 
af24b6ce1d1aa3a06001415664b942e7b7654744|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=af24b6ce1d1aa3a06001415664b942e7b7654744]

> Tag Docs
> 
>
> Key: CB-2151
> URL: https://issues.apache.org/jira/browse/CB-2151
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Docs
>Reporter: Filip Maj
>    Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> After all platforms have been tagged, the docs can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: 2.3.0 final?

[Michael Brooks]

Docs are done.

On Thu, Jan 3, 2013 at 7:06 PM, Shazron  wrote:

> iOS passes all mobile-spec tests. Tagged 2.3.0
>
>
> On Wed, Jan 2, 2013 at 5:06 PM, Filip Maj  wrote:
>
> > Just automated the task creation in a script. I think its better to have
> > this option below (where 8 people waste 10 seconds each) rather than to
> > have one person spend 30+ minutes every release cloning and renaming 40+
> > issues.
> >
> > On 1/2/13 5:00 PM, "Jesse"  wrote:
> >
> > >Can we stop creating tasks for updating the www if it has not changed?
> All
> > >of these items are invalid.
> > >Creating these tasks means that ~8 different people need to go and look
> at
> > >app-hello-world and decide whether it actually needs to be updated.
> > >
> > >
> > >
> > >On Wed, Jan 2, 2013 at 4:45 PM, Filip Maj  wrote:
> > >
> > >> The JIRa issues for tagging are now up.
> > >>
> > >> https://issues.apache.org/jira/browse/CB-2115
> > >>
> > >>
> > >> On 1/2/13 10:15 AM, "Steven Gill"  wrote:
> > >>
> > >> >Lets tag this week!
> > >> >
> > >> >On Sun, Dec 30, 2012 at 11:36 AM, Filip Maj  wrote:
> > >> >
> > >> >> Early JAN release it is! I went into holiday mode early :P
> > >> >>
> > >> >> On 12/20/12 12:35 PM, "Jesse MacFadyen" 
> > >> wrote:
> > >> >>
> > >> >> >Here's the chance to prove it doesn't take a week. Let's release
> > >>2.3.0
> > >> >>!
> > >> >> >Today!
> > >> >> >
> > >> >> >Cheers,
> > >> >> >  Jesse
> > >> >> >
> > >> >> >
> > >> >> >On 2012-12-19, at 12:05 PM, Jesse 
> wrote:
> > >> >> >
> > >> >> >I would like to push 2.3.0 out before the break as well, before
> the
> > >> >>end of
> > >> >> >the week.
> > >> >> >2.3.0 adds support for WP8, and while it IS currently available in
> > >> >>rc2, it
> > >> >> >would be nice if it was available as part of the download from
> > >> >> >phonegap.com,
> > >> >> >which means a release.  As it is, Microsoft and I will have
> several
> > >> >>blog
> > >> >> >posts and videos alluding to 2.3.0 + WP8 but no link to go get it.
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >On Wed, Dec 19, 2012 at 11:43 AM, Brian LeRoux 
> wrote:
> > >> >> >
> > >> >> >> Michael brought this up yesterday w/ the suggestion that we make
> > >> >> >> cutting a release even easier still by including a standard
> > >>./release
> > >> >> >> script (actually he suggested ./configure but I think that
> > >>convention
> > >> >> >> might come w/ unintended baggage).
> > >> >> >>
> > >> >> >> I'm not convinced the speed issue w/ cutting a release is the
> > >>actual
> > >> >> >> compile/compose we do today---but it would make the Coho tool
> > >> >> >> significantly dumber which would make it way easier for
> downstream
> > >> >> >> distributions to live w/ what we do.
> > >> >> >>
> > >> >> >> I'm realizing--this warrants a new thread---I'll kick that up.
> > >> >> >>
> > >> >> >> On Wed, Dec 19, 2012 at 10:38 AM, Joe Bowser  >
> > >> >>wrote:
> > >> >> >> > Actually, given that it takes us a week to actually do a
> > >>release, I
> > >> >> >> > don't think we can get the final release out by the end of the
> > >> >>week,
> > >> >> >> > even though it appears activity on the repositories is slowing
> > >> >>down.
> > >> >> >> > :S
> > >> >> >> >
> > >> >> >> > I'll have to agree to a January release.
> > >> >> >> >
> > >> >> >> > On Wed, Dec 19, 2012 at 10:14 AM, Filip Maj 
> > >>wrote:
> > >> >> >> >> It's getting awfully close to a break. I'm heading out on
> > >>vacation
> > >> >> >> >> tomorrow.
> > >> >> >> >>
> > >> >> >> >> How do people feel about letting rc2 simmer over the break
> and
> > >> >> >>releasing
> > >> >> >> >> 2.3 first thing January?
> > >> >> >> >>
> > >> >> >> >> On 12/19/12 10:10 AM, "Joe Bowser" 
> wrote:
> > >> >> >> >>
> > >> >> >> >>>Can we start tagging the release today?
> > >> >> >> >>>
> > >> >> >> >>>On Wed, Dec 19, 2012 at 6:33 AM, Marcel Kinard
> > >> >>
> > >> >> >> wrote:
> > >> >> >>  +1, FWIW. I'd like to see 2.3.0 out before the break.
> > >> >> >> 
> > >> >> >>  -- Marcel Kinard
> > >> >> >> 
> > >> >> >> 
> > >> >> >>  On 12/17/2012 1:25 PM, Joe Bowser wrote:
> > >> >> >> >
> > >> >> >> > Hey
> > >> >> >> >
> > >> >> >> > How about Wednesday/Thursday for tagging 2.3.0 final?  I
> > >>know
> > >> >> >>that we
> > >> >> >> > haven't fully released 2.3.0rc2, but I know that many, if
> > >>not
> > >> >>the
> > >> >> >> > majority of the committers are going to be on holiday at
> the
> > >> >>end
> > >> >> >>of
> > >> >> >> > this week and it would be good if we could get 2.3.0 out
> > >>before
> > >> >> >> break.
> > >> >> >> >
> > >> >> >> > Thoughts?
> > >> >> >> >
> > >> >> >> > Joe
> > >> >> >> 
> > >> >> >> 
> > >> >> >> >>
> > >> >> >>
> > >> >> >
> > >> >> >
> > >> >> >
> > >> >> >--
> > >> >> >@purplecabbage
> > >> >> >risingj.com
> > >> >>
> > >> >>
> > >>
> > >>
> > >
> > >
> > >--
> > >@purplecabbage
> > >risingj.com
> >
> >
>

Re: the great seperatino of concerns

[Michael Brooks]

@fil @dave, yes to both test suite and docs.

On Thu, Jan 3, 2013 at 5:09 PM, Dave Johnson wrote:

> @fil and docs too
>
> On Thursday, January 3, 2013, Filip Maj wrote:
>
> >
> > >In parallel, we'd look at  moving core plugins out into individual
> > >repos. We should take this slow, and start w/ something simple, like
> > >org.apache.cordova.geolocation (which will help us move Coho and
> > >Robson tools to make this transition transparent to the users
> > >downloading downstream distributions.)
> >
> > Just throwing this out there as it just occurred to me, but this also
> > implies that we are partitioning mobile-spec into discrete test suites
> > that will be the responsibility of the plugins to maintain moving
> forward,
> > yes?
> >
> >
>

[jira] [Commented] (CB-2125) Update JavaScript for webOS

[Michael Brooks (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543350#comment-13543350
 ] 

Michael Brooks commented on CB-2125:


[~hermwong], noticed [commit 
65fa7c69|http://git-wip-us.apache.org/repos/asf/cordova-webos/commit/65fa7c69] 
go in. Can this issue be closed?

> Update JavaScript for webOS
> ---
>
> Key: CB-2125
> URL: https://issues.apache.org/jira/browse/CB-2125
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: webOS
>Reporter: Filip Maj
>Assignee: Herm Wong
> Fix For: 2.3.0
>
>
> Update the cordova.js after CordovaJS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CB-2119) Tag Hello World App

[Michael Brooks (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543184#comment-13543184
 ] 

Michael Brooks commented on CB-2119:


[Commit 
95bb86b3edd0e8e6466d9c4ffd6687bbaeee4f7d|https://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;a=commit;h=95bb86b3edd0e8e6466d9c4ffd6687bbaeee4f7d]

> Tag Hello World App
> ---
>
> Key: CB-2119
> URL: https://issues.apache.org/jira/browse/CB-2119
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: App Hello World
>Reporter: Filip Maj
>    Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> Tag sample application so that each platform can cut a copy of the 
> application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CB-2119) Tag Hello World App

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-2119.


Resolution: Fixed

> Tag Hello World App
> ---
>
> Key: CB-2119
> URL: https://issues.apache.org/jira/browse/CB-2119
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: App Hello World
>Reporter: Filip Maj
>    Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> Tag sample application so that each platform can cut a copy of the 
> application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2104) Pull Request #41: Japanese 2.1.0 Translations

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2104:
---

Fix Version/s: (was: 2.1.0)
   2.3.0

> Pull Request #41: Japanese 2.1.0 Translations
> -
>
> Key: CB-2104
> URL: https://issues.apache.org/jira/browse/CB-2104
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Docs
>Affects Versions: 2.1.0
> Environment: https://github.com/apache/incubator-cordova-docs/pull/41
>Reporter: Keiko Oda
>Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> Github pull request #41
> Add Japanese 2.1.0 translations

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CB-2104) Pull Request #41: Japanese 2.1.0 Translations

[Michael Brooks (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542493#comment-13542493
 ] 

Michael Brooks commented on CB-2104:


What an awesome way to kick off 2013, thanks Keiko!

Merged pull request as [commit 
c988fa|https://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=commit;h=c988fa6a72b053a77a36b87740a6acea7502f3b0].

> Pull Request #41: Japanese 2.1.0 Translations
> -
>
> Key: CB-2104
> URL: https://issues.apache.org/jira/browse/CB-2104
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Docs
>Affects Versions: 2.1.0
> Environment: https://github.com/apache/incubator-cordova-docs/pull/41
>Reporter: Keiko Oda
>Assignee: Michael Brooks
>
> Github pull request #41
> Add Japanese 2.1.0 translations

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CB-2104) Pull Request #41: Japanese 2.1.0 Translations

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-2104.


   Resolution: Fixed
Fix Version/s: 2.1.0

> Pull Request #41: Japanese 2.1.0 Translations
> -
>
> Key: CB-2104
> URL: https://issues.apache.org/jira/browse/CB-2104
> Project: Apache Cordova
>  Issue Type: Improvement
>  Components: Docs
>Affects Versions: 2.1.0
> Environment: https://github.com/apache/incubator-cordova-docs/pull/41
>Reporter: Keiko Oda
>Assignee: Michael Brooks
> Fix For: 2.1.0
>
>
> Github pull request #41
> Add Japanese 2.1.0 translations

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Looking for feedback from the group

[Michael Brooks]

Great summary Dan!

Both of these additions pave the road for some incredibly useful features
for Ripple!

Michael

On Mon, Dec 17, 2012 at 12:45 PM, Dan Silivestru
wrote:

> Hi Cordova and Ripple communites,
>
> As some of you might know, we had a great hack session with some of the
> good folks at Adobe this past week in Whistler. I wanted to email the group
> here to update everyone on the progress made and to ask for comments /
> feedback.
>
> Please keep in mind that this is still in prototype stage and things will
> likely change based on feedback and future work.
>
> The work was primarily done on Ripple and geared towards the
> Cordovadeveloper crowd. The two features implemented are as follows:
>
> *Device Proxy*:
>
> Allowing both Ripple and a device running a new Ripple companion app to
> connect to a socket server (part of Ripple CLI). This will result in all
> api calls (such as the accelerometer api) made by the mobile app inside
> ripple to be proxied directly to the connected device running the companion
> app. Basically making it such that your application is running in ripple,
> but all data will be coming from the connected device. Here are links to
> the repos and branches involved.
>
> Ripple device proxy branch:
> https://github.com/tinyhippos/Ripple-UI/tree/device.proxy
> Ripple companion app: https://github.com/gtanner/ripple-companion
>
> *How to get this stuff running?*
>
> Pretty straight forward.
>
>- Get ripple setup
>
> git clone g...@github.com:tinyhippos/Ripple-UI.git
> cd Ripple-UI
> git checkout device.proxy
> ./configure
> jake
>
>- install the CLI (from the Ripple-UI dir)
>
> npm install -g .
> ripple
>
> OR
>
> ./bin/ripple
>
>- load ripple as unpacked extension into Chrome (if not using Hosted
>Ripple), more details here:
>
> https://github.com/tinyhippos/Ripple-UI/blob/next/README.md#running-as-a-chrome-extension
>- compile and install the companion app (if you want to play with Ripple
>Device Proxy)
>- Run the following command over a directory that contains your app
>
> ripple emulate --path 
>
>- Open http://localhost:4400 and enable Ripple (probably still best to
>use Chrome for now)
>- Open the Device Proxy ui panel
>- Pair the Ripple companion app with the socket serve
>
>
> *Hosted Ripple:*
>
> The feature removes Ripple's dependency on the Chrome Extension mechanism.
> It gets kicked off from the CLI and essentially acts as a
> man-in-the-middle. Allowing Ripple to run in most modern browsers (only
> tested on Firefox and Chrome so far).
>
> Ripple hosted branch:
> https://github.com/tinyhippos/Ripple-UI/tree/hosted.ripple
>
>
> *How to run?*
>
> To run a local app, just read this commit message:
>
> https://github.com/tinyhippos/Ripple-UI/commit/81ed4ef7770e22f411bae9fc69bf2d4efe547a14
> *
> *
> To run a remobe app, just read this commit message:
>
> https://github.com/tinyhippos/Ripple-UI/commit/6961052a01aa2550b2f5a4c234cc746ddc88d876
> *
> *
> Also, we spoof the userAgent header with hosted ripple to ensure we get
> proper mobile content from loaded sites. Commit with comments here:
>
> https://github.com/tinyhippos/Ripple-UI/commit/9a10a8833706bcdb54663b70bb5dbf7d7b887c8e
>
>
> *
> *
> Last by not least, Brian Higgins spent quite a bit of time on the Mobile
> Spec app for BB10 and managed to kill about 80+ failing specs. Figured this
> was a good time to introduce Brian to the group (cc'd here) :-)
>
> Really looking forward to people's comments / thoughts on these features
> and our approach.
>
> Thanks in advance,
>
> --
> Dan Silivestru
>

Re: happy birthday ross!

[Michael Brooks]

Happy Birthday Ross!

On Mon, Dec 10, 2012 at 1:10 PM, Ross Gardler wrote:

> Thanks
>
> Sent from my tablet
> On Dec 10, 2012 7:49 PM, "Brian LeRoux"  wrote:
>
> > =)
> >
>

[jira] [Resolved] (CB-1895) Tag 2.3.0-rc1

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-1895.


Resolution: Fixed

> Tag 2.3.0-rc1
> -
>
> Key: CB-1895
> URL: https://issues.apache.org/jira/browse/CB-1895
> Project: Apache Cordova
>  Issue Type: Task
>Affects Versions: 2.3.0
>        Reporter: Michael Brooks
>Assignee: Steve Gill
> Fix For: 2.3.0
>
>
> Parent issue to track the release steps.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CB-1927) Generate a Source Release

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-1927.


Resolution: Fixed

> Generate a Source Release
> -
>
> Key: CB-1927
> URL: https://issues.apache.org/jira/browse/CB-1927
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Coho
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Steve Gill
> Fix For: 2.3.0
>
>
> After all other sub-tasks have been completed, Coho can generate the source 
> release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CB-1984) Tag Hello World App

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks resolved CB-1984.


Resolution: Fixed

> Tag Hello World App
> ---
>
> Key: CB-1984
> URL: https://issues.apache.org/jira/browse/CB-1984
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: App Hello World
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>    Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> Tag sample application so that each platform can cut a copy of the 
> application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CB-1984) Tag Hello World App

[Michael Brooks (JIRA)]

[ 
https://issues.apache.org/jira/browse/CB-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13528378#comment-13528378
 ] 

Michael Brooks commented on CB-1984:


[Commit 
b6589f|https://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;a=commit;h=b6589fc079b3225301c278d9c0d331d3767b8f93]

> Tag Hello World App
> ---
>
> Key: CB-1984
> URL: https://issues.apache.org/jira/browse/CB-1984
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: App Hello World
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> Tag sample application so that each platform can cut a copy of the 
> application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Tagging 2.3.0rc2?

[Michael Brooks]

@Jesse I agree with you timeline.

@Joe Yep, let's get the ball rolling.

I've created JIRA issue CB-1982 to track our progress:

https://issues.apache.org/jira/browse/CB-1982

Go Go Go!

Michael

On Mon, Dec 10, 2012 at 12:32 PM, Joe Bowser  wrote:

> So, are we getting this ball rolling?
>
> On Fri, Dec 7, 2012 at 4:48 PM, Jesse  wrote:
> > +me
> >
> > Also, 2.3.0 final will be the last release of the year with everyone
> > hopefully enjoying some time off.
> > Many of the Adobe+Cordova committers will be otherwise occupied much
> > of next week, so it may be best to push the release of 2.3.0 to the
> > middle of the following week, on like the 18th or 19th
> >
> >
> >
> >
> >
> > On Fri, Dec 7, 2012 at 4:37 PM, Anis KADRI  wrote:
> >> I approve this message
> >>
> >>
> >> On Fri, Dec 7, 2012 at 3:28 PM, Brian LeRoux  wrote:
> >>
> >>> agree
> >>>
> >>> On Fri, Dec 7, 2012 at 1:38 PM, Simon MacDonald
> >>>  wrote:
> >>> > We doing that or going straight to 2.3.0 release? Personally I'd
> like to
> >>> > see a 2.3.0rc2 on Monday then if no fixes are checked in cut 2.3.0
> the
> >>> > following week.
> >>> >
> >>> > Simon Mac Donald
> >>> > http://hi.im/simonmacdonald
> >>>
> >
> >
> >
> > --
> > @purplecabbage
> > risingj.com
>

[jira] [Updated] (CB-2014) Generate a Source Release

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2014:
---

Summary: Generate a Source Release  (was: CLONE - Generate a Source Release)

> Generate a Source Release
> -
>
> Key: CB-2014
> URL: https://issues.apache.org/jira/browse/CB-2014
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Coho
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Steve Gill
> Fix For: 2.3.0
>
>
> After all other sub-tasks have been completed, Coho can generate the source 
> release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2013) Tag Mobile Spec

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2013:
---

Summary: Tag Mobile Spec  (was: CLONE - Tag Mobile Spec)

> Tag Mobile Spec
> ---
>
> Key: CB-2013
> URL: https://issues.apache.org/jira/browse/CB-2013
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: mobile-spec
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Shazron Abdullah
> Fix For: 2.3.0
>
>
> After all platforms have been tagged, mobile-spec can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2011) Tag WP7

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2011:
---

Summary: Tag WP7  (was: CLONE - Tag WP7)

> Tag WP7
> ---
>
> Key: CB-2011
> URL: https://issues.apache.org/jira/browse/CB-2011
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: WP7
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Jesse MacFadyen
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2012) Tag Docs

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2012:
---

Summary: Tag Docs  (was: CLONE - Tag Docs)

> Tag Docs
> 
>
> Key: CB-2012
> URL: https://issues.apache.org/jira/browse/CB-2012
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Docs
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>    Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> After all platforms have been tagged, the docs can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2009) Tag Tizen

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2009:
---

Summary: Tag Tizen  (was: CLONE - Tag Tizen)

> Tag Tizen
> -
>
> Key: CB-2009
> URL: https://issues.apache.org/jira/browse/CB-2009
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Tizen
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2010) Tag webOS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2010:
---

Summary: Tag webOS  (was: CLONE - Tag webOS)

> Tag webOS
> -
>
> Key: CB-2010
> URL: https://issues.apache.org/jira/browse/CB-2010
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: webOS
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Herm Wong
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2008) Tag Qt

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2008:
---

Summary: Tag Qt  (was: CLONE - Tag Qt)

> Tag Qt
> --
>
> Key: CB-2008
> URL: https://issues.apache.org/jira/browse/CB-2008
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Qt
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2006) Tag iOS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2006:
---

Summary: Tag iOS  (was: CLONE - Tag iOS)

> Tag iOS
> ---
>
> Key: CB-2006
> URL: https://issues.apache.org/jira/browse/CB-2006
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: iOS
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Shazron Abdullah
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2007) Tag Mac

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2007:
---

Summary: Tag Mac  (was: CLONE - Tag Mac)

> Tag Mac
> ---
>
> Key: CB-2007
> URL: https://issues.apache.org/jira/browse/CB-2007
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Mac
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Shazron Abdullah
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2005) Tag BlackBerry

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2005:
---

Description: After updating the JavaScript and sample application, the 
release can be tagged.  (was: After updating the JavaScript and sample 
application, the release can be tagged as 2.2.0rc1)
Summary: Tag BlackBerry  (was: CLONE - Tag BlackBerry)

> Tag BlackBerry
> --
>
> Key: CB-2005
> URL: https://issues.apache.org/jira/browse/CB-2005
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: BlackBerry
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Tim Kim
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2004) Tag Bada

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2004:
---

Description: After updating the JavaScript and sample application, the 
release can be tagged.  (was: After updating the JavaScript and sample 
application, the release can be tagged as 2.2.0rc1)
Summary: Tag Bada  (was: CLONE - Tag Bada)

> Tag Bada
> 
>
> Key: CB-2004
> URL: https://issues.apache.org/jira/browse/CB-2004
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Bada
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2003) Tag Android

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2003:
---

Description: After updating the JavaScript and sample application, the 
release can be tagged.  (was: After updating the JavaScript and sample 
application, the release can be tagged as 2.2.0rc1)

> Tag Android
> ---
>
> Key: CB-2003
> URL: https://issues.apache.org/jira/browse/CB-2003
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Android
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Simon MacDonald
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2002) Update www/ Application for WP7

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2002:
---

Summary: Update www/ Application for WP7  (was: CLONE - Update www/ 
Application for WP7)

> Update www/ Application for WP7
> ---
>
> Key: CB-2002
> URL: https://issues.apache.org/jira/browse/CB-2002
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: WP7
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Jesse MacFadyen
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2001) Update www/ Application for webOS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2001:
---

Summary: Update www/ Application for webOS  (was: CLONE - Update www/ 
Application for webOS)

> Update www/ Application for webOS
> -
>
> Key: CB-2001
> URL: https://issues.apache.org/jira/browse/CB-2001
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: webOS
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Herm Wong
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2003) Tag Android

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2003:
---

Summary: Tag Android  (was: CLONE - Tag Android)

> Tag Android
> ---
>
> Key: CB-2003
> URL: https://issues.apache.org/jira/browse/CB-2003
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Android
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Simon MacDonald
> Fix For: 2.3.0
>
>
> After updating the JavaScript and sample application, the release can be 
> tagged as 2.2.0rc1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1998) Update www/ Application for Mac

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1998:
---

Summary: Update www/ Application for Mac  (was: CLONE - Update www/ 
Application for Mac)

> Update www/ Application for Mac
> ---
>
> Key: CB-1998
> URL: https://issues.apache.org/jira/browse/CB-1998
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Mac
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Shazron Abdullah
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1999) Update www/ Application for Qt

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1999:
---

Summary: Update www/ Application for Qt  (was: CLONE - Update www/ 
Application for Qt)

> Update www/ Application for Qt
> --
>
> Key: CB-1999
> URL: https://issues.apache.org/jira/browse/CB-1999
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Qt
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-2000) Update www/ Application for Tizen

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-2000:
---

Summary: Update www/ Application for Tizen  (was: CLONE - Update www/ 
Application for Tizen)

> Update www/ Application for Tizen
> -
>
> Key: CB-2000
> URL: https://issues.apache.org/jira/browse/CB-2000
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Tizen
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1995) Update www/ Application for Bada

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1995:
---

Summary: Update www/ Application for Bada  (was: CLONE - Update www/ 
Application for Bada)

> Update www/ Application for Bada
> 
>
> Key: CB-1995
> URL: https://issues.apache.org/jira/browse/CB-1995
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Bada
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1996) Update www/ Application for BlackBerry

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1996:
---

Summary: Update www/ Application for BlackBerry  (was: CLONE - Update www/ 
Application for BlackBerry)

> Update www/ Application for BlackBerry
> --
>
> Key: CB-1996
> URL: https://issues.apache.org/jira/browse/CB-1996
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: BlackBerry
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Tim Kim
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1997) Update www/ Application for iOS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1997:
---

Summary: Update www/ Application for iOS  (was: CLONE - Update www/ 
Application for iOS)

> Update www/ Application for iOS
> ---
>
> Key: CB-1997
> URL: https://issues.apache.org/jira/browse/CB-1997
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: iOS
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Shazron Abdullah
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1993) Update JavaScript for WP7

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1993:
---

Summary: Update JavaScript for WP7  (was: CLONE - Update JavaScript for WP7)

> Update JavaScript for WP7
> -
>
> Key: CB-1993
> URL: https://issues.apache.org/jira/browse/CB-1993
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: WP7
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Jesse MacFadyen
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1994) Update www/ Application for Android

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1994:
---

Summary: Update www/ Application for Android  (was: CLONE - Update www/ 
Application for Android)

> Update www/ Application for Android
> ---
>
> Key: CB-1994
> URL: https://issues.apache.org/jira/browse/CB-1994
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Android
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Joe Bowser
> Fix For: 2.3.0
>
>
> Update the www/ sample application after App-Hello-World has been tagged.
> *IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
> {{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1992) Update JavaScript for webOS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1992:
---

Summary: Update JavaScript for webOS  (was: CLONE - Update JavaScript for 
webOS)

> Update JavaScript for webOS
> ---
>
> Key: CB-1992
> URL: https://issues.apache.org/jira/browse/CB-1992
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: webOS
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Markus Leutwyler
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1990) Update JavaScript for Qt

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1990:
---

Summary: Update JavaScript for Qt  (was: CLONE - Update JavaScript for Qt)

> Update JavaScript for Qt
> 
>
> Key: CB-1990
> URL: https://issues.apache.org/jira/browse/CB-1990
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Qt
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1991) Update JavaScript for Tizen

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1991:
---

Summary: Update JavaScript for Tizen  (was: CLONE - Update JavaScript for 
Tizen)

> Update JavaScript for Tizen
> ---
>
> Key: CB-1991
> URL: https://issues.apache.org/jira/browse/CB-1991
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Tizen
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1989) Update JavaScript for Mac

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1989:
---

Summary: Update JavaScript for Mac  (was: CLONE - Update JavaScript for Mac)

> Update JavaScript for Mac
> -
>
> Key: CB-1989
> URL: https://issues.apache.org/jira/browse/CB-1989
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Mac
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Shazron Abdullah
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1988) Update JavaScript for iOS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1988:
---

Summary: Update JavaScript for iOS  (was: CLONE - Update JavaScript for iOS)

> Update JavaScript for iOS
> -
>
> Key: CB-1988
> URL: https://issues.apache.org/jira/browse/CB-1988
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: iOS
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Shazron Abdullah
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1987) Update JavaScript for BlackBerry

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1987:
---

Summary: Update JavaScript for BlackBerry  (was: CLONE - Update JavaScript 
for BlackBerry)

> Update JavaScript for BlackBerry
> 
>
> Key: CB-1987
> URL: https://issues.apache.org/jira/browse/CB-1987
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: BlackBerry
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Tim Kim
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1986) Update JavaScript for Bada

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1986:
---

Summary: Update JavaScript for Bada  (was: CLONE - Update JavaScript for 
Bada)

> Update JavaScript for Bada
> --
>
> Key: CB-1986
> URL: https://issues.apache.org/jira/browse/CB-1986
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Bada
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1985) Update JavaScript for Android

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1985:
---

Summary: Update JavaScript for Android  (was: CLONE - Update JavaScript for 
Android)

> Update JavaScript for Android
> -
>
> Key: CB-1985
> URL: https://issues.apache.org/jira/browse/CB-1985
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: Android
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Simon MacDonald
> Fix For: 2.3.0
>
>
> Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1984) Tag Hello World App

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1984:
---

Summary: Tag Hello World App  (was: CLONE - Tag Hello World App)

> Tag Hello World App
> ---
>
> Key: CB-1984
> URL: https://issues.apache.org/jira/browse/CB-1984
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: App Hello World
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>    Assignee: Michael Brooks
> Fix For: 2.3.0
>
>
> Tag sample application so that each platform can cut a copy of the 
> application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2014) CLONE - Generate a Source Release

[Michael Brooks (JIRA)]

Michael Brooks created CB-2014:
--

 Summary: CLONE - Generate a Source Release
 Key: CB-2014
 URL: https://issues.apache.org/jira/browse/CB-2014
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Coho
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Steve Gill
 Fix For: 2.3.0


After all other sub-tasks have been completed, Coho can generate the source 
release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2013) CLONE - Tag Mobile Spec

[Michael Brooks (JIRA)]

Michael Brooks created CB-2013:
--

 Summary: CLONE - Tag Mobile Spec
 Key: CB-2013
 URL: https://issues.apache.org/jira/browse/CB-2013
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: mobile-spec
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
 Fix For: 2.3.0


After all platforms have been tagged, mobile-spec can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CB-1983) Tag Cordova-JS

[Michael Brooks (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CB-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Brooks updated CB-1983:
---

Summary: Tag Cordova-JS  (was: CLONE - Tag Cordova-JS)

> Tag Cordova-JS
> --
>
> Key: CB-1983
> URL: https://issues.apache.org/jira/browse/CB-1983
> Project: Apache Cordova
>  Issue Type: Sub-task
>  Components: CordovaJS
>Affects Versions: 2.3.0
>    Reporter: Michael Brooks
>Assignee: Anis Kadri
> Fix For: 2.3.0
>
>
> Tag JavaScript so that each platform can cut a JavaScript release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2010) CLONE - Tag webOS

[Michael Brooks (JIRA)]

Michael Brooks created CB-2010:
--

 Summary: CLONE - Tag webOS
 Key: CB-2010
 URL: https://issues.apache.org/jira/browse/CB-2010
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: webOS
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Herm Wong
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2011) CLONE - Tag WP7

[Michael Brooks (JIRA)]

Michael Brooks created CB-2011:
--

 Summary: CLONE - Tag WP7
 Key: CB-2011
 URL: https://issues.apache.org/jira/browse/CB-2011
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: WP7
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Jesse MacFadyen
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2012) CLONE - Tag Docs

[Michael Brooks (JIRA)]

Michael Brooks created CB-2012:
--

 Summary: CLONE - Tag Docs
 Key: CB-2012
 URL: https://issues.apache.org/jira/browse/CB-2012
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Docs
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Michael Brooks
 Fix For: 2.3.0


After all platforms have been tagged, the docs can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2009) CLONE - Tag Tizen

[Michael Brooks (JIRA)]

Michael Brooks created CB-2009:
--

 Summary: CLONE - Tag Tizen
 Key: CB-2009
 URL: https://issues.apache.org/jira/browse/CB-2009
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Tizen
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2008) CLONE - Tag Qt

[Michael Brooks (JIRA)]

Michael Brooks created CB-2008:
--

 Summary: CLONE - Tag Qt
 Key: CB-2008
 URL: https://issues.apache.org/jira/browse/CB-2008
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Qt
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2006) CLONE - Tag iOS

[Michael Brooks (JIRA)]

Michael Brooks created CB-2006:
--

 Summary: CLONE - Tag iOS
 Key: CB-2006
 URL: https://issues.apache.org/jira/browse/CB-2006
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: iOS
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2005) CLONE - Tag BlackBerry

[Michael Brooks (JIRA)]

Michael Brooks created CB-2005:
--

 Summary: CLONE - Tag BlackBerry
 Key: CB-2005
 URL: https://issues.apache.org/jira/browse/CB-2005
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: BlackBerry
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Tim Kim
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged 
as 2.2.0rc1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2003) CLONE - Tag Android

[Michael Brooks (JIRA)]

Michael Brooks created CB-2003:
--

 Summary: CLONE - Tag Android
 Key: CB-2003
 URL: https://issues.apache.org/jira/browse/CB-2003
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Android
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Simon MacDonald
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged 
as 2.2.0rc1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2007) CLONE - Tag Mac

[Michael Brooks (JIRA)]

Michael Brooks created CB-2007:
--

 Summary: CLONE - Tag Mac
 Key: CB-2007
 URL: https://issues.apache.org/jira/browse/CB-2007
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Mac
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2004) CLONE - Tag Bada

[Michael Brooks (JIRA)]

Michael Brooks created CB-2004:
--

 Summary: CLONE - Tag Bada
 Key: CB-2004
 URL: https://issues.apache.org/jira/browse/CB-2004
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Bada
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


After updating the JavaScript and sample application, the release can be tagged 
as 2.2.0rc1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2000) CLONE - Update www/ Application for Tizen

[Michael Brooks (JIRA)]

Michael Brooks created CB-2000:
--

 Summary: CLONE - Update www/ Application for Tizen
 Key: CB-2000
 URL: https://issues.apache.org/jira/browse/CB-2000
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Tizen
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2002) CLONE - Update www/ Application for WP7

[Michael Brooks (JIRA)]

Michael Brooks created CB-2002:
--

 Summary: CLONE - Update www/ Application for WP7
 Key: CB-2002
 URL: https://issues.apache.org/jira/browse/CB-2002
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: WP7
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Jesse MacFadyen
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1999) CLONE - Update www/ Application for Qt

[Michael Brooks (JIRA)]

Michael Brooks created CB-1999:
--

 Summary: CLONE - Update www/ Application for Qt
 Key: CB-1999
 URL: https://issues.apache.org/jira/browse/CB-1999
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Qt
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1998) CLONE - Update www/ Application for Mac

[Michael Brooks (JIRA)]

Michael Brooks created CB-1998:
--

 Summary: CLONE - Update www/ Application for Mac
 Key: CB-1998
 URL: https://issues.apache.org/jira/browse/CB-1998
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Mac
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-2001) CLONE - Update www/ Application for webOS

[Michael Brooks (JIRA)]

Michael Brooks created CB-2001:
--

 Summary: CLONE - Update www/ Application for webOS
 Key: CB-2001
 URL: https://issues.apache.org/jira/browse/CB-2001
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: webOS
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Herm Wong
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1995) CLONE - Update www/ Application for Bada

[Michael Brooks (JIRA)]

Michael Brooks created CB-1995:
--

 Summary: CLONE - Update www/ Application for Bada
 Key: CB-1995
 URL: https://issues.apache.org/jira/browse/CB-1995
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Bada
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1994) CLONE - Update www/ Application for Android

[Michael Brooks (JIRA)]

Michael Brooks created CB-1994:
--

 Summary: CLONE - Update www/ Application for Android
 Key: CB-1994
 URL: https://issues.apache.org/jira/browse/CB-1994
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Android
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Joe Bowser
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1997) CLONE - Update www/ Application for iOS

[Michael Brooks (JIRA)]

Michael Brooks created CB-1997:
--

 Summary: CLONE - Update www/ Application for iOS
 Key: CB-1997
 URL: https://issues.apache.org/jira/browse/CB-1997
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: iOS
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1992) CLONE - Update JavaScript for webOS

[Michael Brooks (JIRA)]

Michael Brooks created CB-1992:
--

 Summary: CLONE - Update JavaScript for webOS
 Key: CB-1992
 URL: https://issues.apache.org/jira/browse/CB-1992
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: webOS
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Markus Leutwyler
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1993) CLONE - Update JavaScript for WP7

[Michael Brooks (JIRA)]

Michael Brooks created CB-1993:
--

 Summary: CLONE - Update JavaScript for WP7
 Key: CB-1993
 URL: https://issues.apache.org/jira/browse/CB-1993
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: WP7
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Jesse MacFadyen
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1996) CLONE - Update www/ Application for BlackBerry

[Michael Brooks (JIRA)]

Michael Brooks created CB-1996:
--

 Summary: CLONE - Update www/ Application for BlackBerry
 Key: CB-1996
 URL: https://issues.apache.org/jira/browse/CB-1996
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: BlackBerry
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Tim Kim
 Fix For: 2.3.0


Update the www/ sample application after App-Hello-World has been tagged.

*IMPORTANT*: Remove the irrelevant platforms from {{www/res/icon}} and 
{{www/res/screen}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1991) CLONE - Update JavaScript for Tizen

[Michael Brooks (JIRA)]

Michael Brooks created CB-1991:
--

 Summary: CLONE - Update JavaScript for Tizen
 Key: CB-1991
 URL: https://issues.apache.org/jira/browse/CB-1991
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Tizen
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1989) CLONE - Update JavaScript for Mac

[Michael Brooks (JIRA)]

Michael Brooks created CB-1989:
--

 Summary: CLONE - Update JavaScript for Mac
 Key: CB-1989
 URL: https://issues.apache.org/jira/browse/CB-1989
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Mac
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1986) CLONE - Update JavaScript for Bada

[Michael Brooks (JIRA)]

Michael Brooks created CB-1986:
--

 Summary: CLONE - Update JavaScript for Bada
 Key: CB-1986
 URL: https://issues.apache.org/jira/browse/CB-1986
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Bada
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1988) CLONE - Update JavaScript for iOS

[Michael Brooks (JIRA)]

Michael Brooks created CB-1988:
--

 Summary: CLONE - Update JavaScript for iOS
 Key: CB-1988
 URL: https://issues.apache.org/jira/browse/CB-1988
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: iOS
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Shazron Abdullah
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1985) CLONE - Update JavaScript for Android

[Michael Brooks (JIRA)]

Michael Brooks created CB-1985:
--

 Summary: CLONE - Update JavaScript for Android
 Key: CB-1985
 URL: https://issues.apache.org/jira/browse/CB-1985
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Android
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Simon MacDonald
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CB-1990) CLONE - Update JavaScript for Qt

[Michael Brooks (JIRA)]

Michael Brooks created CB-1990:
--

 Summary: CLONE - Update JavaScript for Qt
 Key: CB-1990
 URL: https://issues.apache.org/jira/browse/CB-1990
 Project: Apache Cordova
  Issue Type: Sub-task
  Components: Qt
Affects Versions: 2.3.0
Reporter: Michael Brooks
Assignee: Anis Kadri
 Fix For: 2.3.0


Update the cordova.js after Cordova-JS has been tagged.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira