Update polymer 1.0 install to pick up newly added elements.

Update polymer 1.0 install to pick up newly added elements.

BUG=

[estaab, 2015-07-30 22:55:39]

estaab@chromium.org changed reviewers:
+ hinoka@chromium.org

[Ryan Tseng, 2015-07-30 23:54:04]

hinoka@google.com changed reviewers:
+ hinoka@google.com

[Ryan Tseng, 2015-07-30 23:54:04]

shouldn't there be a diff in the root bower.json?

[estaab, 2015-07-31 00:47:57]

On 2015/07/30 23:54:04, Ryan Tseng wrote:
> shouldn't there be a diff in the root bower.json?

There wasn't when I did the update on paper-elements and iron-elements (and
that's it).

[hinoka, 2015-07-31 00:51:15]

So is this still 1.0.4 or is this 1.0.8 now?

If the latter I think its is probably better as a new folder, or rename this to
1.0.8, symlink 1.0.4 to 1.0.8, and add a large note saying that 1.0.4 is
actually a lie.

This bower business is a little confusing to me, how do you update in place
without the manifest changing @__@.

[estaab, 2015-07-31 01:15:28]

On 2015/07/31 00:51:15, hinoka wrote:
> So is this still 1.0.4 or is this 1.0.8 now?
> 
> If the latter I think its is probably better as a new folder, or rename this
to
> 1.0.8, symlink 1.0.4 to 1.0.8, and add a large note saying that 1.0.4 is
> actually a lie.
> 
> This bower business is a little confusing to me, how do you update in place
> without the manifest changing @__@.

The version of polymer is the same, it's still 1.0.4. The polymer components
(e.g. paper, iron) are independent and it the bower.json file didn't get updated
even though the components did. I updated the versions of paper-elements and
iron-elements to match what's actually there.

It turns out our "dependencies" definition allows for a range of versions, and
~1.0.x says any version 1.0.y can be used where y >= x. See
https://github.com/npm/node-semver#tilde-ranges-123-12-1

Given that we use tilde versioning for all of the deps we probably should have
called the directory polymer_1.0, but oh well. The directory name still matches
the polymer version since I didn't update it so it's not a lie.

[Ryan Tseng, 2015-07-31 01:59:17]

lgtm

Oh I see the submodules are the ones being updated.  Ok.

[estaab, 2015-07-31 02:01:41]

The CQ bit was checked by estaab@chromium.org

[commit-bot: I haz the power, 2015-07-31 02:04:02]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-07-31 02:04:03]

Commit queue rejected this change because it did not recognize the base URL.
Please commit your change manually.

[estaab, 2015-10-01 18:38:30]

On 2015/07/31 02:04:03, commit-bot: I haz the power wrote:
> Commit queue rejected this change because it did not recognize the base URL.
> Please commit your change manually.

Oops, I never committed this. I can't seem to find where I uploaded from -
should I just download the patch and land it from a new branch?

[estaab, 2015-10-01 18:41:21]

On 2015/10/01 18:38:30, estaab wrote:
> On 2015/07/31 02:04:03, commit-bot: I haz the power wrote:
> > Commit queue rejected this change because it did not recognize the base URL.
> > Please commit your change manually.
> 
> Oops, I never committed this. I can't seem to find where I uploaded from -
> should I just download the patch and land it from a new branch?

Nevermind, you landed it for me. :)