add setting to hide a given release series without unpublishing release nodes
| Project: | Project |
| Version: | 5.x-1.x-dev |
| Component: | Releases |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
i recently discontinued support of 4.6.x project module. however, it's too bad i had to unpublish all the release nodes just to get 4.6.x to disappear from the project node's download table. ideally, there'd be a checkbox in the little table on the "Releases" subtab of the edit tab, that controlled if that particlar core version was visible on the project node and for the purposes of the project browsing pages. but, leaving the release nodes published is nice so they're still on the "All releases" page, still visible as real versions in the issue queue, etc.
plus, until http://drupal.org/node/90531 is done, it'd be an easy way to give project maintainers a way to discontinue support for a given release series without generating webmasters support issues...
#1
This could also tie into http://drupal.org/node/97568
What about adding an option to each release node for 'Supported' or, one for 'No longer supported.' I don't know which is the better option, but say that the end result is, only supported releases are shown on the project page, (or are you saying only supported releases should up on the 'view all releases'?) Either way, we could also restrict the Version selector on new issue and issue comment pages to only show supported releases. This shouldn't restrict the viewing of old issues.
I'm thinking this would be a column in project_release_nodes? Should install so that all existing releases default to 'supported' to not break releases.
I need to spend more time looking at the code for this one, but wanted to see if anyone had any thoughts on this.
#2
This was fixed with #176776: GHOP #55: Make release summary table UI look more like update(_status)? report. Man, whomever created that issue really should check for duplicates once in a while :)
#3
Automatically closed -- issue fixed for two weeks with no activity.