In one of the discussions unrelated to Slicer, someone raised a question about how to properly phase out software tools that for one reason or another are no longer supported/needed/working. Martin Morgan from the Bioconductor team shared their “Package End-of-Life Policy” . Bioconductor is a well-es…

Thanks for the link. The policy makes complete sense and even if the policy is almost trivial, I agree that it could be useful to put it in writing. We could address some not-so-trivial issues in the policy. For example, we could explicitly state that if the maintainer does not integrate a pull req…

RFC: Slicer extension end-of-life procedure

Support

pieper (Steve Pieper (Isomics, Inc.)) April 12, 2019, 4:31pm 2

Very good point. We actually started discussing this the other day on the developer hangout and started working on a standardized scheme for the extension status.

Topic		Replies	Views
What to do with abandoned extensions? Development	2	263	January 27, 2019
Introduction of "tiers" for Slicer extensions Development extensions-manager	14	415	November 25, 2024
What happens to the extensions in the current stable once a new one is released? Support	3	289	October 20, 2021
Why are the extension manager updates not up-to-date? Support	17	366	March 6, 2023
2019.03.26 Hangout Weekly meetings	2	682	March 26, 2019

RFC: Slicer extension end-of-life procedure

Related topics