> -----Original Message-----
> From: Ben Reser [mailto:bre...@apache.org]
> Sent: donderdag 19 maart 2015 19:34
> To: Daniel Shahaf
> Cc: Subversion Development
> Subject: Re: Apache Subversion 1.9.0-beta1 released
>
> On 3/18/15 11:57 PM, Daniel Shahaf wrote:
> > That link isn't stable: issues disappear from it as soon as they are
> > merged to 1.9.x, so if we fix issue #4560 tomorrow it won't appear in
> > the link, even though it does affect 1.9.0-beta1.
> >
> > Next time, it would be better to explicitly list the known blocker
> > issues. (Unless we plan to introduce a 1.9.0-beta1 milestone.)
> >
> > For future reference, right now that link contains:
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=4560 (pin-externals
API
> semantics)
> > http://subversion.tigris.org/issues/show_bug.cgi?id=4565 (prospective
blame)
> >
> > I'm not sure whether #4565 was fixed in beta1 or not. I'm not sure if
> > there are other formerly-1.9.0-blocker issues that have been fixed since
> > beta1 had been tagged and so are not currently in the linked buglist.
> >
> That's the output from release.py for write-announcement. I didn't think
any
> of the issues were big enough to specifically point out so I didn't edit
it
> this time. But I agree it's not a particularly useful link. On top of
your
> problem is the issue that we're not very good about using the issue
tracker on
> a regular basis.
I think we resolved issue 4565, before beta 1. (Not sure about that other
issue)
It provides several options and I haven't seen any discussion for that issue
on any of our channels.
Bert
