You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code is deployed to multiple external package repositories and new ones are requested from time to time. This is a significant amount of work to manage and I'm interested in people's thoughts of how we can do this.
Currently many of the entries in package repositories are owned by people who did a deployment once, haven't necessarily kept it up to date, and who I don't know personally (so I can't poke them).
I can see either this all becoming my problem (but I have limited time), or we keep it distributed (but then need a way to stay coordinated).
Ideas?
The text was updated successfully, but these errors were encountered:
Code is deployed to multiple external package repositories and new ones are requested from time to time. This is a significant amount of work to manage and I'm interested in people's thoughts of how we can do this.
Currently many of the entries in package repositories are owned by people who did a deployment once, haven't necessarily kept it up to date, and who I don't know personally (so I can't poke them).
I can see either this all becoming my problem (but I have limited time), or we keep it distributed (but then need a way to stay coordinated).
Ideas?
The text was updated successfully, but these errors were encountered: