[FOLIO-541] split backend module projects into it's own jira/git project Created: 04/Apr/17 Updated: 12/Nov/18 Resolved: 09/May/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Umbrella | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint12, sprint13 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 day, 2 hours, 10 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||
| Description |
|
This includes: RMB Decide on the details. |
| Comments |
| Comment by Jakub Skoczen [ 04/Apr/17 ] |
|
Guys, I am curious to hear your opinions but I feel the most seamless way forward is to leave the Git structure intact and introduce Jira projects that map to those projects. For multi-module project like mod-auth, keep sub-module versioning alingned and use that as a "fixVersion"/version management in Jira. |
| Comment by Marc Johnson [ 04/Apr/17 ] |
|
I think going forward it would be good to establish a convention for the repositories, and I think that would likely involve splitting mod-metadata into mod-inventory and mod-inventory storage. I agree that this does not need to happen to achieve the goal of this change (as long as we are happy with a unified version for both modules). If we keep the git repositories as they currently are, then the metadata project can be used for both inventory and inventory storage, and they need to have a unified version. We'd only need two new JIRA projects for circulation and loan-storage (that could be renamed to circulation-storage). Hugs, Marc |
| Comment by Jakub Skoczen [ 05/Apr/17 ] |
|
Kurt Nordstrom Marc Johnson let's establish what Git projects need splitting, this is a prerequisite for knowing what Jira projects must be created (which I will ask John Malconian to do). |
| Comment by Marc Johnson [ 05/Apr/17 ] |
|
I don't know enough to properly comment on the authentication/authorisation modules. I think Jakub Skoczen comment in the call about Okapi components is a good guideline, do we envisage that these modules will almost always/very often be used together? For the business logic / storage modules, I think consistency is the key. At the moment the users storage and business logic modules are separate, as are circulation and loan (maybe to be renamed circulation) storage. It is only the metadata modules which aren't at present (which I think is partly due to how we thought we might answer the question of use together and partly historical), therefore I think splitting them would make the repository organisation more consistent. Hugs, Marc |
| Comment by Jakub Skoczen [ 10/Apr/17 ] |
|
Mike Taylor will create a parallel issue for the front-end components and link it here. |
| Comment by Jakub Skoczen [ 10/Apr/17 ] |
|
Kurt Nordstrom what about mod-users and mod-auth? My thinking was that we would go ahead and "lock" versions of all mod-auth sub modules and create two new project in Jira: MODAUTH and MODUSERS. What say you? |
| Comment by Mike Taylor [ 10/Apr/17 ] |
|
The parallel issue for the front-end is
|
| Comment by Jakub Skoczen [ 12/Apr/17 ] |
|
Kurt Nordstrom I have created the following projects in Jira: mod-users, mod-authtoken, mod-perms, mod-login (I have assume those are the names you will use in GitHub). You are the "lead" for all of them, which means you can maintain versions and set "fixVersion" field for issues. Please start moving issues over from DMOD/FOLIO to specific projects and set that field, if you lack priviliges please ask John Malconian for help. Marc Johnson I have created the missing "Circulation Storage" project, please follow the same steps as in Kurt's case. shale99 I have created a new project called RMB, you are the lead. Please follow the steps from Kurt's, description above. Thanks guys. |
| Comment by Jakub Skoczen [ 12/Apr/17 ] |
|
John Malconian I am assinging to you in case there are any Jira config problems. Feel free to close when guys have succesfully moved stuff over. |
| Comment by John Malconian [ 25/Apr/17 ] |
|
Marc Johnson - I renamed the circulation and ciculation-storage projects in Jira to 'mod-circulation' and 'mod-circulation-storage' just for consistency. I also created projects for mod-inventory and mod-inventory-storage in anticipation of those as separate git projects. You are the Project Manager/Lead for all four projects. Kurt Nordstrom - I renamed the mod-perms Jira project to 'mod-permissions'. Please ensure the new git project for this module is called 'mod-permissions'. I also gave you Project Manager permissions on mod-users, mod-permissions, mod-login, and mod-authtoken. shale99 - I gave you Project Manager permissions on 'RAML Module Builder' project. Let me know if I should create separate Jira projects for other RAML-based modules like mod-configuration or mod-acquisitions. If any of you need assistance moving existing Jira issues to these new projects, let me know. |
| Comment by Heikki Levanto [ 27/Apr/17 ] |
|
Github has a nice article on how to do this: https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/ |
| Comment by Mike Taylor [ 27/Apr/17 ] |
|
That really is nice, though git filter-branch always make me feel queasy. What's needed now is a complementary recipe for how to permanently erase the sliced out branch from the history of the original project. (Yes, I know you often don't want to do that; but sometimes you do.) |
| Comment by Marc Johnson [ 27/Apr/17 ] |
|
Thanks, that article looks like it will help me when I make the changes to split the metadata modules into separate repositories. Hugs |
| Comment by John Malconian [ 27/Apr/17 ] |
|
All the jenkins jobs for the auth modules have been reconfigured and tested. |