Re: [Jsynthlib-devel] Name for refactored branch

[Vladimir A. <vl...@gm...>]

On 09/01/2011 07:54 PM, Joe Emenaker wrote:
>
> Okay, I think I understand Subversion enough to be dangerous.
>
> I'll need to make a branch to upload my refactored version to. All of
> the branches seem to be named after version numbers, but my
> understanding is that we can name them anything (like "my_cool_branch").
>
> Should I name it some step forward in version number (like 0.3,
> perhaps), or name it something like "refactor"? What does the group
> think is the best way to go on this? Personally, I'd prefer the version
> number because, 1) I consider this to be a rather significant step
> forward in the "sorting out" of the mess of classes that is the main JSL
> codebase (hence, my desire to call it something like v0.3), and 2) it's
> more in keeping with the current naming convention in the branch
> folder... so it'll be easier for people to see where it fits in with the
> rest of the versions.
>

I  like naming branches in more descriptive way, so if someone would 
browse repository he could get general idea right from top view.

Naming towards release is not very descriptive, and the plans for next 
release are not documented anywhere.

I would also suggest somewhat further structuring of branches directory. 
You can create subdirectories there based on the purpose of branches 
inside. I could think of three directories: fixes, features, users.

Fixes would be for involved bug resolutions.

Features for development extensive changes.

Users for developers to fiddle with whatever staff the prefer to work at 
the moment.

In such scheme of things you changes would go into features probably.

Just my 2 cents

Regards,
Vladimir