On Thursday 26 November 2009 10:56:14 Jan-Oliver Wagner wrote: > I've observed the usual problem: as long as versions are "beta" > the packages are very much hesitating to touch it. > > Boldy going ahead with the version number seems to be the > only practical approach to get things moving.
I totally agree with you that beta stuff isn't very inviting to test. However, fixing the stuff up, ironing out any remaining (build) issues so binaries can be provided to all major platforms seems to be more important to me than releasing a RC that's mostly only worth to people who are comfortable building it from SVN anyways. Perhaps I'm somehow "oldschool" but IMHO a RC should be in release state so if no more issues are found the RC is declared as GA which currently simply can't happen for various reasons. So first fix most if not all found issues so binaries can be made available to a wider area of testers and then declare it a RC so people have a good thing to test. Then fix the swamp of bugs that surely comes in and once they are fixed think about declaring it a GA so you have a solid one instead or the usual premature one (the premature isn't targeted at you but a general observation which is even more important since your stuff is a security tool) My thoughts, Stephan _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
