[Libreoffice-qa] LibreOffice Bugzilla (migration) Proposal

[bfoman]

Robinson Tryon wrote
>> - consider sending out explanation before, during and after the migration
>> to
>> all LO product reporters, people on cc lists
> I think notification before the migration is prudent, but I'm hesitant
> to send them emails both during and after migration, as they might
> perceive that as us spamming them.

Hi!
As I work in LO's Bugzilla everyday I would like to know when the migration
process will start, then informed that it started and Bugzilla will be
unavailable, informed that it finished and FDO is disabled, greeted in new
system with password change link. I do not consider it spam.

Robinson Tryon wrote
>> - all personal searches, settings, tags, collected new chart data etc.
>> should stay intact
> If we clone the instance and stay on the same version of Bugzilla, I
> believe all of this data will transfer correctly.

Not all data is in database dump - see
https://wiki.mozilla.org/Bugzilla:Move_Installation

Robinson Tryon wrote
>> - 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).
> If we update Bugzilla at the same time as we perform the migration,
> that may cause breakage, and it may be difficult to determine what
> step broke what part of the system. I really want to upgrade to the
> latest and greatest Bugzilla, too, but I suggest that we wait a week
> or so after the initial migration before we consider any upgrades or
> tweaks, to make the migration go as smoothly as possible.

So please ask for FDO upgrade to 4.2.7 before migration as it is currently
on Bugzilla 4.2.3, which have known security vulnerabilities and should be
updated ASAP - http://www.bugzilla.org/security/ 
Best regards.




--
View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-LibreOffice-Bugzilla-migration-Proposal-tp4082184p4082305.html
Sent from the QA mailing list archive at Nabble.com.