Mailing List Archive

On 23 Jul 2020, at 01:32, Daniel Ruggeri <daniel@bitnebula.com> wrote:

> It's been a while since we've rolled a release and gotten fixes/etc in our community's hands. Apologies for not suggesting this sooner. How about a T&R Friday? That will let vote run through the weekend.

+1.

Regards,
Graham
—

Sure. Go ahead. +1

> On Jul 22, 2020, at 7:32 PM, Daniel Ruggeri <daniel@bitnebula.com> wrote:
>
> Hi, all;
> It's been a while since we've rolled a release and gotten fixes/etc in our community's hands. Apologies for not suggesting this sooner. How about a T&R Friday? That will let vote run through the weekend.
> --
> Daniel Ruggeri

On Thu, Jul 23, 2020 at 1:32 AM Daniel Ruggeri <daniel@bitnebula.com> wrote:
>
> It's been a while since we've rolled a release and gotten fixes/etc in our community's hands. Apologies for not suggesting this sooner. How about a T&R Friday? That will let vote run through the weekend.

+1

Regards;
Yann.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Daniel,

On 7/22/20 19:32, Daniel Ruggeri wrote:
> Hi, all; It's been a while since we've rolled a release and gotten
> fixes/etc in our community's hands. Apologies for not suggesting
> this sooner. How about a T&R Friday? That will let vote run through
> the weekend.

If I clean-up my patch for
https://bz.apache.org/bugzilla/show_bug.cgi?id=64338 is there a chance
it could make it into this release?

I'm super-ignorant about the httpd release process so I apologize if
that's a ridiculous question.

- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl8Z2BUACgkQHPApP6U8
pFiQig/9EoMU1nfImF1hwwMEkJCSmkIY9flImsMzd4yF+apeK8YS1uzA9yLGfGgw
++5FEOEBjNbpZTnQWJ5Lgc3dBIZ9l/Q9Jg5OryaX31JEOoRaTuwHvxx4KTXfJriW
lDCjmoB18N3ze2jNRfRxJuBDbYeDWbluz9lb28qZdkCGwpmUdz5PoS1oNYxu6V3h
AVccJEos0eMdKhfIuVtjcUoZ9gb9+eq4CJwNBeyMOV8tW+vY/Zf00OCy4tTvenE2
HDf+nx7AbnrpTAOJBbrvjXbpYTaWY/NbtRaCQFEGFPYPrv+4k/4tlyn4V+p6LAcQ
Ol03TqE6Q6APAq3BsvgvRUKTVzJdnxfUS6XjaePh4l+q14kF06umPHAUo4DNn0MD
o3hU0LZUpyftklxvkYALMeoNflDXzPw9pkVq+VSYwGLk0/DiqVRvIJsMacr41a/Y
9sm8OWMkK4um/HNhR4USkIhVzsEDsY+bQR1m2f8m50FDXiU+I+AD5Rg9Yt0qwWZ3
TM3FhdFsARp2l9jSucY0cQKz8WYZGGoED5ccRBzOnnKaPePQwwOAQoQcBzoU3tLk
Yre8IAuGN4TvtTp6hViLDDSdEvs6ogmmOIB5RovWE6WGnn6S60D21ySkOca5IKi6
DRaIIx11UspPKRACb8VHmjlhYejlBQ2p/8ZqPxPT+zG40ePLPW0=
=ZoLM
-----END PGP SIGNATURE-----

Hey there, Chris;

   Fair question - and I don't think I have a handy link describing the
flow of patch -> trunk -> STATUS backport proposal -> branch commit ->
release

   Generally speaking, the code goes into trunk and is proposed for
backport into a stable branch via the STATUS file (at the root of the
branch - ex
http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?view=markup).
A lot of times, patches are proposed for discussion/refined and
tweaked/etc before being committed in trunk, which seems to fit the
conversation in your reference BZ item. From there, we need three
committer +1s to backport. Once all three are in place, the proposer (or
release manager) commits the change to the branch. So, for this one, I
think we're not quite ready to incorporate.

P.S.
I hope all is well - long time no chat!

--
Daniel Ruggeri

On 7/23/2020 1:33 PM, Christopher Schultz wrote:
> Daniel,
>
> On 7/22/20 19:32, Daniel Ruggeri wrote:
> > Hi, all; It's been a while since we've rolled a release and gotten
> > fixes/etc in our community's hands. Apologies for not suggesting
> > this sooner. How about a T&R Friday? That will let vote run through
> > the weekend.
>
> If I clean-up my patch for
> https://bz.apache.org/bugzilla/show_bug.cgi?id=64338 is there a chance
> it could make it into this release?
>
> I'm super-ignorant about the httpd release process so I apologize if
> that's a ridiculous question.
>
> -chris

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Daniel,

