
Having a separate public development repo for the experimental stuff is a good idea. Maybe we can ask for project space on the code.haskell.org community server? They have all the infrastructure in place already. Balazs
Hm. I certainly agree that testing and API review is required for release. However I'd prefer other developers to have easy access to these patches through a main development repository than not. If API stability is a concern with the main repository then I suggest having two repositories: One for development and another for stable use.
Cheers, Corey
On Wed, Dec 17, 2008 at 6:58 PM, Corey O'Connor
wrote: Excellent stuff! I like having the framebuffer texture functions check the status as well. That's a handy addition. So how do we get your patch into the mainline repo? I'd hate to have another person duplicate the same work again.
Cheers, Corey O'Connor