Rough meeting notes:
Attendees: @Bajix @chasen @cherif_b @imjoshdean @justinbmeyer @Macrofig @matthewp @pYr0x
Discussed topics:
- How should we handle this breaking change?
- Start a
major
branch for breaking changes; we’ll coalesce all of them into acan-stache
4.0 release - There’s already a deprecation warning for those two keys
- We’ll eventually figure out how we want to handle new major versions of CanJS
– Maybe coalesce multiple breaking changes in different modules into one major CanJS release
– Maybe release new major versions every ~6 months
- General consensus on moving forward with the proposal
@Nothing_New’s issues:
- Available for someone to pick up:
– can-view-import error reporting
– can-import can-tag fails silently when tag does not exist - Already fixed Development mode doesn’t package players in players page
- Kinda similar to
can-connect
’s behaviors - This is one proposal; still looking for better solutions
- Josh’s module helps you lint
.js
and.component
files
- Most people are on a recent version or would not have a difficult time upgrading
- Current strategy: support Node 4, 6, 7 for now; wait until we have issues with 4 before making a decision about dropping it