Deprecated - Drupal.org infrastructure

Building on the foundation of the new release system, and to lay the foundation for Drupal core telling you if your site is out of date and in particular telling you if there is a security update available for any of your installed modules, it is now possible for project maintainers to classify their releases. There is a new vocabulary on drupal.org that only applies to releases, called Release type. The possible values are:

Security update

This release contains a critical security update. Any release associated with this term should have a link to the corresponding security announcement in the release notes. Please see the Contacted by the security team. Now what? handbook page about the proper way to handle security-related releases.

Bug fixes

The release should be marked with this if it contains any non-security related bug fixes.

New features

In general, new features should only be added to development branches for your project, but any release that contains new features should have this term.

This should possibly be a feature request, but posting it here first to get some feedback on the idea. It is initially about Drupal.org, but generally useful I would think.

It would be practical if there was a way of saying "ok, thanks" or similar feedback WITHOUT that remark being regarded (and syndicated) as new or updated content.

Hi

It strikes me that there is probably a *lot* of duplicate effort going on when it comes to defining new FAPI elements.

I think if there were a new category on the Module list page here at drupal.org, called "Form Elements", it would make it a lot easier for people to find perfectly good and already existing form elements that could be reused (as opposed to rolling it again from scratch).

MrTaco

Hi!

I was interested that flickr and delicious used drupal, but I also hear that design with drupal is slightly constrained, so how is it that both these sites don't look constrained in their design.

Can the design and the drupal aspect be seperate, if not why not?

thanks t

The gallery module now has an official 5.x-1.0 release, and 2 development snapshots (5.x-1.x-dev and 5.x-2.x-dev). I cannot get the 5.x-2.x-dev snapshot to appear on the main gallery module page under "Development Snapshots" without losing the 5.x-1.0 official release. Is there a way to do this, or (even better), have both 5.x-1.x-dev and 5.x-2.x-dev snapshot releases appear?

I think it would be a great idea to allow users to submit review for modules.

The problem today is that, there are so many modules available, but woefully inadequate descriptions,/b>. There are so vague and users we still have to download, install, and try to figure out what each module does.

Its so bad, that I was thinking of setting up my own site to review modules. I don't really want to rate modules, but rather, give a better explanation to what each module does. Go through the menu hook and explain where the settings are for each module and what are the effects this module does.

I want to give screenshots for these modules. The best way to explain modules is by giving screenshots because its quite difficult to visualize module functions using words.

Of course I would explain which version of the module I'm using.

Notice I used to word review and not comment. Comments would only lead to people complaining about bugs and asking how to install or use the module, which are better put in the issues section.

To avoid frivalous comments, I would suggest

a) the easiest way,
- put up a big disclaimer informing users what a review is as opposed to comments.
- imposing a minimum word count
- imposing a screenshot requirement

b) a more complex method,