>>> - should I attach this stuff to THRIFT-582 as a massive patch? not
>>> sure how well that would work, as there will still be a lot of future
>>> updates. I'm happy to just continue to work on github, or use something
>>> else if there are suggestions.
>> Yes, you should attach a massive patch, since that is the easiest way for
>> us to document the history of the code. Keeping an active branch on github
>> is also good to allow more detailed analysis of the development process.
>
> Should we do that now, or later, once the server implementation is
> complete and the tests have full code coverage?
Either.
