From: Siggi L. <si...@us...> - 2004-08-30 23:18:54
|
Hi Stephen, On Mon, 30 Aug 2004, Stephen torri wrote: > Do we have a scoreboard of tests like yours that we use for a release? > For example, if all the tests on the scoreboard are green then we have > passed all the regression testing for things xine supports. Therefore > xine-lib is good to go for a new release. Althought that question was not directed to me: We only have Thibaut's scoreboard, and it has never been completely green before. However, it's a good guideline about what has to be fixed ;-) WRT releases, one should probably document the red parts for each release. > > > 3) Is there a way to freeze the CVS repo so that a nightly build can be > > > done without interferrence ? > > > > why ? The testsuite does a cvs checkout, developers are supposed to keep the repository in a compilable state. > > A project that I use will freeze the repo before a release. They do so > to let any bug-fix only patches to go in. Once the build is done the > repo is unfrozen (thawed) for general usage. What we usually do is an informal freeze: The release manager writes to -devel that we are going to release and asks developers to commit only safe, well-tested patches and concentrate on bugfixes while holding new features back. > > > Perhaps this could be a training of a young padawan master Siggi. > > > > the release or the testsuite announcement ? > > I am available to help learn how to do a release. Okay Stephen, you've got the job. Your first step is to lay out a realistic release schedule and announce that on the mailing list, considering all "show-stopper" bugs that should be fixed in this release. Cheers, Siggi |