I'm with Chris on this: Once you've included it, it's in. That is - people will code against those packages - because, well, there they are! "levels of warranty" as listed on some web page aren't really going to imply much!
So, I think if a package is included, all it's dependencies need to be included too. I hereby commit to publishing a list of "what I need from the package maintainers of platform packages" this weekend. While the process and criteria for the platform has not changed (until this group decides to change them), this will list the practical needs I see as release manager. As for all those packages, aeson is essential. We must get it in! Perhaps it might be best on bos if we don't heavily load this release with new packages from him. Not that I don't like those others, but I imagine, in part because of all the dependencies, they will be more of a slog.... and perhaps we could get the process rolling better first. - Mark
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
