The release is tagged and uploaded, but I'll wait to send an announcement until
I see the distribution site updated.
-- Scott
With 4 +1 votes and no objections, I'll call the vote passed and do the release
early this week.
The only change to the RC will be the site update I applied, which doesn't
change any code.
-- Scott
34
> To: c-dev@xerces.apache.org
> Subject: Re: 3.2.4 release candidate
>
> FWIW we still need one more +1 vote I believe.
>
> -- Scott
>
+1
> On 2022-10-10 18:58, Cantor, Scott wrote :
>
> I've posted a signed RC here:
> https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
>
> The web site update embedded in it includes a note on the front page that
> the library lacks maintainers and should not be used for new projects.
> -Original Message-
> From: Cantor, Scott
> Sent: 14 October 2022 17:34
> To: c-dev@xerces.apache.org
> Subject: Re: 3.2.4 release candidate
>
> FWIW we still need one more +1 vote I believe.
I will try to find time to do some testing this weekend.
Regards,
Roger
FWIW we still need one more +1 vote I believe.
-- Scott
>We run NetAccessorTest.cpp on every platform and it seems to work,
> at least over HTTP (HTTPS would require some further patching to deal
> with CA paths setup on some platforms):
Ok, before I fiinalize I'll see what I can figure out from that. If that
doesn't work for me it must be environ
Cantor, Scott writes:
> On 10/12/22, 9:09 AM, "Boris Kolpackov" wrote:
>
> >2. We build with ICU and Curl everywhere so other transcoders
> > and netaccessors were not tested.
>
> Do you actually use them? Because in my testing, I haven't managed to
> make any of the net accessors wo
On 10/12/22, 9:09 AM, "Boris Kolpackov" wrote:
>2. We build with ICU and Curl everywhere so other transcoders
> and netaccessors were not tested.
Do you actually use them? Because in my testing, I haven't managed to make any
of the net accessors work (per the open bug that was reporte
Cantor, Scott writes:
> I've posted a signed RC here:
> https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
We've updated our build2 package[1] to RC1 and ran the CI. Everything
seems to be fine except for the wasm32-emscripten target, which is
not unexpected. The complete list of tested
On 10/11/22, 11:33 AM, "Boris Kolpackov" wrote:
>That's what I thought but I don't see any commits in the history that
>add your original note.
I may have forgotten to commit it. In any case it won't match the RC anyway,
and I committed the wording you requested for the eventual site bu
Cantor, Scott writes:
> On 10/11/22, 10:28 AM, "Boris Kolpackov" wrote:
>
> >Remind me where does the source for the front page live?
>
> doc/readme.xml I think (it's in doc, but page is from memory, should
> be clear from the commit).
That's what I thought but I don't see any commits in
On 10/11/22, 10:28 AM, "Boris Kolpackov" wrote:
>Remind me where does the source for the front page live?
doc/readme.xml I think (it's in doc, but page is from memory, should be clear
from the commit).
>If so, I would be against this wording. As I believe was clearly
>demonstrated
Cantor, Scott writes:
> Done, v3.2.4rc1.
Thanks!
> > The web site update embedded in it includes a note on the front page
> > that the library lacks maintainers and should not be used for new
> > projects. Are we talking about this change or something else?
>
> I changed both the front page a
> Thanks for your work on this! The corresponding git branch is xerces-3.2
> and the commit is bfe32a149e8c ("Adjust release info."), correct?
Yes, that was the last one.
>Wouldn't be bad to tag the RC to make sure we are testing the same
> thing.
Done, v3.2.4rc1.
> The web site update embedde
Cantor, Scott writes:
> I've posted a signed RC here:
> https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
Thanks for your work on this!
The corresponding git branch is xerces-3.2 and the commit is
bfe32a149e8c ("Adjust release info."), correct? Wouldn't be
bad to tag the RC to make sur
I've posted a signed RC here:
https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
The web site update embedded in it includes a note on the front page that the
library lacks maintainers and should not be used for new projects.
This is my +1 to release it. I can do the release next week s
17 matches
Mail list logo
