[Linux-ha-dev] 2.1.1 is imminent

[Lars Marowsky-Bree]

On 2007-07-13T10:13:28, Max Hofer <max.hofer at apus.co.at> wrote:

> But what is it good for running regression tests (which i hope you
> guys do before releasing a new version) if you pull code from dev to
> test branch 3 days before the release should come out?

Well, dev is being constantly tested already; it's not as if we sit idle
for months (some of us might) on the project and only test in a 3d
timeframe, ever ;-)

We're asking for additional resources to validate the release further.

Pre-compiled packages for testing are conveniently available from
http://software.opensuse.org/download/home:/LarsMB/.

> I always thought there is a kind of fteaure freeze (means where the
> dev becomes test) and then a time period where regresison tests are
> done on the test branch.

Yes, for this it would have been useful to know the schedule in
advance. On the other hand, we do have on-going testing.

> Bugfixing for failed tests takes place on the test branch (with puling
> the fixes back to the dev branch). But no new feature are going into
> the test branch.

> Here my questions:
> * when was the feature freeze for 2.1.1?
> * how long is the period of regression tests? (rough estimation)
> * does there exits a person which is responsible to coordinatate the
> developers during this period? (I know it is funnier to code on the
> dev than on test but hey, life sucks sometimes ;-) )

Well, known bugs get fixed either in dev or in test; doesn't really
matter where, as long as they end up in the release and get pulled over
by the release coordinator.

So even developers who continue to work on dev will contribute to the
quality of the release. It's the release manager's duty to decide
whether a fix should go into it still or not.

> * there was no roadmap for 2.1.0/2.1.1 release. Could someone please
> provide a roadmap for 2.1.2? (fix the date for code freeze, estimated
> regression test period now, and release date for 2.1.2 now ---> put it
> on the homepage)

My, wouldn't that be a good idea. ;-) I've asked for that since 5 years.
Good luck.

> If there is not such kind of roadmap people work on dev all the time,
> persons like me who would like to test for a release have no clue
> which release we should test, and against what we should report bugs.

Well, bugs which are in test are in dev; bugs which are in dev are (very
likely) in test as well. It doesn't really matter. ;-)

> Thank god it is Friday: do you really expect that we gonna test over
> weekend? ;-)

People who don't get paid to work on heartbeat but for whom it is a
"hobby" project are probably more likely to do that on the weekend then
during the week, so I assume it doesn't matter when you test, as long as
you do report the issues you find ;-)


Regards,
    Lars

-- 
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde