[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Please review for backport the issue #3275 changes (Was: Re: 1.5.5 next Wednesday (12/17))

From: David Ferguson <ferguson.david_at_gmail.com>
Date: Tue, 16 Dec 2008 10:54:03 -0500

As an admin of a mutli-site SVN shop, please consider including the fix to
#3275 in 1.5.5. We are stuck on 1.5.0!

thanks,
David

On Tue, Dec 16, 2008 at 10:42 AM, Hyrum K. Wright <
hyrum_wright_at_mail.utexas.edu> wrote:

> Mark Phippard wrote:
> > On Tue, Dec 16, 2008 at 10:21 AM, C. Michael Pilato <cmpilato_at_collab.net>
> wrote:
> >> Konstantin Kolinko wrote:
> >>> 2008/12/16 Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>:
> >>>> Hyrum K. Wright wrote:
> >>>> Status update: still on track for rolling 1.5.5 tomorrow.
> >>>>
> >>> Will the fix for issue #3275 be included in 1.5.5?
> >>> It is a P1 one.
> >> I agree that this is an important bugfix. Unfortunately, if we don't
> get
> >> other eyes on it soon, it will not be included in the release.
> >
> > I do not think we should do the release until all of the issues in
> > STATUS are cleared. I do not mean that as a general policy statement,
> > just that of the bugs that are still in STATUS, several of them are P1
> > nature. The --reintegrate bug fix goes a long way towards solving the
> > #1 problem with the 1.5 release. I cannot see why we would do another
> > bug fix release without this fix now that it exists.
>
> If you want specific revisions in the next patch release, then encourage
> people
> to review the items in STATUS.
>
> The entire point of doing time-based releases (patch or feature) is that we
> can
> just release what we've got when the time hits. There are always
> exceptions to
> the rule, but I think they should be few and far between. We need to think
> hard
> before making them. If developers (myself included) aren't willing to
> review
> items which have a known impact to our user base, we've got deeper issues
> at
> play, and no amount of postponement will fix them.
>
> It's been no secret for the *last month* that 1.5.5 was rolling on 12/17.
> The
> reintegrate improvements branch was nominated on 12/2, two weeks ago. I
> find it
> difficult to believe that postponing the release an indefinite amount of
> time
> will speed review, when nothing has happened on that item in the past two
> weeks.
> (To the contrary, actually, I find that hard release dates actually
> encourage
> increased review.)
>
> In the end, I'm just a reflection of the community, and enough people say
> "hold
> the release", I'll do so. But know that I'm taking that action under
> protest. :)
>
> -Hyrum
>
> PS - Mark, nice to see you've got power back.
>
> ------------------------------------------------------
>
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=985046

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=985054
Received on 2008-12-16 16:54:32 CET

This is an archived mail posted to the Subversion Dev mailing list.