<br>Having a separate public development repo for the experimental stuff is <br>a good idea. Maybe we can ask for project space on the <a href="http://code.haskell.org">code.haskell.org</a> <br>community server? They have all the infrastructure in place already.<br>
<br>Balazs<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>Hm. I certainly agree that testing and API review is required for<br>
release. However I'd prefer other developers to have easy access to<br>
these patches through a main development repository than not. If API<br>
stability is a concern with the main repository then I suggest having<br>
two repositories: One for development and another for stable use.<br>
<br>
Cheers,<br>
<font color="#888888">Corey<br>
</font><div><div></div><div class="Wj3C7c"><br>
> On Wed, Dec 17, 2008 at 6:58 PM, Corey O'Connor <<a href="mailto:coreyoconnor@gmail.com">coreyoconnor@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Excellent stuff! I like having the framebuffer texture functions check<br>
>> the status as well. That's a handy addition.<br>
>> So how do we get your patch into the mainline repo? I'd hate to have<br>
>> another person duplicate the same work again.<br>
>><br>
>> Cheers,<br>
>> Corey O'Connor<br>
>><br>
>><br>
><br>
><br>
</div></div></blockquote></div><br>