You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Stein <gs...@gmail.com> on 2011/08/17 07:56:34 UTC
ra_serf testing (was: svn commit: r1158522 - /subversion/branches/1.7.x/STATUS)
On Wed, Aug 17, 2011 at 01:30, <gs...@apache.org> wrote:
> Author: gstein
> Date: Wed Aug 17 05:30:23 2011
> New Revision: 1158522
>
> URL: http://svn.apache.org/viewvc?rev=1158522&view=rev
> Log:
> IMO, issue 3979 should be fixed if ra_serf is the default, but we're too
> late in the cycle for the necessary work. Ship with Neon.
I would like to be very clear about something here:
The bugs that arrived "last minute" are (IMO) due to a failing in the
community to properly test ra_serf. And now we have kicked the damned
can down the road. I fear that we're going to run into the same
fuckin' problem when we try to ship 1.8, and it makes me cranky.
Configure your client with ra_serf. Disable Neon. Test it. And if you
have a problem, then FILE A BUG. Do it.
We need serf to properly deal with our goal of "request only the
pristines (by SHA) that we need". Failing to properly test ra_serf
impacts our future direction. PLEASE: no more of this "test at last
minute" crap that has happened.
-g
Re: ra_serf testing (was: svn commit: r1158522 - /subversion/branches/1.7.x/STATUS)
Posted by Greg Stein <gs...@gmail.com>.
On Wed, Aug 17, 2011 at 04:13, Stefan Sperling <st...@elego.de> wrote:
> On Wed, Aug 17, 2011 at 01:56:34AM -0400, Greg Stein wrote:
>> On Wed, Aug 17, 2011 at 01:30, <gs...@apache.org> wrote:
>> > Author: gstein
>> > Date: Wed Aug 17 05:30:23 2011
>> > New Revision: 1158522
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1158522&view=rev
>> > Log:
>> > IMO, issue 3979 should be fixed if ra_serf is the default, but we're too
>> > late in the cycle for the necessary work. Ship with Neon.
>>
>> I would like to be very clear about something here:
>>
>> The bugs that arrived "last minute" are (IMO) due to a failing in the
>> community to properly test ra_serf. And now we have kicked the damned
>> can down the road. I fear that we're going to run into the same
>> fuckin' problem when we try to ship 1.8, and it makes me cranky.
>>
>> Configure your client with ra_serf. Disable Neon. Test it. And if you
>> have a problem, then FILE A BUG. Do it.
>>
>> We need serf to properly deal with our goal of "request only the
>> pristines (by SHA) that we need". Failing to properly test ra_serf
>> impacts our future direction. PLEASE: no more of this "test at last
>> minute" crap that has happened.
>
> I've put a call for user testing into the 1.7 release notes.
Thanks, Stefan!
Re: ra_serf testing (was: svn commit: r1158522 -
/subversion/branches/1.7.x/STATUS)
Posted by Stefan Sperling <st...@elego.de>.
On Wed, Aug 17, 2011 at 01:56:34AM -0400, Greg Stein wrote:
> On Wed, Aug 17, 2011 at 01:30, <gs...@apache.org> wrote:
> > Author: gstein
> > Date: Wed Aug 17 05:30:23 2011
> > New Revision: 1158522
> >
> > URL: http://svn.apache.org/viewvc?rev=1158522&view=rev
> > Log:
> > IMO, issue 3979 should be fixed if ra_serf is the default, but we're too
> > late in the cycle for the necessary work. Ship with Neon.
>
> I would like to be very clear about something here:
>
> The bugs that arrived "last minute" are (IMO) due to a failing in the
> community to properly test ra_serf. And now we have kicked the damned
> can down the road. I fear that we're going to run into the same
> fuckin' problem when we try to ship 1.8, and it makes me cranky.
>
> Configure your client with ra_serf. Disable Neon. Test it. And if you
> have a problem, then FILE A BUG. Do it.
>
> We need serf to properly deal with our goal of "request only the
> pristines (by SHA) that we need". Failing to properly test ra_serf
> impacts our future direction. PLEASE: no more of this "test at last
> minute" crap that has happened.
I've put a call for user testing into the 1.7 release notes.
Re: ra_serf testing (was: svn commit: r1158522 -
/subversion/branches/1.7.x/STATUS)
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
+1; let's identify problems /throughout/ the 1.8 release release cycle,
rather than only at 1.8 stabilization.
Greg Stein wrote on Wed, Aug 17, 2011 at 01:56:34 -0400:
> On Wed, Aug 17, 2011 at 01:30, <gs...@apache.org> wrote:
> > Author: gstein
> > Date: Wed Aug 17 05:30:23 2011
> > New Revision: 1158522
> >
> > URL: http://svn.apache.org/viewvc?rev=1158522&view=rev
> > Log:
> > IMO, issue 3979 should be fixed if ra_serf is the default, but we're too
> > late in the cycle for the necessary work. Ship with Neon.
>
> I would like to be very clear about something here:
>
> The bugs that arrived "last minute" are (IMO) due to a failing in the
> community to properly test ra_serf. And now we have kicked the damned
> can down the road. I fear that we're going to run into the same
> fuckin' problem when we try to ship 1.8, and it makes me cranky.
>
> Configure your client with ra_serf. Disable Neon. Test it. And if you
> have a problem, then FILE A BUG. Do it.
>
> We need serf to properly deal with our goal of "request only the
> pristines (by SHA) that we need". Failing to properly test ra_serf
> impacts our future direction. PLEASE: no more of this "test at last
> minute" crap that has happened.
>
> -g