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.

Comments

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

Bump.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
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.

killes@www.drop.org’s picture

killes@www.drop.org commented

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

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

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).

killes@www.drop.org’s picture

killes@www.drop.org commented
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.