[SM-Grimoire-Bugs] [Bug 8736] rename UPDATED to PATCHLEVEL

bugzilla-daemon at bugs.sourcemage.org bugzilla-daemon at bugs.sourcemage.org
Wed Apr 27 16:44:39 EDT 2005


acedit at armory.com changed:

           What    |Removed                     |Added
OtherBugsDependingO|8379                        |
              nThis|                            |
            Summary|UPDATED behaviour is broken |rename UPDATED to PATCHLEVEL

------- Additional Comments From acedit at armory.com  2005-04-27 13:44 -------
as far as I know the ENTERED/CREATED field is only for informational purposes, i
think its unneeded given that we have HISTORY files.

My suggestion has and still is to have two fields, one for general updates and a
seperate one for security updates as in bug 8379. Otherwise I have to parse the
field to figure out if the last update was a security update or if its just a
bugfix. Its just simpler. more extensible, and a lot less bug-prone code needs
to be added. Adding a tablet entry is easy, adding code to parse the meaning of
a field is not, but thats really an issue for bug 8379 as to how the fact that
theres been a security update is to be conveyed.

With the exception of the *name* of the updated field this bug is a duplicate of
8060. So the question is, do we want to rename UPDATED to PATCHLEVEL (or
something else). If not, then lets leave this closed this as a duplicate, if you
do want to rename it, then there is work to be done and a new bug should be
filed or this should be re-opened.

Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the SM-Grimoire-Bugs mailing list