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.
On Tue, Feb 25, 2014 at 4:22 AM, Tim Oxley <[email protected]> wrote: > 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. > > > On Tuesday, 25 February 2014 11:04:34 UTC+8, Eric Bidelman wrote: >> >> 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 >> > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/39f89146-d4e6-4ddb-9d09-12e93c1e9c01%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAHbmOLYdT-ukQ9VJ9zWnbeA0aQgHTwVTkTg0ocW%2BmB6qcvv_-g%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
