Production push doc update

mozilla-releng / beetmoverscript

An implementation of scriptworker for moving TC artifacts to all release-related buckets.

1 stars 19 forks source link

Production push doc update #158

Closed nthomas-mozilla closed 6 years ago

nthomas-mozilla commented 6 years ago

process changes for puppet move to github
move of puppet repo into mozilla-releng org
add note to wait for masters to sync requirements.txt change

tomprince commented 6 years ago

This should have a newsfragement.

coveralls commented 6 years ago

Pull Request Test Coverage Report for Build 556

0 of 0 changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.913%

Totals
Change from base Build 554:	0.0%
Covered Lines:	455
Relevant Lines:	460

💛 - Coveralls

MihaiTabara commented 6 years ago

Come to think about it after chatting with @nthomas-mozilla - this raises the question, some of the PRs are not quliafiying for a bug number, hence am not sure they should really have a newsfragment. I mean, any code change that can affect functionality should have a bug number I suppose, but for doc fixing or tooling (e.g. tox, coveralls, etc) I don't think it's worth filing a bug.

@tomprince what do you think?

MihaiTabara commented 6 years ago

Let's make a consensus: any changes that don't have a tracking bug number in Bugzilla can ignore the newsfragment I suppose. In this category we can definitely shove the update of the info files (README, requirements, etc). We can always come back and change this.

MihaiTabara commented 6 years ago

Pushing this to be grabbed in the upcoming 7.5.0 roll-out