* Knut Yrvin <[EMAIL PROTECTED]> [050131 16:28]: > Before releasing Skolelinux 1.0 Venus we made 47 prereleases and 3 > release candidates. We started with the woody-based developer branch > in June 2001. Today this work is manly sarge based. But it's a > difference in how the testing and releasing is done that could be > improved. > > * What am I asking for? > > I am an highly skilled system developer that are able to file bugs, > and do much testing of the daily builds and prereleases. I know of a > whole lot of teachers and maintainers of small and huge > Skolelinux-installations that has made a test bench for testing the > new versions of Skolelinux. I can't set them to work with testing the > sarge version of Skolelinux because I don't know where to start, or > which CD that should be tested. It's no report that shows the work in > progress, and to collect the bugfixes in bugzilla is to > complicated. The result is that a lot of hands and heads walking > around unemployed with "to much" spare time. They have the equipment, > and just waiting to help. So where are the release notes and the > prereleases? Then we could organise the people that are interested to > give us a hand. This is contributors that are not so familiar with the > daily-build and the track of the date and hours, to test prereleases > and give the developer and bug-tracking system feedback. This is the > people that loves that Skolelinux is as simple as possible. ...
I support this. We need prereleases for sarge to coordinate the development. We testet in our lern- and testcenter different versions. We have to bring the information together and so we have to have prereleases. So please, is someone able to do this. I propose Petter, what do you think about? Comments welcome! Regards/Viele Gruesse! Kurt -- [EMAIL PROTECTED] GnuPG Key ID 0xE263FCD4 http://www.skolelinux.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