On 7/24/20 17:36, Daniel Ruggeri wrote:
> Hey there, Chris;
>
> Fair question - and I don't think I have a handy link describing
> the flow of patch -> trunk -> STATUS backport proposal -> branch
> commit -> release
>
> Generally speaking, the code goes into trunk and is proposed for
> backport into a stable branch via the STATUS file (at the root of
> the branch - ex
> http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?view=ma
rkup).
>
>
A lot of times, patches are proposed for discussion/refined and
> tweaked/etc before being committed in trunk, which seems to fit
> the conversation in your reference BZ item. From there, we need
> three committer +1s to backport. Once all three are in place, the
> proposer (or release manager) commits the change to the branch. So,
> for this one, I think we're not quite ready to incorporate.

Sounds reasonable to me.

I'll be pushing to get this back-ported for the next 2.4.x release
since I'm throwing mod_jk completely under the bus at ApacheCon this
year and it's a pretty important missing-feature in mod_proxy.

Thanks,
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAl8bVaEACgkQHPApP6U8
pFjuIRAAnp6Ej0SvbRrS+bCgyDQzoATyycNSTPnYZt7uBKIGmuSXhZXHDgCJw6hs
XdCu9j1/9mJKHK0+PibElEGogFYb6bl7Ncm21wWrV4g70RUW0EJEAKVbEEQN/xA8
1QbnhK6MFtex9eNJcw8AQCKncht6V4foO9GKNbrV4IeJ/1By/3VYPe0mfq2AsHSJ
OnVL4WPvk3mQs7Ct1FMhra5/05tb+tkfA+A4wjLVd3+kR850xJrfsgoTIaBfjH+a
/XoOqhgyc0/9F9dkKNlXh1NUDRfmvHQm8HvNIJWWtfAxG88ksxy3umEwfsZoUeXE
PaSnCvS8GzVuAvoroQ/4vszHPCSMdL13o333H2nc4qDSnTRXuxgW3uxOFZXpRdIT
7Qq4H153AxUQpT0kLlaew8SyMCiK7V/mP0GMlx3UHdPYMl38JdjYlgRGb7YpZ5IX
c4tZ4VUH6/7iLZ4BlG2/es9YdoypsSv06Hx8ZTztYfnbR7pvoYA4t2qWQKrQ+17G
PUGEkGpbFL8LcWxN/nf3fYaoFy8sp3u5kSn7CyCmLetSKjZ32jxToMPJF+Fsk4c7
ULDlvehugffoVgI2Wi/zxqPe+S5XAyWyGzhcfal7MdM67J/Tsc9QDqhNT7kaHAlQ
kcO7WE3HpDohON0DVqz3GcaQo293wXyEPB5b68flsJNbgO55H/A=
=0hj2
-----END PGP SIGNATURE-----

Hi, all;
FYI, I came across an unexpected set of diffs when rebuilding docs before tagging this morning. Haven't forgotten about T&R, but would like to figure out the origin of the docs changes (likely my environment). I've started a conversation on docs@ about what I'm seeing.


On 2020/07/22 23:32:05, Daniel Ruggeri <daniel@bitnebula.com> wrote:
> Hi, all;
> It's been a while since we've rolled a release and gotten fixes/etc in our community's hands. Apologies for not suggesting this sooner. How about a T&R Friday? That will let vote run through the weekend.
> --
> Daniel Ruggeri

> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri <druggeri@apache.org>:
>
> Hi, all;
> FYI, I came across an unexpected set of diffs when rebuilding docs before tagging this morning. Haven't forgotten about T&R, but would like to figure out the origin of the docs changes (likely my environment). I've started a conversation on docs@ about what I'm seeing.

Sorry about your troubles. Do we need to look for someone else doing the RMing or what's your status?

>
>
> On 2020/07/22 23:32:05, Daniel Ruggeri <daniel@bitnebula.com> wrote:
>> Hi, all;
>> It's been a while since we've rolled a release and gotten fixes/etc in our community's hands. Apologies for not suggesting this sooner. How about a T&R Friday? That will let vote run through the weekend.
>> --
>> Daniel Ruggeri

On July 27, 2020 2:12:45 AM CDT, Stefan Eissing <stefan.eissing@greenbytes.de> wrote:
>
>
>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri <druggeri@apache.org>:
>>
>> Hi, all;
>> FYI, I came across an unexpected set of diffs when rebuilding docs
>before tagging this morning. Haven't forgotten about T&R, but would
>like to figure out the origin of the docs changes (likely my
>environment). I've started a conversation on docs@ about what I'm
>seeing.
>
>Sorry about your troubles. Do we need to look for someone else doing
>the RMing or what's your status?

