Implementing GitHub Milestones

Gabe Alford redhatrises at gmail.com
Tue Sep 2 18:28:27 UTC 2014


Hello list,

I was thinking/pondering about this today, and was wondering if our project
should implement milestones on GitHub. This way we can see the pull
requests by milestone (historical) and set loose expectations about future
milestones. (I say loose because priorities change, no one may be currently
working on an issue, etc.)

Milestones could match the existing versioning with scap-security-guide
releases. (0.19, 0.20, etc.)
Any pull request that is merged without an existing issue would be added to
the existing milestone. Any issue that is not fixed in time for the monthly
release will be moved to the next milestone.

An example would be here: https://github.com/Netflix/Hystrix/milestones

It may be beneficial, or might just be added process/work without a lot of
beneficial use. Thoughts?

Thanks,

Gabe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/scap-security-guide/attachments/20140902/03aeee3a/attachment-0001.html>


More information about the scap-security-guide mailing list