> On Nov 9, 2018, at 2:54 PM, Graham Leggett wrote:
>
> On 09 Nov 2018, at 17:51, Stefan Eissing wrote:
>
>> So, the chance is high that releases we do will work for most of you.
>> AND the chance is high that releases might break something for some of you
>> (hopefully a few).
>
> The
On Fri, Nov 9, 2018 at 2:04 PM Graham Leggett wrote:
> On 09 Nov 2018, at 17:51, Stefan Eissing
> wrote:
>
> > So, the chance is high that releases we do will work for most of you.
> > AND the chance is high that releases might break something for some of
> you (hopefully a few).
>
> The chance
On 09 Nov 2018, at 17:51, Stefan Eissing wrote:
> So, the chance is high that releases we do will work for most of you.
> AND the chance is high that releases might break something for some of you
> (hopefully a few).
The chance is very low that releases might break something, and this is done
On 09 Nov 2018, at 10:05, Barry Pollard wrote:
> I do wish Apache would run its own “official” repo to make upgrading to
> latest easier. Don’t have the expertise to help with this and understand it
> was done in the past and given up due to lack of people who did but still
> think it’s a
On Thu, Nov 8, 2018 at 1:48 PM Jim Jagielski wrote:
> I have a semi-working implementation that I'll be committing to trunk in a
> bit...
I'm confused. Semi-working would seem to be orthoganal to keeping trunk in
a releasable state, but it depends on what you mean. But before you commit
a
I clicked send on this note, before I saw the deluge.
What we would not want is to hide closure notices to the cc recipients on
the issue. We would not want to remove bugs@ from the issue itself. And
anyone reconfirming a ticket is not stale is going to the bugs@
notification list.
My only
On Fri, Nov 9, 2018 at 2:03 AM Ruediger Pluem wrote:
>
> On 11/08/2018 09:23 AM, Micha Lenk wrote:
> > Hi all,
> >
> > I have a customer asking about whether the SSL handshake can be made to
> fail in case the SNI from the "Client Hello"
> > message doesn't match at all any server name of the
*to thank* (oh my)
> Am 09.11.2018 um 16:51 schrieb Stefan Eissing :
>
> I would like all who replied in this thread for their feedback. It is good
> to hear that many are looking forward to frequent releases, especially as
> the field we are all working in continues to develop.
>
> Apache
I would like all who replied in this thread for their feedback. It is good
to hear that many are looking forward to frequent releases, especially as
the field we are all working in continues to develop.
Apache httpd is a server capable of many things, all configurable in various
ways and even
+1 (as one of the 99.99%)
In particular: "I'd prefer frequent releases and honest changelogs."
-Original Message-
From: Niklas Edmundsson
Reply-To: "dev@httpd.apache.org"
Date: Friday, November 9, 2018 at 8:10 AM
To: "dev@httpd.apache.org"
Subject: [**EXTERNAL**] Re: 2.4.38
I usually don't like top-posts, but I just want to say that I agree
completely with everything Barry stated below.
If you as an admin want an easy life, use the distro version.
If you have good reasons to build yourself simply suck it up and
accept the maintenance pain (which it is, since
Hi Bill,
On Wed, Nov 7, 2018 at 10:22 PM William A Rowe Jr wrote:
>
> Mass update completed.
Would it be possible now to have buz send us an email on bugs@ (and
possibly only bugs@) for tickets still in the "open" field (i.e. not
resolved/invalid/...)?
For those of us who track bz but by
Disagree. My 2 cents as a watcher, administrator and user:
1/ they have better things to do
Then don’t take the release! If a release contains security patches (so they
should take it), then I don’t see how hiding the issue by holding back the
release helps.
2/ it gives impression of
On 11/08/2018 09:23 AM, Micha Lenk wrote:
> Hi all,
>
> I have a customer asking about whether the SSL handshake can be made to fail
> in case the SNI from the "Client Hello"
> message doesn't match at all any server name of the configured virtual hosts.
> E.g. consider a setup like this
>
14 matches
Mail list logo
