diff options
| author | jocuri%softhome.net <> | 2004-12-14 11:11:29 +0100 |
|---|---|---|
| committer | jocuri%softhome.net <> | 2004-12-14 11:11:29 +0100 |
| commit | 025df7c70f82579cc59e52cb576a0db2701d38c9 (patch) | |
| tree | 7ac2851bf79ff1798ea2ab7d84692fd0121e9c3e /docs | |
| parent | 982de31eeb8549a4c1d60890d788b9dd54fbc507 (diff) | |
| download | bugzilla-025df7c70f82579cc59e52cb576a0db2701d38c9.tar.gz bugzilla-025df7c70f82579cc59e52cb576a0db2701d38c9.tar.xz | |
Documentation patch for bug 262268: Document in release notes that flags should not contain spaces and indicate checksetup.pl tool for upgrading; patch by justdave@bugzilla.org updated by Nick.Barnes@pobox.com, r=vladd.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/rel_notes.txt | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/rel_notes.txt b/docs/rel_notes.txt index 3c53d609d..e9302db1f 100644 --- a/docs/rel_notes.txt +++ b/docs/rel_notes.txt @@ -264,6 +264,24 @@ Miscellaneous Improvements What's Changed? *************** + +Flag names +---------- + +Prerelease versions of Bugzilla 2.17 and 2.18 inadvertantly allowed +commas and spaces in the names of flags, which due to the way they're +processed, caused lots of internal havoc if you named flags to have +any commas or spaces in them. Having commas or spaces in the names +can cause errors in the notification emails and in the bug activity +log. The ability to create new flags with these characters has been +removed. If you have any existing flags that you named that way, +running checksetup will attempt to automatically rename them by +replacing commas and spaces with underscores. + + +Rules for changing fields +------------------------- + There have been some changes to the rules governing who can change which fields of a bug report. The rules for Bugzilla version 2.16 and 2.18, along with differences between them, are listed below. Bear in mind that there are other |