Hi, Stefen;
I'm still good to go. I just need clarity on what encoding behavior we expect in the docs. More info is on docs@. Either way works for me... just need to know what the consensus is.

>
>>
>>
>> On 2020/07/22 23:32:05, Daniel Ruggeri <daniel@bitnebula.com> wrote:
>>> Hi, all;
>>> It's been a while since we've rolled a release and gotten
>fixes/etc in our community's hands. Apologies for not suggesting this
>sooner. How about a T&R Friday? That will let vote run through the
>weekend.
>>> --
>>> Daniel Ruggeri

Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
>
>
> On July 27, 2020 2:12:45 AM CDT, Stefan Eissing <stefan.eissing@greenbytes.de> wrote:
>>
>>
>>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri <druggeri@apache.org>:
>>>
>>> Hi, all;
>>> FYI, I came across an unexpected set of diffs when rebuilding docs
>> before tagging this morning. Haven't forgotten about T&R, but would
>> like to figure out the origin of the docs changes (likely my
>> environment). I've started a conversation on docs@ about what I'm
>> seeing.
>>
>> Sorry about your troubles. Do we need to look for someone else doing
>> the RMing or what's your status?
>
> Hi, Stefen;
> I'm still good to go. I just need clarity on what encoding behavior we expect in the docs. More info is on docs@. Either way works for me... just need to know what the consensus is.
>
>>
>>>
>>>
>>> On 2020/07/22 23:32:05, Daniel Ruggeri <daniel@bitnebula.com> wrote:rance :))
>>>> Hi, all;
>>>> It's been a while since we've rolled a release and gotten
>> fixes/etc in our community's hands. Apologies for not suggesting this
>> sooner. How about a T&R Friday? That will let vote run through the
>> weekend.
>>>> --
>>>> Daniel Ruggeri
>

Hi,

I don't have access to my PC these days (side effect from being on
vacation in the south of France :)), however, have a look at r1878788 on
trunk which should fixed once and for all the issue.

This commit switches the en doc files into utf8 which works great with
older and newer versions of Java.

To be consistent with the other language, the files themselves should be
renamed to have a trailing .utf8, as explained in the commit description.

I've not done it on trunk because it is painful (at least for me) to
synch all the news .utf8 files with svn. If s.o. feels like making the
change, please do.

CJ

Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
>
>
> On July 27, 2020 2:12:45 AM CDT, Stefan Eissing <stefan.eissing@greenbytes.de> wrote:
>>
>>
>>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri <druggeri@apache.org>:
>>>
>>> Hi, all;
>>> FYI, I came across an unexpected set of diffs when rebuilding docs
>> before tagging this morning. Haven't forgotten about T&R, but would
>> like to figure out the origin of the docs changes (likely my
>> environment). I've started a conversation on docs@ about what I'm
>> seeing.
>>
>> Sorry about your troubles. Do we need to look for someone else doing
>> the RMing or what's your status?
>
> Hi, Stefen;
> I'm still good to go. I just need clarity on what encoding behavior we expect in the docs. More info is on docs@. Either way works for me... just need to know what the consensus is.
>
>>
>>>
>>>
>>> On 2020/07/22 23:32:05, Daniel Ruggeri <daniel@bitnebula.com> wrote:rance :))
>>>> Hi, all;
>>>> It's been a while since we've rolled a release and gotten
>> fixes/etc in our community's hands. Apologies for not suggesting this
>> sooner. How about a T&R Friday? That will let vote run through the
>> weekend.
>>>> --
>>>> Daniel Ruggeri
>

Hi,

I don't have access to my PC these days (side effect from being on
vacation in the south of France :)), however, have a look at r1878788 on
trunk which should fixed once and for all the issue.

This commit switches the en doc files into utf8 which works great with
older and newer versions of Java.

To be consistent with the other language, the files themselves should be
renamed to have a trailing .utf8, as explained in the commit description.

I've not done it on trunk because it is painful (at least for me) to
synch all the news .utf8 files with svn. If s.o. feels like making the
change, please do.

CJ

