![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
Upstream flag
After discussion with ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
tupshin and henrylyne this past week, we've figured out that the best way for us to get patches committed upstream to LJ is to create a new flag in our Bugzilla, which I've done: now, when you upload a patch, you can also set the "Upstream" flag, which will call things to Henry's attention. He's agreed to be our liaison.
This flag should be used when you're uploading a patch that also patches a bug that appears on LJ. It shouldn't be used for new features or for things that patch bugs that only appear on DW.
If you've got things that have already been resolved/fixed that you think should be pulled upstream, comment here and I'll assemble a list for Henry and Tupshin.
tupshin and henrylyne this past week, we've figured out that the best way for us to get patches committed upstream to LJ is to create a new flag in our Bugzilla, which I've done: now, when you upload a patch, you can also set the "Upstream" flag, which will call things to Henry's attention. He's agreed to be our liaison. This flag should be used when you're uploading a patch that also patches a bug that appears on LJ. It shouldn't be used for new features or for things that patch bugs that only appear on DW.
If you've got things that have already been resolved/fixed that you think should be pulled upstream, comment here and I'll assemble a list for Henry and Tupshin.
no subject
And as mentioned elsewhere, please please please at least do me the courtsey of holding off on making changes to the development process until I get back. Discuss all you like (CC me!!) but stop pulling triggers... kinda frustrating.