[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 Küng <tortoisesvn_at_gmail.com>
Date: 2006-06-19 11:38:39 CEST

On 6/18/06, Tobias Schäfer <tobiasschaefer@gmx.de> wrote:
> > So, we would need 'stable' testers, which have to follow some few rules:
> > * install every stable nightly build, when they get notified by mail
> > * use that nightly build as their main build
> > * report back any problem they encounter
> > * if they can't install the nightlies anymore (vacation, no time, ...)
> > they must tell us so we can find replacements
> > * maybe (to have some control over who really is using those nightlies)
> > we could require them to send a short notice every time they install
> > such a nightly (e.g. subject: installed stable nightly, body=revision
> > XXXX, date of installation, x64/win32, processor-type (single/dual) ).
> Sounds good. To make it a little easier for the testers and make it easier
> for the developers to follow which release has been installed/tested by
> whom I'd change it a little:
> Whenever a revision is merged into the stable branch a mail is sent to a
> mailing list (users@ dev@ or maybe a new list). Everyone who installs a
> nightly stable build, just replies and mentions the installation date,
> platform and processor-type.

Good idea. Replying is much easier :)

Should we create a new mailing list for this? I think the dev list
could handle those few mails, after all, they're only text (no
attachments). And I'm sure the testers will just reply again if they
find a bug to report. And those definitely belong on the dev list.
So I'm in favour of keeping that on the dev list.
Other opinions/reasons?

> The advantages of informing of a new stable build by mail:
> - no need to watch the changelog for changes in the branch because the
> testes will be informed by mail
> - all replies to nightly build will be grouped together assuming that
> replies are shown as threads in the mail client
> This is similar to the signing of release candidates on dev@subversion. As
> Stefan mentioned there should be couple of key testers whose replies are
> required, but further testers are welcome to answer too.

But the signing process happens *after* the subversion devs have
tested a tarball. Our mail-based system would require those mails to
be sent right *before* they test, i.e. when they *start* testing by
simply installing it.
So I'd say that such a release could be considered 'signed' about x
days after y testers replied to such a mail.

Now, let's define x and y.
My suggestion:
x = 5
y = 5

> Who sends the message? It could be sent automatically when Stefan manually
> trigggers the build of the stable branch. It doesn't make sense that the
> developer sends the mail because at that time the build has not been
> triggered yet.

I just send the mail after I triggered the build and confirmed that it
was uploaded correctly.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jun 19 11:38:53 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.