public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [ANNOUNCE] PostgreSQL 8.3.1, 8.2.7 Update Release
Date: Wed, 26 Mar 2008 11:50:31 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
On Tue, 2008-03-18 at 15:31 -0700, Josh Berkus wrote:
> > These links are clearly wrong. Please at least try to click on them
> > before you post them.
Sorry for not getting back to you earlier on this. The email ended up in
the grayzone that is "deal with this later"-emails...
> I did actually run the announcement past 16 people, none of whom caught the
> error. However, since they weren't web people, nobody looked at the
> links. For some reason, the core web team was booted off -packagers,
> something I was unaware of, so I didn't know they'd gone unexamined.
I think that was by mistake really.
> Unfortunately, I don't have a composer for e-mail which allows me to "click
> on" the links; so if I forget a "cut & paste" test for some of the links
Wow, such mail programs even exist? :-) I can even do that through mutt
on the commandline :-P
> they don't get fixed. Oddly, I did actually check & fix the ones on
> wwwmaster, but those didn't save, apparently?
Maybe we fixed them at the very same time? There is no locking for edits
on that page, so if you started editing it and I also started editing it
before you saved, I got the non-fixed version.
> Anyway, we obviously need the core web team (you, Robert, Stefan) in the
> review lineup since nobody else checks things like links. What's the best
> way to do that?
A good start is probably to add "verify all web links" to the release
checklist? Doesn't have to be a core web guy to do that - it just
requires someone with a browser...
//Magnus
view thread (23+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: [ANNOUNCE] PostgreSQL 8.3.1, 8.2.7 Update Release
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox