I'm proposing that we, the closure-compiler team, update our planning process to include some form of publication of those plans where they can be easily seen by the Open Source community.
I expect this increased visibility will make people much more comfortable using closure-compiler.
At the moment, I'm thinking this would include:
For each quarter:
New features we're actively working to add.
Limitations and bugs we're actively working to eliminate.
Use-cases we're actively working to enable.
In some general place, but reviewed for possible update each quarter.
A general statement of our goals for closure-compiler.
A gneral statement of use-cases we actively support (or don't).
I'm proposing that we, the closure-compiler team, update our planning process to include some form of publication of those plans where they can be easily seen by the Open Source community.
I expect this increased visibility will make people much more comfortable using closure-compiler.
At the moment, I'm thinking this would include:
For each quarter:
In some general place, but reviewed for possible update each quarter.