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

Combine template library repositories #309

Open
jrha opened this issue Oct 26, 2017 · 5 comments
Open

Combine template library repositories #309

jrha opened this issue Oct 26, 2017 · 5 comments
Milestone

Comments

@jrha
Copy link
Member

jrha commented Oct 26, 2017

Merge template-library-core and template-library-standard into a single repository named template-library, the history must be preserved https://github.com/unravelin/tomono may help with this.

Hold off on merging template-library-os and template-library-grid until we can reach a consensus on what to do with the multiple "master" branches.

@jrha
Copy link
Member Author

jrha commented Oct 26, 2017

  • Documentation will also need to be updated to reflect new locations.
  • Release and build_all_repos scripts will need to ne updated to operate on new locations.

@ned21
Copy link
Contributor

ned21 commented Oct 26, 2017

Agreed at RAL workshop that it would be nice to consolidate all templates into one repository but first need agreement on whether we can move away from the per-release development workflow which would cause a single repo to have an unmaintainable number of branches.

@jrha
Copy link
Member Author

jrha commented Oct 26, 2017

Individual repository indentity should translate to subdirectories, e.g.
Files from template-library-core should go in to a subdirectory named core.

@jrha jrha added this to the 18.9 milestone Jan 25, 2018
@jrha jrha modified the milestones: 18.12, 19.2 Oct 30, 2018
@jrha jrha removed this from the 19.12 milestone Dec 20, 2019
@jrha
Copy link
Member Author

jrha commented Dec 20, 2019

Not likely to happen without actual time put aside to do it, which I can't promise right now.

@jouvin
Copy link
Contributor

jouvin commented Nov 8, 2024

I completely forgot about this issue... I'm personnally not in favor of merging these repos with different purposes... But restructuring the repositories not using a master branch is something we should do and that should not be too difficult.

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

No branches or pull requests

3 participants