Hi! I would propose to: - search for fulltime Bugzilla administrator and his deputies before migration - they will be responsible for updating and managing installation - consider sending out explanation before, during and after the migration to all LO product reporters, people on cc lists - draft complete FAQ about the rationale - change password for all migrated users and include reset password link in welcome message - all personal searches, settings, tags, collected new chart data etc. should stay intact - migrate to latest stable Bugzilla - to receive new features from day one. Currently it is 4.4.1 (or at least update to latest used branch version - atm it is 4.2.7). - not enabling e-mail gateway - enabling whining system (it is half enabled at FDO) - put the source code of our Bugzilla into repository, as it will be modified and customized for sure (preferably by extensions system and not direct code changes) - setup test install based on latest unstable Bugzilla code for experiments - write a draft of new security and build-in features' use settings of new install - probably using https://wiki.documentfoundation.org/How_to_Improve_Bugzilla and https://wiki.documentfoundation.org/QA-ImprovingBugzilla - consider to build-in BSA into Bugzilla as guided template - example https://bugs.freedesktop.org/enter_bug.cgi?product=LibreOffice&format=guided%E2%80%8E&bug_status=UNCONFIRMED Best regards.
-- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-LibreOffice-Bugzilla-migration-Proposal-tp4082184p4082225.html Sent from the QA mailing list archive at Nabble.com. _______________________________________________ List Name: Libreoffice-qa mailing list Mail address: [email protected] Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
