On Thu, May 28, 2020 at 06:27:54AM +, Daniel Shahaf wrote:
> Stefan Sperling wrote on Thu, 28 May 2020 08:07 +0200:
> > +++ releasing.part.html (working copy)
> > @@ -1300,6 +1300,20 @@ Ensure that your mailer doesn't wrap the URLs over
> > NOTE: We announce the release before updating the
svn-r...@apache.org wrote on Thu, 28 May 2020 04:00 -:
> +++ subversion/branches/1.14.x/subversion/libsvn_client/mtcc.c Thu May 28
> 04:00:12 2020
> @@ -453,7 +453,8 @@ mtcc_verify_create(svn_client__mtcc_t *m
>
>if (op)
> return svn_error_createf(SVN_ERR_FS_ALREADY_EXISTS,
Stefan Sperling wrote on Thu, 28 May 2020 08:07 +0200:
> +++ releasing.part.html (working copy)
> @@ -1300,6 +1300,20 @@ Ensure that your mailer doesn't wrap the URLs over
> NOTE: We announce the release before updating the website since the
> website
> update links to the release announce
On Thu, May 28, 2020 at 03:03:40AM +, Daniel Shahaf wrote:
> s...@apache.org wrote on Wed, 27 May 2020 14:34 -:
> > Author: stsp
> > Date: Wed May 27 14:34:18 2020
> > New Revision: 1878162
> >
> > URL: http://svn.apache.org/viewvc?rev=1878162&view=rev
> > Log:
> > * tools/dist/release-lin
On Thu, May 28, 2020 at 07:59:48AM +0200, Stefan Sperling wrote:
> Receiving such a message at the end of a long release preparation day is
> indeed rather discouraging. Since this is recurring behaviour and can
> potentially have toxic results in affected project communities, I think
> we should d
On Wed, May 27, 2020 at 09:41:18PM +0100, Julian Foad wrote:
> Branko Čibej wrote:
> > > > On 27.05.2020 19:30, Stefan Sperling wrote:
> > > > > Out of the blue, I have received nitpicking of changes I made to the
> > > > > website and the announce message I sent. I've received this feedback
> > >
On 28.05.2020 07:40, Daniel Shahaf wrote:
> Someone could start a discussion with the announce@a.o moderators. The
> escalation path, IIRC, is: announce-owner@, press@, VP M&P (= Sally),
> operations@, board@, members@.
Did that about half an hour ago. Let's see what happens. If whoever
blocked t
Daniel Shahaf wrote on Thu, 28 May 2020 03:01 +:
> jcor...@apache.org wrote on Wed, 27 May 2020 18:39 -:
> > Author: jcorvel
> > Date: Wed May 27 18:39:53 2020
> > New Revision: 1878189
> >
> > URL: http://svn.apache.org/viewvc?rev=1878189&view=rev
> > Log:
> > * 1.14.x/STATUS: Vote for r1
Julian Foad wrote on Wed, 27 May 2020 21:41 +0100:
> Branko Čibej wrote:
> >>> On 27.05.2020 19:30, Stefan Sperling wrote:
> Out of the blue, I have received nitpicking of changes I made to the
> website and the announce message I sent. I've received this feedback
> via the mailing
Dear announce@ moderators,
Moderation is not an appropriate venue for discussing policy. It is a
way to prevent spam. If you have something to say, you're welcome to say
it on dev@subversion.apache.org. You are not responsible for the
contents of a release. The PMC is. Your anonymous pontification
s...@apache.org wrote on Wed, 27 May 2020 14:34 -:
> Author: stsp
> Date: Wed May 27 14:34:18 2020
> New Revision: 1878162
>
> URL: http://svn.apache.org/viewvc?rev=1878162&view=rev
> Log:
> * tools/dist/release-lines.yaml: Update supported release list for release.py.
Good catch. Is this al
jcor...@apache.org wrote on Wed, 27 May 2020 18:39 -:
> Author: jcorvel
> Date: Wed May 27 18:39:53 2020
> New Revision: 1878189
>
> URL: http://svn.apache.org/viewvc?rev=1878189&view=rev
> Log:
> * 1.14.x/STATUS: Vote for r1877072, approving.
>
> Modified:
> subversion/branches/1.14.x/ST
Branko Čibej wrote:
On 27.05.2020 19:30, Stefan Sperling wrote:
Out of the blue, I have received nitpicking of changes I made to the
website and the announce message I sent. I've received this feedback
via the mailing list moderation mechanism.
Can anyone tell me what's going on here? Who even
On 27.05.2020 20:35, Stefan Sperling wrote:
> On Wed, May 27, 2020 at 07:48:41PM +0200, Branko Čibej wrote:
>> On 27.05.2020 19:30, Stefan Sperling wrote:
>>> Out of the blue, I have received nitpicking of changes I made to the
>>> website and the announce message I sent. I've received this feedbac
On Wed, May 27, 2020 at 07:48:41PM +0200, Branko Čibej wrote:
> On 27.05.2020 19:30, Stefan Sperling wrote:
> > Out of the blue, I have received nitpicking of changes I made to the
> > website and the announce message I sent. I've received this feedback
> > via the mailing list moderation mechanism
On 27.05.2020 19:30, Stefan Sperling wrote:
> Out of the blue, I have received nitpicking of changes I made to the
> website and the announce message I sent. I've received this feedback
> via the mailing list moderation mechanism.
>
> Can anyone tell me what's going on here? Who even wrote this?
>
Out of the blue, I have received nitpicking of changes I made to the
website and the announce message I sent. I've received this feedback
via the mailing list moderation mechanism.
Can anyone tell me what's going on here? Who even wrote this?
FWIW, the announce message was generated by release.py
I'm happy to announce the release of Apache Subversion 1.14.0.
Please choose the mirror closest to you by visiting:
https://subversion.apache.org/download.cgi#recommended-release
This is a stable feature release of the Apache Subversion open source
version control system.
SHA-512 checksums a
On Wed, May 27, 2020 at 10:35:02AM -0400, Nathan Hartman wrote:
> To finalize the release notes for 1.14.0, I think there are just these
> three changes to make:
>
> (1) Document the test failures that occur on Windows with links to the
> revisions (and/or patches) that fix them. Say that "the
On Wed, May 27, 2020 at 4:43 PM Nathan Hartman wrote:
>
> On Tue, May 26, 2020 at 10:02 PM Yasuhito FUTATSUKI
> wrote:
> > >> Should any of these be added to
> > >> https://subversion.apache.org/docs/release-notes/1.14#issues ?
> > >
> > > Yes, all of them I think.
> > > I thought first to wait
On Tue, May 26, 2020 at 10:02 PM Yasuhito FUTATSUKI wrote:
> >> Should any of these be added to
> >> https://subversion.apache.org/docs/release-notes/1.14#issues ?
> >
> > Yes, all of them I think.
> > I thought first to wait whether we can still commit some / most of
> > them, and nominate for b
To finalize the release notes for 1.14.0, I think there are just these
three changes to make:
(1) Document the test failures that occur on Windows with links to the
revisions (and/or patches) that fix them. Say that "these issues
are expected to be fixed in the next point release" or somet
22 matches
Mail list logo
