Skip to content

Conversation

@TimvdLippe
Copy link
Contributor

To make sure this implement can be cleanly installed in a Polymer 2 application,
use the latest stable versions of most of the elements.

To make sure this implement can be cleanly installed in a Polymer 2 application,
use the latest stable versions of most of the elements.
@notwaldorf
Copy link

@ebidel @e111077 halp, should this go in? who's in charge? 👮

@ebidel
Copy link
Contributor

ebidel commented Jun 7, 2017

I'm out of the loop when it comes to Polymer 2.

I've never seen the form #1 - 2. Is that something we want? IOW, is this element going to work with 2.0 without any changes?

@e111077
Copy link
Contributor

e111077 commented Jun 7, 2017

@ebidel this PR is attempting to merge into the 2.0-preview branch which has already been updated to work in 2.0.

For the versioning, that's what we've been using for our 2.0 elements ¯\_(ツ)_/¯

@e111077
Copy link
Contributor

e111077 commented Jun 7, 2017

Merging into 2.0-preview. It also seems as if @samuelli has been maintaining the branch. Can he be made member / collaborator please?

@e111077 e111077 merged commit 1ba6a7f into GoogleWebComponents:2.0-preview Jun 7, 2017
@TimvdLippe TimvdLippe deleted the patch-1 branch June 7, 2017 05:01
@joemarini
Copy link

When will these changes be updated into webcomponents.org?

@e111077
Copy link
Contributor

e111077 commented Jun 7, 2017

I believe these changes do not reflect until it is merged into master ...and possibly released?

@samuelli
Copy link
Contributor

samuelli commented Jun 8, 2017

Each release will show up on webcomponents.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants