hide issues list for polymer-dev and platform-dev?

[Eric Bidelman]

To minimize confusion, can we consolidate and use the non "-dev" issue trackers?

I'm happy to port the issues from polymer-dev and platform-dev and turn off their bug sections.

Eric

[Steve Orvell]

This is fine by me.

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CACGqRCB_3CMyWa2oGU9DbUsh%2BJ3VnpJo4fAaA%3Ds5XN9iaCrOOg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Tim Oxley]

Would you consider doing this the other way around since the -dev ones are actually for dev… i.e. point people at the development repos if you want them to collaborate on the development.

[Scott Miles]

IMO, it would be better to have the issues on *-dev, because that's where commits go, and otherwise it will be hard to match commits to issues. I do realize that it could be confusing for end-users, so I'm not insisting.

Follow Polymer on Google+: plus.google.com/107187849809354688692

---
You received this message because you are subscribed to the Google Groups "Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to polymer-dev...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/39f89146-d4e6-4ddb-9d09-12e93c1e9c01%40googlegroups.com.

[Eric Bidelman]

I also don't care either way...but I'm not volunteering to write the migration script :)

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAHbmOLYdT-ukQ9VJ9zWnbeA0aQgHTwVTkTg0ocW%2BmB6qcvv_-g%40mail.gmail.com.