Hi team,
Happy New Year 2020.
In a spirit to promote a clear ownership, code isolation, and responsibility, and also for CI/CD pipeline enabled in future, we would like to inform you that we have migrated fprint from flight repo to new fprint repo, and plan to use it starting next week. So if you are currently writing code for fprint in flight repo, here is our migration plan for you (feel free to give any feedback).
fprint/release/2020-01-06 (this week release branch). That is 851b31bc541a008f1baf502e2f5def141b110dce. If your code is included there, you do not need to notify us since it will be automatically migrated.
851b31bc541a008f1baf502e2f5def141b110dce, the author should notify us so we can help to move the code.
x at Wednesday 6pm JKT time, and start migrating the delta (from 851b31bc541a008f1baf502e2f5def141b110dce to x) from flight repo to new fprint repo.
FAQ:
Q: Where is the repository?
A: Here it is: https://github.com/traveloka/fpr-integrator-backend
Q: We have airline-common-fetch module in flight repo, that is widely used by supply , TDM, and may be other team. As member of TDM team, should we write our changes in the new fprint repo when we want to enhance our reschedule API functionality?
A: No, you shouldn't. We leave airline-common-fetch in flight repo so you can adjust your code there. However, we will no longer maintain it since we have a copy of it in fprint repo.
Q: What if I need to fix something in fprint (especially if I am oncall)?
A: Just like other repo maintained by other team, you (as developer) are allowed to make changes in that repo and submit PR for code review. However, merging and deployment to production will be taken care by @flight-supply-backend /@flight-supply-oncall
Last but not least, really thanks to @Musa, @Vincent , @arpit.agrawal, @Apriyanto.Arkiang (Adi), @putu.pradnyana, and special credit to @alok.singh for helping the migration process. If you have any queries, please do not hesitate to let us know