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...@lyra.org> on 2003/12/21 02:09:00 UTC

soak time (was: Ann: Subversion 0.35.1 released)

We settled on a week of "soak time" simply to avoid patch releases like
this right after releasing. If we *still* do little patches like this,
then wtf do we have a soak time for?

I'd like to suggest that we just dispense with the soak time. It is
certainly not preventing patch releases. Yes, I know that other patches
got into 0.35 that may not have been there, but we released a 0.35.1
anyways. They could have gone there.

And yah, I know that the release is going to be way stable now anyways, so
risks are low and soak isn't needed. Mostly, I'm talking about when we
start making regular releases again next year. Screw the soak time and the
delay it introduces. Just stick with bi-weekly releases. If you miss a
release, then wait for the next. It isn't very far off. If the problem is
critical, then sure: we make a patch. But the soak time that we're
providing is only giving us time to integrate non-critical, and is not
saving us from patch releases for the critical items. Thus, I consider the
experience so far to be a failure.

Cheers,
-g

On Sat, Dec 20, 2003 at 05:20:30PM +0100, Jostein Chr. Andersen wrote:
> The latest interim bugfix release of Subversion is ready at
> 
>    http://svn.collab.net/tarballs/subversion-0.35.1.tar.gz
> 
> The MD5 checksum is c4473988acdd82e8b0e176eefc7d0fb7.
> 
> CHANGES:
> -----------------------------------------------------------
> Version 0.35.1 (branching 19 December 2003, from /tags/0.35.0)
> http://svn.collab.net/repos/svn/tags/0.35.1
> 
>                               NOTICES:
> 
>        This release is to correct for the problems in the 0.35.0
>        release and affects Windows users only:
> 
>        * fix: file handle leak (r8048)
>        * fix: UTF-8 path problem (issue #1660)
> -----------------------------------------------------------
> 
> 
> Please direct questions/comments to the users@subversion.tigris.org
> and/or dev@subversion.tigris.org mailing lists.
> 
> Jostein
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

-- 
Greg Stein, http://www.lyra.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: soak time (was: Ann: Subversion 0.35.1 released)

Posted by "Jostein Chr. Andersen" <jo...@webconnect.no>.
Greg Stein wrote:
> saving us from patch releases for the critical items. Thus, I consider the
> experience so far to be a failure.

I'm not sure that it was the system's (the soak time idea) failure.

I'm the one to blame here because I saw that Branko wrote this message to
the dev list (an answer to my 'branch 0.35.0: All my "make tests" are ok..'
posting): 

  http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=52737

That thread should have prevented me from releasing 0.35.0. So, I'm the one
to blame. Not the system and not anyone else.
The dev list was wery noizy that day, but I can't even find exuses here:
-I'm using kmail in threded mode so I have full vue of what's happening
there.

Sorry folks.

Jostein



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: soak time (was: Ann: Subversion 0.35.1 released)

Posted by Sander Striker <st...@apache.org>.
On Mon, 2003-12-22 at 21:56, solo turn wrote:
> --- kfogel@collab.net wrote:
> > I don't think the "soak time" system itself is broken, we just had
> > some human error this time.  No system is going to eliminate that
> > completely, but the soak time is still valuable...

I agree.

> i like gregs proposition, as human errors are possible and do not matter.

In this case I think it certainly does matter.

> for deployment, we always keep a week soak time,

We?

> which means if releasing takes a week soak time and we do another
> week, we are at two weeks now ...

The Subversion project doesn't take 3rd party deployment soak time into
account.  The soak time is there so that the critical features that are
destined for a release aren't committed on the day of the deadline and
released the same day.  Since we do branch on the day of the milestone,
testing can occur for an entire week to flush out issues.  Basically
nothing but critical bugfixes should be included on the branch.

It helps when the people involved with the various aspects of the
release process would test on the branch day (or close after).


Sander


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: soak time (was: Ann: Subversion 0.35.1 released)

Posted by solo turn <so...@yahoo.com>.
i like gregs proposition, as human errors are possible and do not matter. for deployment, we
always keep a week soak time, which means if releasing takes a week soak time and we do another
week, we are at two weeks now ...

--- kfogel@collab.net wrote:
> I don't think the "soak time" system itself is broken, we just had
> some human error this time.  No system is going to eliminate that
> completely, but the soak time is still valuable...
> 
> -K
> 
> Greg Stein <gs...@lyra.org> writes:
> > We settled on a week of "soak time" simply to avoid patch releases like
> > this right after releasing. If we *still* do little patches like this,
> > then wtf do we have a soak time for?
> > 
> > I'd like to suggest that we just dispense with the soak time. It is
> > certainly not preventing patch releases. Yes, I know that other patches
> > got into 0.35 that may not have been there, but we released a 0.35.1
> > anyways. They could have gone there.
> > 
> > And yah, I know that the release is going to be way stable now anyways, so
> > risks are low and soak isn't needed. Mostly, I'm talking about when we
> > start making regular releases again next year. Screw the soak time and the
> > delay it introduces. Just stick with bi-weekly releases. If you miss a
> > release, then wait for the next. It isn't very far off. If the problem is
> > critical, then sure: we make a patch. But the soak time that we're
> > providing is only giving us time to integrate non-critical, and is not
> > saving us from patch releases for the critical items. Thus, I consider the
> > experience so far to be a failure.
> > 
> > Cheers,
> > -g
> > 
> > On Sat, Dec 20, 2003 at 05:20:30PM +0100, Jostein Chr. Andersen wrote:
> > > The latest interim bugfix release of Subversion is ready at
> > > 
> > > ���http://svn.collab.net/tarballs/subversion-0.35.1.tar.gz
> > > 
> > > The MD5 checksum is c4473988acdd82e8b0e176eefc7d0fb7.
> > > 
> > > CHANGES:
> > > -----------------------------------------------------------
> > > Version 0.35.1 (branching 19 December 2003, from /tags/0.35.0)
> > > http://svn.collab.net/repos/svn/tags/0.35.1
> > > 
> > >                               NOTICES:
> > > 
> > >        This release is to correct for the problems in the 0.35.0
> > >        release and affects Windows users only:
> > > 
> > >        * fix: file handle leak (r8048)
> > >        * fix: UTF-8 path problem (issue #1660)
> > > -----------------------------------------------------------
> > > 
> > > 
> > > Please direct questions/comments to the users@subversion.tigris.org
> > > and/or dev@subversion.tigris.org mailing lists.
> > > 
> > > Jostein
> > > 
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > > For additional commands, e-mail: dev-help@subversion.tigris.org
> > 
> > -- 
> > Greg Stein, http://www.lyra.org/
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
> 


__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: soak time (was: Ann: Subversion 0.35.1 released)

Posted by kf...@collab.net.
I don't think the "soak time" system itself is broken, we just had
some human error this time.  No system is going to eliminate that
completely, but the soak time is still valuable...

-K

Greg Stein <gs...@lyra.org> writes:
> We settled on a week of "soak time" simply to avoid patch releases like
> this right after releasing. If we *still* do little patches like this,
> then wtf do we have a soak time for?
> 
> I'd like to suggest that we just dispense with the soak time. It is
> certainly not preventing patch releases. Yes, I know that other patches
> got into 0.35 that may not have been there, but we released a 0.35.1
> anyways. They could have gone there.
> 
> And yah, I know that the release is going to be way stable now anyways, so
> risks are low and soak isn't needed. Mostly, I'm talking about when we
> start making regular releases again next year. Screw the soak time and the
> delay it introduces. Just stick with bi-weekly releases. If you miss a
> release, then wait for the next. It isn't very far off. If the problem is
> critical, then sure: we make a patch. But the soak time that we're
> providing is only giving us time to integrate non-critical, and is not
> saving us from patch releases for the critical items. Thus, I consider the
> experience so far to be a failure.
> 
> Cheers,
> -g
> 
> On Sat, Dec 20, 2003 at 05:20:30PM +0100, Jostein Chr. Andersen wrote:
> > The latest interim bugfix release of Subversion is ready at
> > 
> >    http://svn.collab.net/tarballs/subversion-0.35.1.tar.gz
> > 
> > The MD5 checksum is c4473988acdd82e8b0e176eefc7d0fb7.
> > 
> > CHANGES:
> > -----------------------------------------------------------
> > Version 0.35.1 (branching 19 December 2003, from /tags/0.35.0)
> > http://svn.collab.net/repos/svn/tags/0.35.1
> > 
> >                               NOTICES:
> > 
> >        This release is to correct for the problems in the 0.35.0
> >        release and affects Windows users only:
> > 
> >        * fix: file handle leak (r8048)
> >        * fix: UTF-8 path problem (issue #1660)
> > -----------------------------------------------------------
> > 
> > 
> > Please direct questions/comments to the users@subversion.tigris.org
> > and/or dev@subversion.tigris.org mailing lists.
> > 
> > Jostein
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
> 
> -- 
> Greg Stein, http://www.lyra.org/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org