Drupal.org
Issues

Unpublish project releases because of critical bugs

Posted by Xano on February 28, 2013 at 10:49pm
Project:Drupal.org webmasters
Component:Project/Git problem
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (won't fix)

Issue Summary

I'd like http://drupal.org/node/1930200 and http://drupal.org/node/1930224 to be unpublished, as the first one lacks a specific versioned dependency and the second one contains a type the test bot didn't catch. I already released a beta9, which means that these two versions were never recommended to anyone anyway.

Login or register to post comments

Comments

#1

Posted by Xano on March 5, 2013 at 11:32am

Bump.

#2

Posted by greggles on March 5, 2013 at 2:03pm
Title:Unpublish project releases» Unpublish project releases because of critical bugs

Updated title to match what I think the situation is. It's not a common request. Leaving here to see what others think.

#3

Posted by killes@www.drop.org on March 5, 2013 at 2:13pm

we don't unpublish releases that have known security bugs, so I think this is "won't fix".

#4

Posted by Xano on March 5, 2013 at 3:32pm

These are not security bugs, but simple stupid bugs that can cause some major WTFs. I talked to Moshe on IRC and he agreed that these released could be unpublished (at the time they were not yet published, so there was no way to unpublish them).

#5

Posted by killes@www.drop.org on March 6, 2013 at 4:04am
Status:active» closed (won't fix)

The two releases are not advertised on the project page, there is a more recent release. That means that nobody ever will download them. This is a total non-issue.