From mcote at mozilla.com Tue Jul 8 01:59:34 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 07 Jul 2014 21:59:34 -0400 Subject: REST API docs updated Message-ID: If you are using the BzAPI proxy server for your Bugzilla installation, note that the documentation has moved to https://wiki.mozilla.org/Bugzilla:BzAPI. The former location of BzAPI docs, https://wiki.mozilla.org/Bugzilla:REST_API, now focusses on the new native REST API available in the upcoming Bugzilla 5.0 release. There are redirects in place for all BzAPI subpages. Since the root page still exists but with new content, there is no redirect there, but there is a note at the top for those looking for the BzAPI docs. Mark _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From theycallmefish at gmail.com Wed Jul 23 14:57:59 2014 From: theycallmefish at gmail.com (Ryan Wilson) Date: Wed, 23 Jul 2014 07:57:59 -0700 (PDT) Subject: Bugzilla Implementations That Use Testopia Message-ID: <0aa4ee3c-ed13-4c88-994b-c67cea0cd865@googlegroups.com> I've been actively working on upgrading the codebase of Testopia. As one of my big projects is to upgrade the framework behind Testopia (which is currently running ext JS 3), I'm looking to get as many eyes on these changes as possible. It may be a little while before "phase one" of this upgrade is ready for testing, but I'd like to compile a list of Bugzilla implementations that use Testopia, so that I can get as many active user testers as possible. Please respond to this message if you are interested. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Wed Jul 23 18:41:01 2014 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 23 Jul 2014 19:41:01 +0100 Subject: Documentation: Next Steps Message-ID: I'm pleased to say that all of the contributors to Bugzilla's documentation have either been tracked down and agreed to the Creative Commons relicensing, or their contributions have been evaluated and removed if necessary (that turned out to be only two one-paragraph removals). So we are ready to move forward! I have written a "Contents Page" for how I am planning to reorganize and structure the documentation. Some of this will be rearranged from the old stuff, some will be imported from elsewhere, and some will be new. Comments on the structure are welcome: https://wiki.mozilla.org/Bugzilla:Documentation_Plan Particularly useful are comments like: "You need a section about X", or "That's not a logical order because Y". There's no need at this stage to list things that need mentioning that would occupy less than a section, as long as you an see a logical place where they could go. Big picture stuff at the moment. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Jul 25 15:20:43 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 25 Jul 2014 16:20:43 +0100 Subject: Questions for docs, part 1 Message-ID: <4_mdne_-KuhW6E_OnZ2dnUVZ_uednZ2d@mozilla.org> Part 1 because I suspect there will be more of these :-) * Under what circumstances do people need to use a tarball to install or upgrade? Is it only if they have no network connection? * Should we recommend using Git (over tarballs) wherever possible? * Do our tarballs come with VCS information? Since when? If so, does that mean everyone actually has a VCS checkout, and can upgrade using a VCS method? * I'm writing a Quick Start guide - a simple 1, 2, 3 to get Bugzilla up and running using Ubuntu 14.04 LTS, MySQL and Apache. Do I describe Ubuntu Server (supported for longer) and a console install, or Ubuntu Desktop so they can use a graphical text editor and web browser? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From sgreen at redhat.com Sun Jul 27 10:51:01 2014 From: sgreen at redhat.com (Simon Green) Date: Sun, 27 Jul 2014 20:51:01 +1000 Subject: Questions for docs, part 1 In-Reply-To: <4_mdne_-KuhW6E_OnZ2dnUVZ_uednZ2d@mozilla.org> References: <4_mdne_-KuhW6E_OnZ2dnUVZ_uednZ2d@mozilla.org> Message-ID: <53D4D995.1000405@redhat.com> On 26/07/14 01:20, Gervase Markham wrote: > * Under what circumstances do people need to use a tarball to install > or upgrade? Is it only if they have no network connection? I would expect the vast majority of user would use the tarball over VCS. It's easier to get a gz file than it is to install git, and try and figure out the right command. I'm basing this on the assumption that most companies that use Bugzilla have sysadmins whos skills can be described as beginner to immediate. > * Should we recommend using Git (over tarballs) wherever possible? Definitely make a note in the guide, but I think for the lowest barrier to entry, the quick start guide should use the .tar.gz file. Sysadmins know what to do with that file :) > * Do our tarballs come with VCS information? Yes, .bzr exists in these directories ( http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-4.4.5.tar.gz at least) Surprisingly, 4.5.5 also has a .bzr directory even though there won't be a 5.0 bzr repo, IIRC. dkl or mcote will be able to clarify. > If so, does > that mean everyone actually has a VCS checkout, and can upgrade using > a VCS method? Yes. > * I'm writing a Quick Start guide - a simple 1, 2, 3 to get Bugzilla up > and running using Ubuntu 14.04 LTS, MySQL and Apache. Do I describe > Ubuntu Server (supported for longer) and a console install, or Ubuntu > Desktop so they can use a graphical text editor and web browser? Ubuntu Server LTS. I'm going to assume even a beginner sysadmin knows how to edit a file from the command line. -- Simon Green Software Engineer Red Hat Asia Pacific Pty Ltd From damien.nozay at gmail.com Sun Jul 27 16:18:22 2014 From: damien.nozay at gmail.com (Damien) Date: Sun, 27 Jul 2014 09:18:22 -0700 Subject: Questions for docs, part 1 In-Reply-To: <53D4D995.1000405@redhat.com> References: <4_mdne_-KuhW6E_OnZ2dnUVZ_uednZ2d@mozilla.org> <53D4D995.1000405@redhat.com> Message-ID: On Sun, Jul 27, 2014 at 3:51 AM, Simon Green wrote: > On 26/07/14 01:20, Gervase Markham wrote: > > * Under what circumstances do people need to use a tarball to install > > or upgrade? Is it only if they have no network connection? > > I would expect the vast majority of user would use the tarball over VCS. > It's easier to get a gz file than it is to install git, and try and > figure out the right command. I'm basing this on the assumption that > most companies that use Bugzilla have sysadmins whos skills can be > described as beginner to immediate. > In my case, we have sysadmins, and we have a "tools" team. Tools team maintains a git clone of bugzilla with a branch that contains all customizations and extensions needed. They know how to spell git. IMHO, nobody would use a tarball unless it contains their customizations; or they also maintain a bunch of patches somewhere that they can apply. > > > * Should we recommend using Git (over tarballs) wherever possible? > > Definitely make a note in the guide, but I think for the lowest barrier > to entry, the quick start guide should use the .tar.gz file. Sysadmins > know what to do with that file :) > To me, someone who doesn't know what a VCS is, is not a team player. Most concepts are portable. https://try.github.io/ http://gitimmersion.com/ > > > * Do our tarballs come with VCS information? > > Yes, .bzr exists in these directories ( > http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-4.4.5.tar.gz at > least) > > Surprisingly, 4.5.5 also has a .bzr directory even though there won't be > a 5.0 bzr repo, IIRC. dkl or mcote will be able to clarify. > > > If so, does > > that mean everyone actually has a VCS checkout, and can upgrade using > > a VCS method? > > Yes. > > > * I'm writing a Quick Start guide - a simple 1, 2, 3 to get Bugzilla up > > and running using Ubuntu 14.04 LTS, MySQL and Apache. Do I describe > > Ubuntu Server (supported for longer) and a console install, or Ubuntu > > Desktop so they can use a graphical text editor and web browser? > > Ubuntu Server LTS. I'm going to assume even a beginner sysadmin knows > how to edit a file from the command line. > The 2 sysadmins I have to work with have no love for ubuntu (e.g. config files in a totally different place than other distros.). They are from a RHEL/CentOS background. I think any documentation better than none is a great idea though. Server over desktop, clearly. Sysadmins can have ubuntu desktop on their own machine; they can do scp if they can't work with vim or nano. I got a page for a different stack: https://wiki.mozilla.org/Bugzilla:Installation_with_nginx see if there is anything of interest there. Regards, Damien. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From dkl at mozilla.com Sun Jul 27 17:54:42 2014 From: dkl at mozilla.com (David Lawrence) Date: Sun, 27 Jul 2014 13:54:42 -0400 Subject: Questions for docs, part 1 In-Reply-To: <53D4D995.1000405@redhat.com> References: <4_mdne_-KuhW6E_OnZ2dnUVZ_uednZ2d@mozilla.org> <53D4D995.1000405@redhat.com> Message-ID: <53D53CE2.9080109@mozilla.com> On 07/27/2014 06:51 AM, Simon Green wrote: >> * Do our tarballs come with VCS information? > > Yes, .bzr exists in these directories ( > http://ftp.mozilla.org/pub/mozilla.org/webtools/bugzilla-4.4.5.tar.gz at > least) > > Surprisingly, 4.5.5 also has a .bzr directory even though there won't be > a 5.0 bzr repo, IIRC. dkl or mcote will be able to clarify. It does as the scripts used to generate the tarballs still pull from BZR and not yet git. We still mirror git/bugzilla/master in git to bzr/bugzilla/trunk so not a problem until we turn that off. dkl -- David Lawrence dkl at mozilla.com