On 14 Apr 2011, at 12:56, Søren Hauberg wrote: > ons, 13 04 2011 kl. 23:04 +0200, skrev Thomas Weber: >> is there a way to test releases before they are released (hmm, sort of >> recursive statement)? I have 3 test failures in the 1.0.14 image >> package and I think that each one of them is in the package, not in my >> installation. > > I guess we can have a beta period for package releases. We could agree > to upload the package to the SF server, but not update the web pages > (thereby making the package quite hard to find). This would give some > people a chance to test. This does seem like a rather dirt solution, so > alternative suggestions are most welcome. > > Regarding the image package, then I guess I just did a sloppy piece of > work with the release (sorry). I can make a 1.0.15 release with bug > fixes, though (assuming I can find the bugs in the little time I have > available). > > Søren
I think that having commands like pkg test <pkg_name> and pkg demo <pkg_name> would help in this testing phase. We could then require that the package maintainer include the results of the test in the submission post. IIRC this was even discussed on the developers list some time ago. I might implement this feature myself but it would take very long as I am very busy lately, so please feel free to beat me to it ;) c. ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
