On 06/28/2017 02:57 AM, Pierre-Yves Chibon wrote: > I did not realize this before, but this will impact the decommissioning of > pkgdb. > The idea was to deploy pagure on dist-git on July 5th and deprecate pkgdb on > July 10th. > > So could/should we postpone this to say, deploy pagure on dist-git on the 10th? > and deprecate pkgdb on the 17th? > (The pagure part worries me less since it's a new service which should have > minimal impact on the existing one). > The issue is then, what do we do is release slips? > > Pierre > > > PS: on a personal note, I'm not sure how much I'll be around on the 5th > afternoon, 6th and 7th, so postponing to the 10th is actually appealing to me. Well, the folks with the short timeline/constraints are the factory 2.0 folks, so lets see what they say here. ;) I'm fine with doing it later, but this may impact more milestones they have. I agree the pagure part might be less impactfull since it should hopefully not affect f26 efforts. The pkgdb drop could affect f26 (say a blocker couldn't be built or the like), so it might be better to do that when f26 is already go. kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
