> The Go tree is still in a code freeze but I'll have those > CLs submitted as soon as it reopens. > > Also, we have three months (until the Go 1.3 code freeze) to > get the Plan 9 port passing all tests on the build dashboard > or it will have to move outside the main repository:
there is no demotivation in open source as powerful as a threat. is the threat standing? that is, if the plan 9 port is broken again when 1.5 rolls around in just a few more months, does the plan 9 port get booted then, too? personally, i think a preemtive strike is in order. a lot of time has been spent chasing basic broken-with-merge issues, the rather superfluous libbio macros, the self-inflicted memmove problem, &c. those are just recent issues. given the rate of go development, i would think this is likely to continue. - erik
