Philip, can you help clarify this?
Daniel Shahaf wrote on 2018-07-02:
> Julian Foad wrote on Mon, 02 Jul 2018 12:20 +0100:
> > Philip Martin wrote:
> > > I did also worry about thread safety: it's not safe to modify the
> > > context like that if the context can be shared across multiple threads.
The 1.10.1 release artifacts are now available for testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.
Thanks!
- Julian
The 1.9.8 release artifacts are now available for testing/signing.
Please get the tarballs from
https://dist.apache.org/repos/dist/dev/subversion
and add your signatures there.
Thanks!
- Julian
Julian Foad wrote:
> The 1.10.1 release artifacts are now available for testing/signing.
The 'CHANGES' file in the 1.10.1 tarball is missing the last two changes, that
were merged last night:
+* Fix segfault using Gnome Keyring with libsecret (r1835782)
+* Fix
Daniel Shahaf wrote:
>[...] committed the patch --- r1835760 --- and proposed it for
> backport to to 1.10.x [...]
This fix will be in 1.10.1, along with some other gnome keyring fixes.
- Julian
Julian Foad wrote:
> Daniel Shahaf wrote:
> > In the meantime, we can document the authz regression on
> > https://subversion.apache.org/docs/release-notes/1.10#issues [...]
>
> Yes. I can do that now.
http://svn.apache.org/r1835812
- Julian
Julian Foad wrote on Thu, 12 Jul 2018 22:35 +0100:
> Philip Martin wrote:
> > [...] a user recently reported another regression
> > [...] I'd like to delay 1.10.1 for a few days [...]
>
> My time is currently allocated to rolling a release of the good fixes we
> already have. In a few days I
Daniel Shahaf wrote:
> In the meantime, we can document the authz regression on
> https://subversion.apache.org/docs/release-notes/1.10#issues so it's
> easily visible to those considering to upgrade from 1.9.x to 1.10.1.
Yes. I can do that now.
- Julian
Our releasing docs say, "CHANGES should always be edited on trunk and then
merged over to the release branch(es)". The 'CHANGES' file in 1.10.1 doesn't
have the latest two fixes that were merged to 1.10.x last night, because I
missed manually re-executing that step.
Possible improvements:
1)
On 13.07.2018 16:19, Julian Foad wrote:
> Our releasing docs say, "CHANGES should always be edited on trunk and then
> merged over to the release branch(es)". The 'CHANGES' file in 1.10.1 doesn't
> have the latest two fixes that were merged to 1.10.x last night, because I
> missed manually
On 7/13/2018 4:28 PM, Branko Čibej wrote:
On 13.07.2018 16:19, Julian Foad wrote:
Our releasing docs say, "CHANGES should always be edited on trunk and then merged
over to the release branch(es)". The 'CHANGES' file in 1.10.1 doesn't have the
latest two fixes that were merged to 1.10.x last
Julian Foad writes:
> Philip, can you help clarify this?
>>
>> It's not clear to me from the added paragraph whether the restriction
>> "only access the context from a thread at a time" is imposed by the
>> library implementation or by the way API consumers' code is typically
>> structured.
Julian Foad wrote on Fri, 13 Jul 2018 14:28 +0100:
> Julian Foad wrote:
> > The 1.10.1 release artifacts are now available for testing/signing.
>
> The 'CHANGES' file in the 1.10.1 tarball is missing the last two
> changes, that were merged last night:
The CHANGES file in 1.10.1 also has a
Daniel Shahaf wrote:
> > The 'CHANGES' file in the 1.10.1 tarball is missing the last two
> > changes, that were merged last night:
>
> The CHANGES file in 1.10.1 also has a "Version 1.11.0" section with some
> bugfixes listed in it.
>
> I think CHANGES in 1.10.x (and earlier) releases
I have decided I will re-roll these releases. Just the CHANGES file will be
up-to-date, and without changes relating to later minor release lines like it
was before. There will be no other changes.
I will re-roll ASAP; Monday at the latest.
I'll find out soon whether I'll be bumping the patch
I have decided I will re-roll these releases. Just the CHANGES file will be
up-to-date, and without changes relating to later minor release lines like it
was before. There will be no other changes.
I will re-roll ASAP; Monday at the latest.
I'll find out soon whether I'll be bumping the patch
Stefan Hett wrote:
> On 7/13/2018 4:28 PM, Branko Čibej wrote:
> > On 13.07.2018 16:19, Julian Foad wrote:
> >>svn ps svn:externals '^/subversion/CHANGES CHANGES' trunk-wc/.
> > This would be mildly horrible as it would show up in release branches
> > and become part of the release. Up to now,
Julian Foad wrote on Fri, 13 Jul 2018 17:12 +0100:
> $ svn ls ^/subversion
> README
> branches/
> developer-resources/
> site/
> site-ng/
> svn-logos/
> tags/
> trunk/
> upstream/
>
> Brane's suggestion of locating CHANGES in the web site tree makes quite
> good sense to me too, although as long
Julian Foad wrote on Fri, 13 Jul 2018 17:20 +0100:
> Daniel Shahaf wrote:
> > > The 'CHANGES' file in the 1.10.1 tarball is missing the last two
> > > changes, that were merged last night:
> >
> > The CHANGES file in 1.10.1 also has a "Version 1.11.0" section with some
> > bugfixes listed in it.
On 13/07/2018 18:12, Julian Foad wrote:
> Stefan Hett wrote:
>> On 7/13/2018 4:28 PM, Branko Čibej wrote:
>>> On 13.07.2018 16:19, Julian Foad wrote:
svn ps svn:externals '^/subversion/CHANGES CHANGES' trunk-wc/.
>>> This would be mildly horrible as it would show up in release branches
>>>
Johan Corveleyn wrote on 2018-06-29:
> > [[[
> > Subversions delivers two kinds of stable releases:
> >
> > * Long Term Support (LTS):
> > - release every 2 years; 4 years support; emphasis on stability
> > * standard:
> > - release every 6 months; 6 months support; emphasis on
21 matches
Mail list logo
