On 11/22/2016 07:29 AM, Hannes Mehnert wrote:
hello,
to get towards a release, and find all the stuff which needs to be done
before, in addition to the tracking issues, I used the already existing
Milestone 3.0.0 on the GitHub issue tracker for mirage/mirage.
This is only an attempt to not loose track of what needs to be done, in
order to get the picture adjusted (comments like "is still broken" help
on the issues, but it is easy enough to loose track of the relevant issues).
I might have taken the wrong decision on some issues, please look
through all mirage issues yourself (and adjust milestones, or comment on
the issue if you lack permissions). There are likely also relevant
issues in other repositories, which we should link to.
You can find the milestone at https://github.com/mirage/mirage/milestone/8
For those keeping track at home, we now have:
https://github.com/mirage/mirage/milestone/8 - a milestone for tracking
MirageOS 3.0.0
https://github.com/mirage/mirage/projects/1 - a project for tracking MirageOS
3.0.0
https://github.com/mirage/mirage/issues/592 - a tracking issue for MirageOS
3.0.0
https://github.com/mirage/mirage/issues/571 - a tracking issue for changes to
the `mirage/mirage` repository including the set of module types over which
`mirage` constructs functors for MirageOS 3.0.0
https://github.com/Solo5/solo5/issues/82 - a tracking issue for the solo5
components of the MirageOS 3.0.0 release (all of which are completed! well
done, mato, djwillia, ricarkol, hannesm, and anyone I've missed)
https://github.com/mirage/mirage/issues/652 - a tracking issue for
infrastructure changes planned for deploying MirageOS 3.0.0
Submitting changes to MirageOS now has a greater-than-normal chance of allowing
you to check off a ticky box somewhere and enjoy the sweet, sweet endorphin
rush of marking something complete.
Thanks,
Mindy
_______________________________________________
MirageOS-devel mailing list
[email protected]
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
