GHC API Refactorings - To Merge or not to Merge?
marlowsd at gmail.com
Fri Aug 29 09:51:58 EDT 2008
Ian Lynagh wrote:
> On Fri, Aug 29, 2008 at 11:35:38AM +0200, Thomas Schilling wrote:
>> (1) Ok, thinking about it, it would probably Ok to merge it in
>> after the 6.10 branch, but then backporting changes to 6.10 would
>> become very difficult. Maintaining it as a long-running branch would
>> be involving, though.
> If the 3 options are:
> 1) Merge before 6.10
> 2) Merge just after 6.10
> 3) Merge some time before 6.12
> then I would vote for 1.
> 2 is a pain for merging fixes to the stable branch, and 3 is a pain for
> merging fixes from the HEAD.
> Also, I expect the number of GHC API clients is going to grow rather
> than shrink, so if we're going to break them all at some point then we
> should do it sooner rather than later.
I concur with Ian. If we also port Haddock, and the changes pass the
testsuite, I don't see a good reason why we shouldn't bring this in now.
But it better be now (i.e. next week), otherwise we're too close to RC.
More information about the Cvs-ghc