Why do we use such a hard-to-figure-out system of naming upgrades? The numbering system makes it hard for a newbie like myself to figure which update I need to run. Instead of 64,65,66,... wouldn't it make more sense to an end user to say "4.1.0 > 4.1.1, 4.3.1 > 4.3.2, or something like that? If I just pick the last one, is it inclusive of all updates? If I click on one that's too early, will I lose data?

Why is there no "2003-xx-08: first update since Drupal 4.3.0 release" => "update_58"?

If I installed 4.3.0 and then installed 4.3.2 which do I do? I just did the last one because I wasn't sure.

Thanks!

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

There are only update headers for those versions, which need update headers... As it was written in the anouncements too, there has been no DB changes between 4.3.x versions, so there are no required updates...

Goba

Anonymous’s picture

(not verified) commented

It said there was no DB changes, but how does a newbie know what the update.php file do? I am competant enought to open it and see, but other may not be. It just seems more confusing than it needs to be. The update.php should be more self explanitory than it currently is. my $.02.

Status: confusing, by design. Shouldnt the last update (70?) be 4.3.0? Or is that 4.31?

Perhaps I the only one that thinks it's confusing? Wouldn't be the first time. :)

Vincent