a user preference to allow users to receive minor bug updatesĭue to the way bugmail is generated, this is trickier than it first seems. an admin parameter for groups allowed to use this feature support for a parameter to the bug.update api call a similar checkbox on the bulk bug update page Minor updates, as well as the results of this checkbox i think it's important that the wording here states that it's for "this is a minor update (do not send email)" a checkbox on show_bug under the comment: In order for a bug changer to tag an update as "minor" to not trigger bugmail we require: As we will not add new features, this means forgoing password complexity checks which is actually a good thing as passwdqc rejects perfectly fine randomly generated passwords and people hate it.While this has been filed a large number of times, i'm opening a new bug to track work following consensus reached in the last bugzilla meeting that this feature is one that we want to implement now in bugzilla.Mostly this is Data::Password::passwdqc.If possible, some dependencies that are difficult to package (or not maintained well) must be dropped.There are complications involving the db schema and how email works that are TBD.This is mainly a matter of reversing the “multiple aliases” support that was added in 5.0 but is not going to be present in 6.0.Ensure a migration (schema migration) is possible from 5.0 to 6.0.Remove the Bugzilla::Report::* classes as those are specific reporting features of BMO that.Delete Mozilla-specific code and branding.We know the “6.0” release will work, because we know works every day. I’m working on the second version of this, but the gist here is very accurate. Since the last meeting, I came up with this (rough) release plan. I hope to finish the parser this week, and have the patch in review over the weekend (Feb 8/Feb 9). While the parser is over 300 lines, it means the overall patch is localized to one new file and a minor change to Bugzilla::DB. It takes a SQL expression and then quotes all column and table references. This approach is promising, and may result in a bit of reusable code useful to other Perl applications that have forbidden column or table names that used to work.Īt the time of writing, I have written a mysql expression parser that can handle nearly every SQL expression used in Bugzilla. There are cases where an ORDER BYmust be quoted, for instance.īecause the patch set to quote all occurrences of is already quite large, I began exploring a more comprehensive fix on February 3rd. The problems remaining are that it is there are many places where snippets of sql are generated and it is non-obvious where and when to quote them. completes and large parts of the code work on MySQL 8.Fixing Safe.pm bug in latest perl (the latest perl has a bug with Safe and Bugzilla must work around it).SQLite works again (sqlite was broken and is untested in the 5.2 branch).MySQL 8 regexp compatibility (it turns out our default emailregexp wasn’t compatible with MySQL 8).Here’s a list of things that are ready in the 5.2 branch: I had desired to be able to release that this week, but this has fallen short because of unforeseen complications. The 5.2 UpdateĪt the behest of justdave I’ve focused my attention on the quality of life release (5.2). MySQL 8 compatibility, and compatibility with the latest versions of perl.Ī feature-packed release (6.0) which includes the UX/UI from, based on mojolicious. As you know, we’re working on two fronts in Bugzilla Development:Ī quality-of-life release (5.2) which includes support for utf8mb4,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |