search

TonicAudio / Tonic

Easy and efficient audio synthesis in C++
The Unlicense
523 stars 63 forks source link

Branching Strategy #175

Closed ndonald2 closed 11 years ago

ndonald2 commented 11 years ago

@morganpackard since we each have a few branches with changes specific for our own projects, I'm wondering if it's better for us to fork Tonic to our own github profiles for that. It might be cleaner if the master repo only has a few branches (master, development, and specific feature branches) and for any changes made for a project that make sense to merge back to the master repo, we can just open a pull request from our own repo back to the master.

If that sounds good to you I will update the wiki.

morganpackard commented 11 years ago

The same had occurred to me. ThicketLeap doesn't belong under the Tonic umbrella, belongs under my own umbrella.

On Thu, Jun 6, 2013 at 8:23 PM, Nick D. notifications@github.com wrote:

@morganpackard https://github.com/morganpackard since we each have a few branches with changes specific for our own projects, I'm wondering if it's better for us to fork Tonic to our own github profiles for that. It might be cleaner if the master repo only has a few branches (master, development, and specific feature branches) and for any changes made for a project that make sense to merge back to the master repo, we can just open a pull request from our own repo back to the master.

If that sounds good to you I will update the wiki.

— Reply to this email directly or view it on GitHubhttps://github.com/TonicAudio/Tonic/issues/175 .

Morgan Packard cell: (720) 891-0122 aim: mpackardatwork twitter: @morganpackard

ndonald2 commented 11 years ago

Wiki updated. I'll trust you to clean up the branches when you have time. Thanks!