Using milestones to track changes between versions

[gsilvapt]

Hello everyone,

As there are many changes happening simultaneously to Surface, I am struggling a bit keeping track of all changes we're introducing between versions. The next release will be version 1.0.1 and it contains really a bunch - and that is okay, as long as know what changes were introduced to write good release notes and so on.
Hence, I'm proposing (and using) GitHub Milestones for this tracking.

Conceptually, I believe Milestones were kind of a way to do project management right: So, I'd add different issues (work items) to different milestones, depending on their priority and the project roadmap. However, this is hard to do at this stage, nor Surface has the maturity to justify such thing.

Thus, the use of Milestones should be reserved solely for pull requests and to keep track of all changes. When performing a new release, we can look into the pull requests associated with the correct milestone and guide ourselves with those changes to properly write some release notes.

If nobody stands against this proposal, this change will be effective immediately in Surface and I will start to slowly propagate to all other repos in this org.

Thanks in advance for your time.