[Greg Stein]
But I'll go one step further: you shouldn't care at all.
I could release 1.2.2 tomorrow with all kinds of crap. Or maybe the
day after 1.8.0 goes final. Not much you can do about it. Subversion
needs to soak its own code, not the entire dependency stack.
You could, but 1.2.2
I think it's clear that we have to wait for a Serf bugfix release before
releasing RC3, and during that time our soak period is simply on hold.
What happens after Serf 1.2.1 is released depends on the changes there.
If it's just a trivial bugfix for the digest authn issue, then we can
simply
On Mon, Jun 3, 2013 at 7:22 AM, C. Michael Pilato cmpil...@collab.net wrote:
I'll suggest that the answer is found in how we'd track the issue locally.
Subversion requires Serf 1.2.1 would be a reasonable issue description.
It would naturally be a 1.8.0 blocking issue. It's resolution (on our
On Mon, Jun 3, 2013 at 8:18 AM, Branko Čibej br...@apache.org wrote:
I think it's clear that we have to wait for a Serf bugfix release before
releasing RC3, and during that time our soak period is simply on hold.
What happens after Serf 1.2.1 is released depends on the changes there.
If it's
On 06/03/2013 11:18 AM, Branko Čibej wrote:
I think it's clear that we have to wait for a Serf bugfix release before
releasing RC3, and during that time our soak period is simply on hold.
What happens after Serf 1.2.1 is released depends on the changes there.
If it's just a trivial bugfix for
Lieven produced a short list of changes to release in 1.2.1, which I'm
merging now. The release should be done in about an hour.
Cheers,
-g
On Mon, Jun 3, 2013 at 11:36 AM, C. Michael Pilato cmpil...@collab.net wrote:
On 06/03/2013 11:18 AM, Branko Čibej wrote:
I think it's clear that we have
On Mon, Jun 3, 2013 at 10:22 AM, C. Michael Pilato cmpil...@collab.net wrote:
...
On the other hand, Serf 1.2.0 is the only available public Serf release with
which Subversion 1.8.0 can operate[2], which really rather limits folks'
...
Unfortunately, there is as yet no public Serf release to
On 05/30/2013 06:20 PM, Ben Reser wrote:
On Thu, May 30, 2013 at 2:53 PM, Mark Phippard markp...@gmail.com wrote:
To actually release on that date you would still need to follow Mike's
proposed schedule. It would just allow more time for the final signing. But
it would still have to happen
I've been working with the ASF's marketing team on the official Apache
Subversion 1.8.0 press release, and we're trying to get a feel for the
timing of the final release (and by extension, the press announcement).
This community posted 1.8.0-rc2 on Tuesday, May 14, with verification and
public
On Thu, May 30, 2013 at 6:00 AM, C. Michael Pilato cmpil...@collab.net wrote:
This community posted 1.8.0-rc2 on Tuesday, May 14, with verification and
public release completing on Thursday, May 16. While it's not precisely
spelled out in the Community Guide which of those two dates starts the
On Thu, May 30, 2013 at 09:24:52AM -0700, Ben Reser wrote:
I'll be flying to England on the 4th, so I should be able to roll the
tarballs sometime late in the week proceeding the hackathon. That
would provide us most of the hackathon for devs to find the time to
test/sign off.
If we don't
On Thu, May 30, 2013 at 9:31 PM, Stefan Sperling s...@elego.de wrote:
On Thu, May 30, 2013 at 09:24:52AM -0700, Ben Reser wrote:
I'll be flying to England on the 4th, so I should be able to roll the
tarballs sometime late in the week proceeding the hackathon. That
would provide us most of the
On 30.05.2013 20:59, Ivan Zhakov wrote:
On Thu, May 30, 2013 at 9:31 PM, Stefan Sperling s...@elego.de wrote:
On Thu, May 30, 2013 at 09:24:52AM -0700, Ben Reser wrote:
I'll be flying to England on the 4th, so I should be able to roll the
tarballs sometime late in the week proceeding the
As noted elsewhere, press releases are ideally on a Tuesday. I'd really
like to see the release/announce go out, coordinated, on a Tuesday.
Cheers,
-g
On May 30, 2013 8:00 AM, C. Michael Pilato cmpil...@collab.net wrote:
I've been working with the ASF's marketing team on the official Apache
My sincerest apologies for that crud at the end of my previous mail in
this thread. Someone decided just a couple hours ago that it's a good
idea to unconditionally add that mess to outgoing messages from a
particular domain, and so I'm no longer sending messages to this list
from that domain
On Thu, May 30, 2013 at 2:00 PM, Greg Stein gst...@gmail.com wrote:
As noted elsewhere, press releases are ideally on a Tuesday. I'd really like
to see the release/announce go out, coordinated, on a Tuesday.
That's fine the release would need to be after the hackathon then.
Given that and
On Thu, May 30, 2013 at 11:23 PM, Ben Reser b...@reser.org wrote:
On Thu, May 30, 2013 at 2:00 PM, Greg Stein gst...@gmail.com wrote:
As noted elsewhere, press releases are ideally on a Tuesday. I'd really like
to see the release/announce go out, coordinated, on a Tuesday.
That's fine the
On May 30, 2013, at 5:23 PM, Ben Reser b...@reser.org wrote:
On Thu, May 30, 2013 at 2:00 PM, Greg Stein gst...@gmail.com wrote:
As noted elsewhere, press releases are ideally on a Tuesday. I'd really like
to see the release/announce go out, coordinated, on a Tuesday.
That's fine the
On Thu, May 30, 2013 at 2:53 PM, Mark Phippard markp...@gmail.com wrote:
To actually release on that date you would still need to follow Mike's
proposed schedule. It would just allow more time for the final signing. But
it would still have to happen during the hackathon.
Correct that was my
On Thu, May 30, 2013 at 2:48 PM, Johan Corveleyn jcor...@gmail.com wrote:
On Thu, May 30, 2013 at 11:23 PM, Ben Reser b...@reser.org wrote:
On Thu, May 30, 2013 at 2:00 PM, Greg Stein gst...@gmail.com wrote:
As noted elsewhere, press releases are ideally on a Tuesday. I'd really
like
to
20 matches
Mail list logo
