<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>andrew_</author><text>Hello. Webpack team member here. The webpack@4 release was, well, interesting. I can&amp;#x27;t add much that hasn&amp;#x27;t already been said - but I can say that we&amp;#x27;re working to make sure there will never be another webpack release that suffers from the same kind of documentation shortcomings. There&amp;#x27;s a metric poopton of good stuff in the release, and we&amp;#x27;re still working to get all of it written down. That said, look for future major releases to be far more proactive than reactive with regard to documentation, announcements, and migration details.</text><parent_chain></parent_chain></comment><story><title>An attempt to upgrade to Webpack 4</title><url>https://gist.github.com/gricard/e8057f7de1029f9036a990af95c62ba8</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>lmcardle</author><text>As someone who has worked with many of the various tools out there, I have a lot of respect for the way the EmberJS team handles upgrades. I personally wish more teams learned from their success. Their mantra is “stability without stagnation.” While it is not perfect, the team appears to try hard to move the framework forward without breaking backwards compatibility. When it comes to a major release, I.e. the just released 3.0, the team released no new features, but rather just removed the features that had been depreciated in earlier releases.&lt;p&gt;Like or hate Ember as a framework, the team has developed some very good release processes and practices a lot of us could learn from.</text><parent_chain></parent_chain></comment><story><title>An attempt to upgrade to Webpack 4</title><url>https://gist.github.com/gricard/e8057f7de1029f9036a990af95c62ba8</url></story>