Tomorrow, we will be having our next weekly hangout at 10:00 AM ET until 11 AM ET.
Anyone is welcome to join to ask questions at https://bit.ly/slicer-googlemeet-hosted-by-kitware
Agenda:
Feel free to post to this thread to request/suggest a topic!
Thanks
Sam and J-Christophe
Any update on timeline of new extension manager backend completion as it relates to the next stable release?
Are the issues in the Slicer 4.13.0 GitHub milestone blockers that must be resolved prior to the next release? How is the Slicer 4.13.0 milestone issues distinct from the Slicer 5.0.0 GitHub milestone? Are these different releases?
There are two blockers to the new Slicer Stable Release: the Extensions Manager update and SlicerVMTK extension build. If these are resolved then the new stable will be released. I hope it can happen within a week or two, but @jcfr is the main developer of both, so he can give a better estimate.
Unresolved 4.13 milestone issues will be automatically rescheduled for 5.0, which is planned to be released in August. There is no much practical difference between 4.13 and 5.0 milestones, other than issues in 5.0 are not even considered to be fixed in the upcoming stable release, while issues in 4.13 might.
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.
Help is welcome with any issues (“bug” has higher priority than “enhancement” and priority tag may give hints about importance of issues). If an issue is already assigned to someone then write a comment at the issue and wait a day (if you don’t get answer earlier) before you assign it to yourself and start working on it. Thank you!