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.

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

Consider migrating front-end issues to this repo #2

Open
hawkw opened this issue Jul 13, 2015 · 7 comments
Open

Consider migrating front-end issues to this repo #2

hawkw opened this issue Jul 13, 2015 · 7 comments

Comments

@hawkw
Copy link
Contributor

hawkw commented Jul 13, 2015

If we end up using this repo for front-end dev, we may want to consider moving all of the front-end tasks from the main Alexandria repo to this repo, so that they can be referenced (and closed) by commits/PRs from this repo

On the other hand, it's nice to have all the issues in one place, so that they can all be part of the same milestones, et cetera. Therefore, we might want to continue tracking all issues on the main Alexandria repo. Alternatively, we could consider tracking tasks/issues externally from GitHub.

@hawkw hawkw added the question label Jul 13, 2015
@hawkw
Copy link
Contributor Author

hawkw commented Jul 13, 2015

Another question: how do we intend on versioning the front-end? Will it be versioned together with the backend or will it be versioned separately? We might want to consider using the same release scheme/milestones for both projects but tracking separate version numbers for the front-end and backend since they are pretty decoupled.

@redbassett
Copy link
Member

The frontend repo is marked as experimental specifically because I'm still figuring these out. Versioning is done most easily in the bower.json file, which already has a version number. I'm good moving all frontend issues to the separate repo. As for milestones, the new frontend code has to go into the backend so it is served once a version is complete, but I'm not sure this process.

@hawkw
Copy link
Contributor Author

hawkw commented Jul 13, 2015

Yeah. I know all this stuff is currently experimental, I just meant for eventually. I think the way we'd want to main-line front-end code would be using git subtree to include the compiled front-end code in the src/main/webapp directory in the back-end repo, and updating the subtree commit every time a new front-end version is ready.

@redbassett
Copy link
Member

We could use a separate repo just for issues/wikis, but I'm fine keeping issues on the appropriate repo until any issues arise (once this repo goes official).

@hawkw
Copy link
Contributor Author

hawkw commented Jul 15, 2015

We could use a separate repo just for issues/wikis

We could do that. I just like having the issue tracker be on the same repo as the code, so that issues can be referenced/closed from commit messages.

@hawkw
Copy link
Contributor Author

hawkw commented Jul 15, 2015

I've added milestones and currently open issues tagged as frontend to this repo. Currently, they all just contain pointers back to the associated issues on the main repo.

@hawkw
Copy link
Contributor Author

hawkw commented Jul 15, 2015

A lot of the issues are assigned to @redbassett but I'm happy to tackle some of them, as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants