all along since i wrote the new release system, i was planning to have additional taxonomy goodness on d.o to take advantage of it. one of the big goals was to be able to tag release nodes to identify if they represent a security update, so that things like update_status.module could be taught to flag them more visibly with the YOU MUST UPGRADE NOW, FOOL! in bright, flashing red. ;) see http://drupal.org/node/125742 and http://drupal.org/node/136172#comment-228691 (comment #4) for more.

well, the first step to all of that is to create the vocabulary, give it some terms, and enable it on release nodes on d.o.

i propose:

name: "Release type"
multi-select, non-required
terms:
- Security update
- Bug fixes
- New features

a given release node could have between 0 and 3 of these options selected.

of course, existing nodes won't have the terms until a maintainer goes in and adds them, but that's ok. the most important part is the "Security update" term, and a) there aren't *that* many official releases that need that flag, so we can easily do that pretty quickly and b) nothing (yet) understands these terms, so the most important thing will be for new release nodes going forward, not all the existing ones...

i've got all the powers on d.o i need to do this, i just want to get some feedback and +1's on this (especially from the core d.o maintainers like killes and dries) before i run off and do it.

thanks,
-derek

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented

I think this is a logical extension of dww's previous work and I am in favour of implementing this too.

heine’s picture

heine commented

I'd certainly support this for the update_status module. and core's system.module, but I would like to wait with creating the terms until the patches have landed for those modules.

dww’s picture

dww
we/he/they
commented

Heine: thing is, i need to start working on the project* backend stuff to include this data NOW. we need the data in the xml histories for those modules to support this feature, and we need the vocab on d.o before the xml histories have the data. plus, as a taxonomy vocabulary, we'd immediately get some goodness out of this, even without support in update_status or system.module (e.g. an RSS feed of all release nodes marked as "Security update")... that's why i want to do this now, and start teaching maintainers to use these terms, and we can work on adding functionality to take advantage of them in the mean time.

merlinofchaos’s picture

merlinofchaos commented

I agree with dww. +1 to this -- it's easier to work from a foundation with data than without.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Excellent. Not only will this be critical for both update status in core and the upcoming project quality metrics SoC project, but it's also very useful for humans even before either of these systems are completed.

RTBC. ;)

heine’s picture

heine commented

True, there certainly are advantages outside of update status too. I'd say go ahead.

dries’s picture

dries commented

+1. I think this will help us communicate better about releases. Just do it. :)

dww’s picture

dww
we/he/they
commented
Status: Active » Needs work

vocab and terms created. by happy circumstance, the "Security update" term is d.o's 100th taxonomy term. ;)
http://drupal.org/taxonomy/term/100

setting to CNW for documentation reasons:

  1. update d.o RSS feeds page
  2. update release node docs in CVS handbook
  3. compose forum post and email to devel list

vounteers welcome for any of those. ;)

also, i took the liberty of a little UI optimization for d.o for now: the taxonomy selectors when you add a release node are now all in-line in the "Categories" fieldset, so as not to waste too much space. however, that's assuming we're not going to stick a big description under "Release type" (i think it's pretty darn self-explanatory as-is). comments on this are welcome.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Updated:
http://drupal.org/node/63589 (feeds)
http://drupal.org/node/94151 (how to create release nodes)
http://drupal.org/handbook/cvs/releases/types (different release types)

Derek said he'd take care of the announcement.

dww’s picture

dww
we/he/they
commented
Status: Needs work » Fixed

thanks to webchick for the help on the other handbook pages!

here's the forum post:
http://drupal.org/node/142344

i just sent out a link for this to the devel + translation email lists.

this issue is hereby done. ;)

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)