<p dir="auto"><a href="http://pypi.python.org/pypi/scikits.learn" rel="nofollow">http://pypi.python.org/pypi/scikits.learn</a> (v. 0.8.1) vs <a href="http://pypi.python.org/pypi/scikit-learn" rel="nofollow">http://pypi.python.org/pypi/scikit-learn</a> (v. 0.10).</p>
<p dir="auto">Follow-up of <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/jnothman/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/jnothman">@jnothman</a> <a href="https://github.com/scikit-learn/scikit-learn/pull/19155#issuecomment-785461124" data-hovercard-type="pull_request" data-hovercard-url="/scikit-learn/scikit-learn/pull/19155/hovercard">comment</a>.<br>
I would like to propose to enforce milestones in pull requests.<br>
That means:</p>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> create a check that verify if the milestone is present</li>
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> modify the check on the change log to verify consistency with the milestone.</li>
</ul>
<p dir="auto">I believe it is helpful in anticipating breaking changes, and could give a more long-term vision on the library developments. It is also helpful for contributors, as they will have a better understanding of how much their pull request is awaited.<br>
This approach is used for example by the <a href="https://github.com/astropy/astropy/milestones">Astropy project</a>: no milestoned pull requests will still have their place anyway, they are long term feature implementations or code reformatting.</p>