We’ve updated the Meteor roadmap with more information about what we (the project maintainers and contributors) will be focusing our time on for upcoming releases.
The roadmap is intended to reflect work that maintainers and contributors plan to undertake in the near- to medium- term.
This roadmap is not intended to be a grand vision for the framework or a commitment to delivering any feature on a particular timeline.
To make the roadmap a good resource for those looking to keep tabs on the project’s operation and progress, we now aim to update it monthly with status updates and changes to roadmap items. We hope you find it helpful!
Here’s a quick list of meta-level changes to the document that you should expect to see going forward:
Status information on roadmap items
Contributors with design approval can now submit changes to the roadmap
Many thanks to @benjamn & @sashko for their help in getting this refreshed!
Note: If you’d like to see a feature on the roadmap that isn’t there, please add to an existing issue or open a new one on meteor/meteor, as we won’t be collecting feature requests in this thread.
And there’s a process for adding additional priorities via issues and design documents! I think this is a new level of transparency, and we’re going to try to update at least monthly so that there are no questions about what we are working on!
That’s a great move! I like that you included past developments and current status. If you update this monthly I’m sure everyone will be super happy :).
On a side note: Code splitting & dead code evaluation
Speeding up page load times will require a combination of new tools for asynchronous JavaScript delivery (code splitting), dead code elimination, deferred evaluation of JavaScript modules, and performance profiling (so that developers can identify expensive packages).