Issues
Consolidate some of our git repos
Description
Details
Details
Assignee
Reporter
Sean FlaniganLabels
Priority
unspecifiedEpic Name
More fields
Time tracking
More fields
Time trackingActivity
Former user20 April 2018 at 00:24
We are closing all the old issues to have more clarity in our backlog for Zanata project. Feel free to re-open or leave a comment if you require our attention on your Jira.
Former user10 August 2017 at 05:05
This epic seems done.
zanata-ui - removed
zanata-assets - removed
Everything else are part of zanata-platform now.
Former user8 June 2017 at 05:50
zanata-ui - YES
zanata-assets - No for quite some time,or until all css in from frontend module.
Sean Flanigan8 June 2017 at 05:26
In terms of closing off this epic, I think we need to deprecate the github repos for zanata-ui and zanata-assets, as we did for zanata-spa. Are we able to do that yet?
Former user31 October 2016 at 00:11
As I mentioned earlier, we are now trying to phase out zanata-assets. The idea now is to have any new css/styling in Zanata server.
Zanata-assets will remain as it is until everything is replaced in either zanata-frontend/new css in zanata-server.
We have more git repos in Zanata than we need, considering we don't use microservices.
This makes dependency management more difficult (affecting continuous integration) and also increases the cost of making releases.
It only makes sense to have separate git repos when the release lifecycle needs to be separate. If two things are always meant to be used together, tested together and released at the same time, they should live in a single git repo, so that they can be changed atomically, tagged together and generally managed together.
The exact form of the restructuring is TBD. I'll follow up with some possibilities as comments.