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

Re: Fwd: Proposal: RCs with ZERO overhead

From: <Stefan.Fuhrmann_at_etas.de>
Date: 2006-06-22 17:12:56 CEST

Stefan Küng wrote:

> > Note, that there is no extra build after the RC
> > (provided that no regressions are found). As I understand
> > the RC handling for major releases, the final version
> > will require an extra build & upload cycle.

> And that's exactly what I don't like at all (sorry). Imagine we provide
> an RC with already the version information as the actual release will
> have (even ommit the 'RC' or '-dev'). Then we find a bug and have to do
> yet another release. Then we'd have two releases with the same version
> information out there.

Not necessary. We just wouldn't release x.y.z but x.y.z+1 instead
(creating just the same number of versioned builds as today).

But I'm not an opponent to "nightlies are RC" approach. So let's
got for that and see how things work out.

> >> I'm not sure we should do the same for bugfix releases as we already
do
> >> for major releases. I don't know of any project out there which does
RCs
> >> for bugfix releases.
> >
> > We do ;) at our company (with an even much more
> > elaborate process behind).
>
> but also with a lot more people (who get paid!) to do the work.

When it comes to company-wide software roll-out, there may be a
number of people that get actually paid for testing our software.
So, it might not be too far fetched to assume that some of our
testers might even get payed for it by their companies.

> I was thinking of just announcing the RC on the mailing list and wait
> until the X amount of people replied to it indicating that they have
> installed it. Then wait Y days for problem reports and if nothing
> serious comes up, make the final release.

Sounds like the simpliest way to do it.

> > Also, we might think of some incentive (most obvious:
> > listing them in some appropriate place). Testing is a *very*
> > unpleasant task after all.
>
> That list would be *huge*!

It was just a random thought that occured to me the other day:
How could we attract and hold in-depth testers?
What kind of incentive could we offer?

So far, I couldn't find a satisfying answer.

-- Stefan^2.
Received on Thu Jun 22 17:13:13 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.