Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Not sure what the general consensus will be on this idea, but...
Right now, updates for 4.7.x -> 5.x start with 1000, 5.x -> 6.x is 2000, etc. This is kind of hard to remember, and fairly unclear.
What if we renamed the updates (from 6.x on) to match the major version you are updating to? Then it's always clear what update corresponded to what version without reading the comments or doing (gasp!) MATH. ;)
Here's a patch.
Comment | File | Size | Author |
---|---|---|---|
#16 | update-renumber-d5.patch | 1.02 KB | Zen |
#15 | update-renumber-leftover.patch | 702 bytes | Zen |
#12 | patch_114.txt | 2.91 KB | webernet |
#9 | patch_109.txt | 2.52 KB | webernet |
#5 | patch_108.txt | 2.57 KB | webernet |
Comments
Comment #1
RobRoy CreditAttribution: RobRoy commentedMe likey. +1
Comment #2
Crell CreditAttribution: Crell commented+1 on concept. It's a good model for contrib to follow then, too. Are we sure that renumbering those now won't cause issues with sites that already ran those functions, or does that fall under the "devel breaks, deal" category? :-)
Comment #3
webchickYes, that falls under "devel breaks, deal" category, imo. :) Anyone who's using 6.x for anything more serious than a testbed at this point is playing with fire anyway.
Comment #4
chx CreditAttribution: chx commentedNext time do not let a maths freak like me introduce numbering. Thanks for fixing.
Comment #5
webernet CreditAttribution: webernet commentedRerolled for more updates (2005, 2006), and fix a typo in the final comment (6000 --> 7000).
Comment #6
kbahey CreditAttribution: kbahey commented+1, for the sake of clarity.
Comment #7
dmitrig01 CreditAttribution: dmitrig01 commentedComment #8
sun@todo
comment seems not appropriate here. IMHO, it could be removed since those numbers are intuitive now.Comment #9
webernet CreditAttribution: webernet commentedYou're right - rerolled without @todo
Comment #10
sun*bump*
http://api.drupal.org/api/5/function/hook_update_N needs an update, too. I'd like to see this new numbering scheme used by contrib modules, too. Although I'd change the numbering scheme for contrib modules to:
IMHO a contrib module won't need more than 10 database updates within a minor version. However, if we want to allow more, we certainly can append another # and start counting from '01'.
Changing the numbering scheme for contrib modules allows new co-maintainers of a module to learn which updates were needed in the past and more importantly, for which version. You don't know that by looking at e.g.
module_update_13
.Comment #11
Dries CreditAttribution: Dries commentedThis patch needs to be re-rolled/updated against HEAD it seems -- there are some updates missing.
Comment #12
webernet CreditAttribution: webernet commentedRerolled with update 2007/6007.
Comment #13
Dries CreditAttribution: Dries commentedThanks! Committed to CVS HEAD.
Comment #14
sunWhat about my proposal in #10? Shall I open another issue for that?
We encourage module maintainers to join forces with others, but the code of many contrib modules is in a out-dated state. So the rule to continuously count module updates beginning from 1 turns upgrading and co-maintaining of contrib modules into a pain.
Comment #15
Zen CreditAttribution: Zen commentedMissed a spot.
Comment #16
Zen CreditAttribution: Zen commentedAnd for 5...
I've also removed all the trailing comments which are irrelevant for the 5 branch.
-K
Comment #17
Crell CreditAttribution: Crell commented@sun: That's a documentation issue, so yes I'd say submit it as a new issue. That said, I like the idea of an established, good numbering standard. :-)
Comment #18
sunCreated an offshoot for the proposed numbering scheme of contrib modules: http://drupal.org/node/136078
Comment #19
dwwboth #15 and #16 are RTBC. thanks, zen. i was worried at first by the comment for #16, since i thought you were proposing to re-number the 5.x updates to match the convention, too. luckily, you're just cleaning up some comments. phew! ;)
Comment #20
Dries CreditAttribution: Dries commentedCommitted to CVS HEAD. Thanks!
Comment #21
(not verified) CreditAttribution: commented