On Tue, Jul 28, 2020 at 4:30 AM Christophe JAILLET
<christophe.jaillet@wanadoo.fr> wrote:
>
> Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
> >
> >
> > On July 27, 2020 2:12:45 AM CDT, Stefan Eissing <stefan.eissing@greenbytes.de> wrote:
> >>
> >>
> >>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri <druggeri@apache.org>:
> >>>
> >>> Hi, all;
> >>> FYI, I came across an unexpected set of diffs when rebuilding docs
> >> before tagging this morning. Haven't forgotten about T&R, but would
> >> like to figure out the origin of the docs changes (likely my
> >> environment). I've started a conversation on docs@ about what I'm
> >> seeing.
> >>
> >> Sorry about your troubles. Do we need to look for someone else doing
> >> the RMing or what's your status?
> >
> > Hi, Stefen;
> > I'm still good to go. I just need clarity on what encoding behavior we expect in the docs. More info is on docs@. Either way works for me... just need to know what the consensus is.
> >
> >>
> >>>
> >>>
> >>> On 2020/07/22 23:32:05, Daniel Ruggeri <daniel@bitnebula.com> wrote:rance :))
> >>>> Hi, all;
> >>>> It's been a while since we've rolled a release and gotten
> >> fixes/etc in our community's hands. Apologies for not suggesting this
> >> sooner. How about a T&R Friday? That will let vote run through the
> >> weekend.
> >>>> --
> >>>> Daniel Ruggeri
> >
>
> Hi,
>
> I don't have access to my PC these days (side effect from being on
> vacation in the south of France :)), however, have a look at r1878788 on
> trunk which should fixed once and for all the issue.
>
> This commit switches the en doc files into utf8 which works great with
> older and newer versions of Java.
>
> To be consistent with the other language, the files themselves should be
> renamed to have a trailing .utf8, as explained in the commit description.
>
> I've not done it on trunk because it is painful (at least for me) to
> synch all the news .utf8 files with svn. If s.o. feels like making the
> change, please do.
>
> CJ

Thanks Christophe. I backported it but did not do the .utf8 extension
due to the amount of spam it would create.
I also put some java checks in docs-build

Daniel -- I say proceed w/ release and we can revisit the .utf8 extension later.

--
Eric Covener
covener@gmail.com

On 7/28/2020 7:41 AM, Eric Covener wrote:
> On Tue, Jul 28, 2020 at 4:30 AM Christophe JAILLET
> <christophe.jaillet@wanadoo.fr> wrote:
>> Le 27/07/2020 à 14:11, Daniel Ruggeri a écrit :
>>>
>>> On July 27, 2020 2:12:45 AM CDT, Stefan Eissing <stefan.eissing@greenbytes.de> wrote:
>>>>
>>>>> Am 25.07.2020 um 00:14 schrieb Daniel Ruggeri <druggeri@apache.org>:
>>>>>
>>>>> Hi, all;
>>>>> FYI, I came across an unexpected set of diffs when rebuilding docs
>>>> before tagging this morning. Haven't forgotten about T&R, but would
>>>> like to figure out the origin of the docs changes (likely my
>>>> environment). I've started a conversation on docs@ about what I'm
>>>> seeing.
>>>>
>>>> Sorry about your troubles. Do we need to look for someone else doing
>>>> the RMing or what's your status?
>>> Hi, Stefen;
>>> I'm still good to go. I just need clarity on what encoding behavior we expect in the docs. More info is on docs@. Either way works for me... just need to know what the consensus is.
>>>
>>>>>
>>>>> On 2020/07/22 23:32:05, Daniel Ruggeri <daniel@bitnebula.com> wrote:rance :))
>>>>>> Hi, all;
>>>>>> It's been a while since we've rolled a release and gotten
>>>> fixes/etc in our community's hands. Apologies for not suggesting this
>>>> sooner. How about a T&R Friday? That will let vote run through the
>>>> weekend.
>>>>>> --
>>>>>> Daniel Ruggeri
>> Hi,
>>
>> I don't have access to my PC these days (side effect from being on
>> vacation in the south of France :)), however, have a look at r1878788 on
>> trunk which should fixed once and for all the issue.
>>
>> This commit switches the en doc files into utf8 which works great with
>> older and newer versions of Java.
>>
>> To be consistent with the other language, the files themselves should be
>> renamed to have a trailing .utf8, as explained in the commit description.
>>
>> I've not done it on trunk because it is painful (at least for me) to
>> synch all the news .utf8 files with svn. If s.o. feels like making the
>> change, please do.
>>
>> CJ
> Thanks Christophe. I backported it but did not do the .utf8 extension
> due to the amount of spam it would create.
> I also put some java checks in docs-build
>
> Daniel -- I say proceed w/ release and we can revisit the .utf8 extension later.
>
Excellent! I've performed my prechecks and everything is looking pretty
good. I'll get this moving now.

--
Daniel Ruggeri