Deprecated - Drupal.org infrastructure

The 5.0 release candidate of Drupal core is now installed on scratch.drupal.org. Of particular interest for contribution maintainers on drupal.org, this means that the Project module and all related parts of the new release system have been ported to the 5.x API. Please help ensure that the release system continues to function smoothly once we upgrade drupal.org to a 5.0 release candidate by testing out things on http://scratch.drupal.org. Read more to find out how...

I am probably not the first one to think of this but

why not have a "my modules" section that shows recent updates only of the modules that a user has downloaded either by allowing a user to specify which modules he/ she uses (e.g. radio buttons) or asking the user to login before downloading a module to track which ones have been downloaded or a combination of both methods.

Hello,

Please, could a Drupal's site maintainer remove this release node ?
I mistakenly created a 4.7 2.x release node as the first release.

Thanks in advance and sorry for the inconvenience.

Regards.
Moxide

I'm really excited about Drupal 5.0 - so much so that I've been hitting the "critical bugs" links from the beta and RC pages over and over again to watch the developers progress towards new releases. Due to work and other coding commitments, I can't get involved in rolling patches right now—eventually, I will. In the meantime, I want to help by doing bug triage; that is, herding bugs so they're easier for developers to attack. For example,

• There are three pages of active bugs against 5.0-beta1 and 5.0-beta2; shouldn't these be updated to 5.0-rc1 or 5.x-dev if they're still outstanding? Which one?
• There are active tasks (16 total) and feature requests (9 total) against 5.0-beta1, 5.0-beta2 and 5.0-rc1. Since these are really development milestones and not actual releases, should there really even be features and tasks for them?

There are also 49 pages of bugs, tasks and feature requests against "x.y.z". I suspect a lot of cruft could be cleaned out, and many recent issues would be revealed as duplicates of, e.g. Drupal.org node #572, which is four years old.

I tried to install drupal on a subdomain on my web server and it made all my web site's index pages inaccessible, turned them all into just lists of the parent directory. I only wanted drupal on one subdomain web site, not every website I have. Now I have uninstalled Drupal to return the web sites as before, but they still won't go to the homepage when the url is given, instead go to the parent directory. What can I do to return things to normal? Can I not install Drupal on just one subdomian. It's kind of put me off that I have to turn every site into Drupal.