Bommels05/Mozilla
Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updates from review comments from Ryan.

Browse Source 
git-svn-id: svn://10.0.0.236/trunk@265737 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
bzrmirror%bugzilla.org 2014-12-03 22:35:04 +00:00
parent d3315e9950
commit cb7e38eca4
5 changed files with 34 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
mozilla/webtools/bugzilla/.bzrrev
View File

@ -1 +1 @@
9263
9264

2
mozilla/webtools/bugzilla/.gitrev
View File

@ -1 +1 @@
92e11c7c13e167cfe7ba13ec415fd636c290b4ae
645d58e1763156d24c512c9ecaa0222ef5f4c795

1
mozilla/webtools/bugzilla/docs/en/rst/upgrading/index.rst
View File

@ -13,3 +13,4 @@ Upgrading Bugzilla
migrating-from-cvs
migrating-from-a-tarball
upgrading-with-a-tarball
upgrading-customizations

19
mozilla/webtools/bugzilla/docs/en/rst/upgrading/overview.rst
View File

@ -23,9 +23,9 @@ Before Git, we used to use Bazaar and, before that, CVS. If your installation
of Bugzilla consists of a checkout from one of those two systems, you need to
upgrade in three steps:
1. upgrade to the latest point release of your current Bugzilla version;
2. move to Git while staying on exactly the same release;
3. upgrade to the latest Bugzilla using the instructions for :ref:`upgrading-with-git`.
1. Upgrade to the latest point release of your current Bugzilla version.
2. Move to Git while staying on exactly the same release.
3. Upgrade to the latest Bugzilla using the instructions for :ref:`upgrading-with-git`.
See :ref:`migrating-from-bazaar` or :ref:`migrating-from-cvs` as appropriate.
@ -38,12 +38,15 @@ If you aren't sure which of these categories you fall into, to find out which
version control system your copy of Bugzilla recognizes, look for the
following subdirectories in your root Bugzilla directory:
* :file:`.git`: you installed using Git - follow :ref:`upgrading-with-git`
* :file:`.bzr`: you installed using Bazaar - follow :ref:`migrating-from-bazaar`
* :file:`CVS`: you installed using CVS - follow :ref:`migrating-from-cvs`
* none of the above: you installed using an old tarball - follow
:ref:`migrating-from-a-tarball`
* :file:`.git`: you installed using Git - follow :ref:`upgrading-with-git`.
* :file:`.bzr`: you installed using Bazaar - follow :ref:`migrating-from-bazaar`.
* :file:`CVS`: you installed using CVS - follow :ref:`migrating-from-cvs`.
* None of the above: you installed using an old tarball - follow
:ref:`migrating-from-a-tarball`.
It is also possible, particularly if your server machine does not have and
cannot be configured to have access to the public internet, to upgrade using
a tarball. See :ref:`upgrading-with-a-tarball`.
Whichever path you use, you may need help with
:ref:`upgrading-customizations`.

20
mozilla/webtools/bugzilla/docs/en/rst/upgrading/upgrading-customizations.rst Normal file
View File

@ -0,0 +1,20 @@
.. _upgrading-customizations:
Upgrading a Customized or Extended Bugzilla
###########################################
If your Bugzilla has been customized or uses extensions, you will need to
make your customizations or extensions work with your new version of Bugzilla.
If this is the case, you are particularly strongly recommended to do a test
upgrade on a test system and use that to help you port forward your
customizations.
If your extension came from a third party, look to see if an updated version
is available for the version of Bugzilla you are upgrading to. If not, and
you want to continue using it, you'll need to port it forward yourself.
If you are upgrading from a version of Bugzilla earlier than 3.6 and have
extensions for which a newer version is not available from an upstream source,
then you need to convert them. This is because the extension format changed
in version 3.6. There is a file called :file:`extension-convert.pl` in the
:file:`contrib` directory which may be able to help you with that.