Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reconciling gem-plate-map and master. #16

Closed
gorj-tessella opened this issue Sep 20, 2017 · 4 comments
Closed

Reconciling gem-plate-map and master. #16

gorj-tessella opened this issue Sep 20, 2017 · 4 comments
Assignees
@gorj-tessella

Comments

@gorj-tessella
Copy link
Contributor

The gem-plate-map branch is being actively developed, however all changes are applicable to master. The problem is that the two branches have different hierarchies.

We need to decide if both branches should be maintained, or only the gem version. Alternatively, we could have a separate project for the gem version, but then things will need to be updated twice.
@bwlang
Copy link
Member

bwlang commented Sep 21, 2017

i think we should just keep the gem version - easier to deploy.

@gorj-tessella gorj-tessella mentioned this issue Sep 27, 2017
Closed
@gorj-tessella gorj-tessella self-assigned this Sep 27, 2017
@gorj-tessella
Copy link
Contributor Author

OK, I will make features/ekappotis/plate-map-gem the new master. I will retain the old master.

@gorj-tessella
Copy link
Contributor Author

Merged master, deleted features/ekappotis/gem-plate-map

@gorj-tessella
Copy link
Contributor Author

The state of the old master is now on branch plain-js

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gorj-tessella gorj-tessella

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bwlang @gorj-tessella