-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
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. |
The frontend repo is marked as |
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 |
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). |
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. |
I've added milestones and currently open issues tagged as |
A lot of the issues are assigned to @redbassett but I'm happy to tackle some of them, as well. |
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.
The text was updated successfully, but these errors were encountered: