updated pages that mention bugzilla in one way or another

development/git.md

@@ -149,7 +149,7 @@ and it'll tell you:
 Switched to a new branch 'welcome'
 ```
 
-If you have filed a bug on [Bugzilla](/development/issues), you could name your new branch _bugXXXX_ where XXXX is the number of the bug. If you have filed an issue on [GitHub](/development/issues), you could name your new branch _issueXXXX_ with the number. This helps linking your code suggestions to the discussion on that specific bug or issue.
+If you have filed an issue on [GitHub](/development/issues), you could name your new branch _issueXXXX_ with the number; this helps linking your code suggestions to the discussion on that specific bug or issue. If you have not filed an issue yet, just give the new branch a short name that refers to the things you want to change.
 
 ### 4. Add and edit files
 

development/integration.md

@@ -78,11 +78,11 @@ We used the DCCN [download server](https://download.fieldtriptoolbox.org/) to di
 
 ## Bugzilla - obsolete
 
-In the past we used [Bugzilla](http://www.bugzilla.org) as an "issue tracker". This allows to maintain and distribute to-do lists and supports the follow up communication with users that report problems or suggestions. Our bugzilla server is still online for reference and can be found at <http://bugzilla.fieldtriptoolbox.org>.
+In the past we used [Bugzilla](https://www.bugzilla.org) as an "issue tracker" to maintain to-do lists, distribute work, and to support follow-up communication with users. Our bugzilla server has been discontinued in 2024. The archived bug reports and discussions are still available on <http://bugzilla.fieldtriptoolbox.org>.
 
 ## Dokuwiki - obsolete
 
-In the past we used [dokuwiki](http://dokuwiki.org/) as the CMS system for our website.
+In the past we used [dokuwiki](http://dokuwiki.org/) as the CMS system for our website. In 2018 we switched to Jekyll and GitHub.
 
 ## SVN - obsolete
 
@@ -106,7 +106,7 @@ We used to maintain a copy of the SVN repository with the software on [SourceFor
 
 ## Facebook - obsolete
 
-We used <http://facebook.com/fieldtriptoolbox> to announce events and to post photos and messages that relate to the social interaction between developers and users. The Facebook page is **not** used to provide support. In the past we also listed people who like our Facebook page on the start page. or linked in news items to photos from Facebook albums. Due to privacy concerns we stopped using FaceBook.
+We used <http://facebook.com/fieldtriptoolbox> to announce events and to post photos and messages that relate to the social interaction between developers and users. The Facebook page was never used to provide support. In the past we also listed people who like our Facebook page on the start page, or linked from news items to photos in Facebook albums. Due to privacy concerns we stopped using FaceBook.
 
 ## Twitter - obsolete
 

development/issues.md

@@ -51,7 +51,3 @@ Please create a small test script and a piece of data that are both as small and
 If there is a chance of the bug being platform dependent, please also specify the platform (Windows, macOS, Linux), the version of your operating system (Windows 10, Redhat 7.2, High Sierra, ...) and the version of MATLAB that you are using.
 
 Example data (e.g., your MATLAB workspace) that helps to pinpoint a specific issue can be uploaded to the GitHub server as an attachment. This only works for relatively small files. If the data that you want to share is too large, please use a file hosting service as explained [here](/faq/how_should_i_send_example_data_to_the_developers).
-
-## Issues on bugzilla
-
-In the past we used our own [Bugzilla](http://bugzilla.fieldtriptoolbox.org) server for tracking the development and issues, but we have moved over to [GitHub issues](https://github.com/fieldtrip/fieldtrip/issues). The bugzilla server is still available at <http://bugzilla.fieldtriptoolbox.org> for reference to documentation of previous issues.

development/testing.md

@@ -9,7 +9,7 @@ redirect_from:
 
 To make sure everything works correctly, we use [regression testing](https://en.wikipedia.org/wiki/Regression_testing). This way, we can be confident that when we add, modify, or remove a function, we won't break the existing ones. Testing also helps us find and fix any issues early on, ensuring that FieldTrip functions smoothly for all users. We use nightly testing as part of the [release](/development/releasing) procedure.
 
-FieldTrip is a toolbox with many functions, designed to be compatible with each other. This means that one function often relies on the output of another function. Functions are categorized as [high, low-level, or private](https://www.fieldtriptoolbox.org/development/architecture/#high-level-low-level-and-private-functions), with high-level functions depending on low-level and private functions. The regression testing mainly focusses on high- and low-level functions that users can call from their analysis scripts. 
+FieldTrip is a toolbox with many functions, designed to be compatible with each other. This means that one function often relies on the output of another function. Functions are categorized as [high, low-level, or private](https://www.fieldtriptoolbox.org/development/architecture/#high-level-low-level-and-private-functions), with high-level functions depending on low-level and private functions. The regression testing mainly focusses on high- and low-level functions that users can call from their analysis scripts.
 
 ## How are the tests organized in FieldTrip?
 
@@ -34,7 +34,7 @@ If you suspect a problem with the FieldTrip code, the best way to resolve it is
 {% include markup/end %}
 
 {% include markup/info %}
-It is important to keep in mind that the test files or directories related to a GitHub issue or Bugzilla report are named after the GitHub issue or Bugzilla number.
+Test data that is related to a specific GitHub or Bugzilla issue is named correspondingly, for example `bugXXX.mat` or `issueXXX.mat`.
 {% include markup/end %}
 
 ### Failed and obsolete tests

faq/how_should_i_send_example_data_to_the_developers.md

@@ -1,6 +1,6 @@
 ---
 title: How should I share example data with the email list or developers?
-tags: [faq, email, development, bugzilla]
+tags: [faq, email, development, git]
 ---
 
 # How should I share example data with the email list or developers?