How would this differ from just putting candidate package versions on Hackage? What would be the advantage to making a "Platform Candidate" that has APIs that could "undergo radical API changes"?
Currently, the burden on the HP team doesn't stem from 'unproven' packages. We already only deal with 'proven' packages. Adding an alternate release style would only increase the burden and we don't really have the volunteer bandwidth for more.
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
