I was actually referring to documenting it as _methods_ in
MCVersionName; not the class-comment (but there's no harm in putting
it there too).

But before I would do that, I would want to make sure there was
consensus and then code, tests, inbox, testing, etc..


On Tue, Apr 19, 2011 at 4:31 AM, Hannes Hirzel <hannes.hirzel at gmail.com> wrote:
> On 4/19/11, Chris Muller <asqueaker at gmail.com> wrote:
>> Thanks for the great clarification about branches, it makes total
>> sense.  And, I can understand how a naming-convention would be plenty
>> good enough for that situation.
>>
>> If we do choose to adopt / document this convention, we should capture
>> it in MCVersionName.  :-)
>
> Please do so, for people who did not follow this discussion closely
> and after a few weeks it willl be forgotten. However looking at the
> class coment of MCVersionName might not be the most obvious thing to
> do but still it is a likely place where people will stumble upon....
>
> --Hannes
>
>