如何将自定义迁移到较新版本的 Bugzilla
在哪里可以找到有关将自定义页面从当前安装的 Bugzilla 迁移到最新版本 Bugzilla 3.6 的信息？
我正在尝试快速了解如何将所有部分组合在一起以使 Bugzilla 正常工作。我在 VHD 中安装了 3.6 的有效安装（我们在 Windows 上运行）。接下来，我只需要弄清楚如何推进我们的定制。
谢谢！
Where can I find information on migrating our customized pages from our current install of Bugzilla to the latest, Bugzilla 3.6?
I'm trying to get up to speed on how all of of the pieces come together to make Bugzilla work. I have a working installation of 3.6 in a VHD (we are running on Windows). Next, I just need to figure out how to move our customizations forward.
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您必须考虑如何继续推进以下几类内容：
如果您直接对代码进行更改，那么只需将 3.6 合并到源代码树中即可。这可能会产生许多冲突，并且可以通过代码考古学来找出解决方案。
以此为契机，赶上代码钩子潮流，这样您就可以对 Mozilla 源代码进行最小程度的（希望没有）更改，这将使未来的升级变得更加容易。
如果您一直在
template/en/default中更改模板，那么这与上面的情况几乎相同 - 您需要合并 Mozilla 的更改。如果您已将自定义项放入template/en/custom中，那么您需要根据对默认值的相应更改来评估是否需要进行任何更改。3.6 在扩展系统中引入了一些新的架构。您可能会像我一样想深入研究此页面：
http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/Extension.html
您可能还想查看 3.6 的升级说明：
http://www.bugzilla.org/releases/3.6/release-notes。 html#v36_upgrading
最后，在我手动转换扩展之前我没有注意到，有一个脚本可以为您完成此操作！
http://www.bugzilla.org/ docs/3.6/en/html/api/contrib/extension-convert.html
您可能会发现访问 irc.mozilla.org 上的 #mozwebtools 很有帮助。那是所有酷炫的 Bugzilla 孩子们闲逛的地方！他们很乐意根据您的喜好进行定制。
There are several categories of stuff that you must consider how to move forward:
If you've been making changes to the code directly, it should be just a matter of merging 3.6 onto your source tree. This can create a number of conflicts, and it can be an exercise in code archaeology to figure out the resolution.
Use this as an opportunity to jump on the code hooks bandwagon so that you have minimal (hopefully no) changes to Mozilla's source, which will make future upgrades a lot easier.
If you've been changing templates in
template/en/default, then that's pretty much the same as the case above - you need to merge in Mozilla's changes. If you've been putting customizations intotemplate/en/custom, then you need to evaluate whether you need to make any changes based on corresponding changes to the defaults.3.6 introduces some new architecture in the extension system. You'll probably want to dig into this page as much as I have:
http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/Extension.html
You'll probably also want to look at the upgrading notes for 3.6:
http://www.bugzilla.org/releases/3.6/release-notes.html#v36_upgrading
Finally, what I didn't notice until I had manually converted an extension, there's a script that will do it for you!
http://www.bugzilla.org/docs/3.6/en/html/api/contrib/extension-convert.html
You may find it helpful to visit #mozwebtools on irc.mozilla.org. That's where all the cool Bugzilla kids hang out! They're happy to chat up customizations to your heart's content.