Skip to content
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.

Document or script patch creation #2319

Closed
ianb opened this issue Mar 8, 2017 · 4 comments
Closed

Document or script patch creation #2319

ianb opened this issue Mar 8, 2017 · 4 comments
Assignees

Comments

@ianb
Copy link
Contributor

ianb commented Mar 8, 2017

After copying files into the Firefox tree (#2318) we need to produce a patch and put the patch in Bugzilla. This could be documented or scripted, or some combination of the two.

@ianb ianb added the releng label Mar 8, 2017
@ianb ianb modified the milestone: Page Shot in 54 Mar 8, 2017
@Standard8 Standard8 self-assigned this Mar 8, 2017
@Standard8
Copy link
Contributor

I'd suggest scripted. I had something for Loop that could do this, so I'll see if I can pull it out.

@Standard8
Copy link
Contributor

We've now got a scripted way of exporting to mozilla-central (#2407).

I don't have requirements for creating bugs, but it should be pretty easy to adapt https://github.com/mozilla/loop/blob/master/bin/create_release.py to file bugs automatically & post patches.

The one thing that is slightly different is that the export_mc.py script created in #2407 already does the creating of a branch & commit from which to push the changes. Hence the first part of releaseMozillaCentral just needs to make a call to that script.

@Standard8 Standard8 removed their assignment Apr 21, 2017
@jaredhirsch
Copy link
Member

Hmm. Looking at the create_release.py script, I think it would be good to create a bugzilla component for firefox release requests and security bugs.

@johngruen
Copy link
Contributor

Closing for now since current process seems to be working

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants