Ok so a 4.13 release in July/August once Extensions Manager update and SlicerVMTK are complete. Then 5.0 released soon after in August.
As the milestones are currently organized, carrying over issues to the next milestone makes it difficult for me to consider which ones to maybe help out with to test and debug. It is difficult to see which items must be complete before a release and which things are not. It seems like many items in the 4.13 milestone are just nice to haves and not that much different from issues in the “backlog” milestone or with an undefined milestone.
Maybe this is part of the “how to know which issues are priority” issue. Up votes can help, but maybe only keeping the main things in the milestone would also help and other supporting things just be outside of the milestone. Maybe at least issues are only added to the milestone when someone has actually started work on the issue.