From: Jeffrey Forman <jforman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: gentoo-core@lists.gentoo.org
Subject: Re: [gentoo-dev] TESTREQUEST bugs.g.o upcoming upgrade
Date: Wed, 16 Nov 2005 15:05:41 -0500 [thread overview]
Message-ID: <1132171541.29027.22.camel@sixthstreet.formanonline.com> (raw)
In-Reply-To: <1132168160.29030.19.camel@sixthstreet.formanonline.com>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
On Wed, 2005-11-16 at 14:09 -0500, Jeffrey Forman wrote:
> Users and Dev's Alike,
>
> With the past release of bugzilla 2.20, it is once again time to upgrade
> our bugzilla (http://bugs.gentoo.org) to the latest release. I have been
> working on getting our test installation (http://bugstest.gentoo.org) up
> to standards of our current bugzilla, implementing patches and other
> customizations to it. Now I need the general population to login, test
> it, and alert me of any show stopping issues.
I want to thank the astute dev jkt for alerting me to the fact that
HTTPS://BUGS.GENTOO.ORG is NOT the test installation. Bugstest is ONLY
available via standard http, NOT https.
Live install:
http://bugs.gentoo.org
https://bugs.gentoo.org
Test install (this is what I would like users/devs to test)
http://bugstest.gentoo.org
Sorry about any possible confusion that might have caused,
Jeffrey
--
-----------------------
Jeffrey Forman
Gentoo Infrastructure
Gentoo Release Engineering
Bugs.Gentoo.org Administrator
jforman@gentoo.org
-----------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-16 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 19:09 [gentoo-dev] TESTREQUEST bugs.g.o upcoming upgrade Jeffrey Forman
2005-11-16 20:05 ` Jeffrey Forman [this message]
2005-11-17 10:25 ` [gentoo-dev] Re: [gentoo-core] " Henrik Brix Andersen
2005-11-17 11:32 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1132171541.29027.22.camel@sixthstreet.formanonline.com \
--to=jforman@gentoo.org \
--cc=gentoo-core@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox