jlipps

We recently swapped Appium branches so that the old 1.5 branch is now master. This is great! Unless you already have a local copy of Appium master checked out and want to do a git pull. Unfortunately since we have reset master this is no longer possible. Here's how you do it.

0. Ensure you have no local changes or commits you want to save. (If you do, get them in a branch).
1. Figure out what your Appium remote branch is called. For me it is upstream, for you it might be origin. Below, I will call this <remote> and you should replace it with the reality for your own local checkout.
2. git checkout master
3. git reset --hard fbbb126 -- this will get you to a place in the git history prior to the divergence
4. git pull <remote> master -- this will get all the new code
5. You might also need to rm -rf submodules/ in order to have a clean checkout, since we no longer track submodules in the Appium git repo.

That's it! Happy hacking.

jlipps

Appium 2.0

As described in the Appium 2.0 Epic, Appium needs to evolve from being a server which bundles many drivers to one which by default doesn't bundle any drivers, and instead provides an interface for retrieving and using drivers. Essentially, "Appium" will become:

• A set of spec extensions to the WebDriver W3C protocol (eventually upstreaming those extensions to the official protocol)
• A set of code libraries (like BaseDriver or jsonwp-proxy that make it easy to write Appium drivers)
• A driver runner (this is what the main Appium package currently does); the difference is that drivers will not come bundled with the runner by default
• A plugin interface based around command-level hooks
• An API and CLI interface for retrieving and managing different versions of Appium-compatible drivers and plugins

jlipps

Keybase proof

I hereby claim:

• I am jlipps on github.
• I am jlipps (https://keybase.io/jlipps) on keybase.
• I have a public key ASA5enU7HxGauG4EsLazqFp6THAD-Uts_EWqs9QILVU7IQo

To claim this, I am signing this object: