Peter McNab wrote:
> > Maybe a thumb rule to only include feature additions after they've
> > soaked for a week or two?
>
> I'm way behind the conversation now but harking back to the above, who
> then does the soak testing?
Community people has a lot to do already, but perhaps they could be
intrigued into testing if they were offered a list of new features to
test (on a regular not-too-often basis ;-)).
TSVN responsibles for larger corporations could probably be persuaded
to test RCs.
We would probably need a 'tsvn announcements-only' mailing list for them.
Automated testing could work too, but it's harder when it's a GUI app.
There's tools for GUI testing covering most price ranges, from quite
expensive to $100
(http://www.snapfiles.com/features/robotask-702-466640.php), but I
haven't seen any free-as-in-beer alternatives ;-/.
I think the most realistic approach would be:
Branch for release every month. For the next week after the branch,
someone (I'm not saying Stefan!) would merge bugfixes *only* from
trunk to the branch. After that week has passed, the release is cut
from branch (probably by Stefan).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Oct 25 13:58:38 2005