Since we have accepted GCV4.1 as the default and GCV5 as the development GC based on several list discussions, I think that we may be OK with announcing that GCv4 is deprecated, and maybe taken out of the active tree by end of 2006?
Patches that are still coming in that only work with GCV4, probably began development quite a while ago ... since the default code does not pick up GCV4, I am not sure how they are passing acceptance tests, unless their functionality is not covered by the existing tests. Anyway, this is risky IMHO, since as soon as we add the right test to the acceptance suite, the functionality will fail( since we will only run tests with default paths ). Anyway, announcing deprecation will only help, IMHO. Thanks for bringing this up. Rana On 11/4/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Yeah, put some logging statements in. Ask Tim if you need some help ;) I think we can do as you suggest, or simply document it somewhere. Cleaerly if someone knows enough to switch GC, they have hit a manual or code somewhere. I guess when I asked the original question, I was thinking that we should just be clear that it's now deprecated, and therefore except for required changes to keep compatible w/ the interface to GC, nothing should change it. This was driven by my noticing that there was some recent patches that worked on GCv4, not 4.1... geir
