Open dkingofpa opened 11 years ago
This makes sense to me.
On Thu 10 Jan 2013 11:02:56 PM EST, David King wrote:
Just wanted to get some feedback on the current structure of xforty-drupal.
Creating a repo per drupal version would allow us to use git-flow for easier development. It would also allow us to periodically drop some baggage when a new major version of drupal is released. Currently, we have close to 300 tags in xforty-drupal and it's only going to grow (slower than before though). Repo names could be xforty-drupal7, xforty-drupal8, etc. The current xforty-drupal could be considered legacy and be left for existing projects.
Creating a new branch when drupal releases a new major version allows us to do nothing right now.
— Reply to this email directly or view it on GitHub https://github.com/xforty/xforty-drupal/issues/11.
This too makes sense. This repo was started prior to any knowledge of git-flow. I would like to propose clone xforty-drupal local. Remove the 6.x branch, rework the 7.x branch into git-flow, and remove all the tags that are not needed. Then we can drop the xforty-drupal remote origin in favor of a xforty-drupal7 on github.
Also with doing this, we should work through and close out all the issues.
Just wanted to get some feedback on the current structure of xforty-drupal.
Creating a repo per drupal version would allow us to use git-flow for easier development. It would also allow us to periodically drop some baggage when a new major version of drupal is released. Currently, we have close to 300 tags in xforty-drupal and it's only going to grow (slower than before though). Repo names could be xforty-drupal7, xforty-drupal8, etc. The current xforty-drupal could be considered legacy and be left for existing projects.
Creating a new branch when drupal releases a new major version allows us to do nothing right now.