Closed Bug 1165344 Opened 10 years ago Closed 10 years ago

The posted policy for performance regressions doesn't reflect reality

Categories

(www.mozilla.org :: Pages & Content, defect)

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: kohei)

References

()

Details

(Whiteboard: [kb=1798491] )

Attachments

(2 files)

as discussed on dev.platform a few months ago: https://groups.google.com/forum/#!searchin/mozilla.dev.platform/talos$20regression$20policy/mozilla.dev.platform/HkfaOTtAFVo/6L1E9GiOGGIJ we should update our policy. I am not very familiar with the wiki.m.o site, but let me submit a patch.
I am not sure who to ask for review, let me assume someone will guide me through this.
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
this patch was developed using: http://svn.mozilla.org/projects/mozilla.org/branches/staging/ ideally I would like to see it up there first, then land it on trunk: http://svn.mozilla.org/projects/mozilla.org/trunk/
Adding Gerv and Steven to review.
jbertsch: if you want someone to review something, set the review? flag, and give their email address. However, I don't think this particular policy is my responsibility... Gerv
:jbertsch- do you know the next steps here? We shouldn't have content as a policy online that doesn't match the current workflow. I have no idea who is required to review the policy- I referenced a discussion on mozilla.dev.platform surrounding this policy.
Flags: needinfo?(jbertsch)
I guess if it is based on discussion and agreement in the forum we can just push it live? Is there a module owner? Maybe Kohei or Silver Orange could push it live?
Flags: needinfo?(jbertsch)
as a note, this patch was for staging- I wasn't sure if I messed anything up; I assume it would apply to production as well.
this bug seems impossible to get traction on? is there a policy for updating this wiki? Anything else I could do?
This policy (as in, the idea of closing the tree for performance regressions) was originally a bit controversial back in 2002, which is why Mitchell is listed as the contact person and owner. But it has barely changed since then, according to the history. I think that today, the sheriffs either /de facto/ own the policy or know who does. I suggest you ask them, and whoever they say calls the tune that they dance to is the policy owner. That person can r= changes to the document, or (simpler) just ask for it to be removed. I suspect information about when and why we close the tree doesn't live on mozilla.org these days. Gerv
we don't close trees for perf regressions; as it stands I am the only perf sheriff and want to get the policy we currently used on live documentation.
OK. If you are the bearer of the currently-agreed policy, then I think you should just go ahead and make the change. r=gerv. Gerv
Attachment #8606299 - Flags: review+
Depends on: 1182527
Sorry this one has taken so long. Let's get it live. Kohei: Do you have time to help? Thanks!
Flags: needinfo?(kohei.yoshino)
Sure.
Flags: needinfo?(kohei.yoshino)
Assignee: jmaher → kohei.yoshino
Whiteboard: [kb=1798491]
Version: Development/Staging → Production
Oh the page is still on the SVN repo. I'm gonna move it to Bedrock then and update the content as suggested.
Depends on: 1183936
:kohei, I know how svn commit access- not sure what bedrock is, is this something I should let you handle?
The current mozilla.org is a mixture of legacy PHP-based SVN repo and new Python-based Git repo. The new one is called Bedrock and we have to migrate all the content from the legacy repo to Bedrock within several months. This page is on Bedrock: https://www.mozilla.org/en-US/about/governance/policies/ https://github.com/mozilla/bedrock/blob/master/bedrock/mozorg/templates/mozorg/about/governance/policies/policies.html This page is still on the legacy repo: https://www.mozilla.org/hacking/regression-policy.html http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/hacking/regression-policy.html Once we migrate the content, changes can be made with just a single GitHub pull request. That should be easier than SVN-based workflow :) I'm happy to help moving the remaining 4 files on the /hacking/ directory to Bedrock, along with the changes proposed here. # I have SVN access but only for l10n-related directories.
Hi All- Mike is going to file a blocker bug to migrate all the remaing /hacking files on SVN to Bedrock. Thanks again for your patience, Jen
Flags: needinfo?(malexis)
Depends on: 1185070
Attached file pull request
Filed Bug 1185070 for migration and sent a PR including this change.
Flags: needinfo?(malexis)
Blocks: 1186102
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/6f7408a5e1b22d5d6b2cecad6914e3986b1badc3 Fix Bug 1165344 - The posted policy for performance regressions doesn't reflect reality https://github.com/mozilla/bedrock/commit/183915232095a35077d9862ddd19bae4b984d7a8 Merge pull request #3136 from kyoshino/bug-1165344-regression-policy Fix Bug 1165344 - The posted policy for performance regressions doesn't reflect reality
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
the old policy is still here: https://www.allizom.org/hacking/regression-policy.html and here: https://www.mozilla.org/hacking/regression-policy.html I don't understand what Bedrock is, but do let me know what I can do to help out or resolve this myself.
Status: RESOLVED → REOPENED
Flags: needinfo?(kohei.yoshino)
Resolution: FIXED → ---
The new page is not yet pushed to production by the team, but can be previewed on the staging site: https://www-dev.allizom.org/hacking/regression-policy.html The production push may happen today or tomorrow, so just hang on and be patient :)
Flags: needinfo?(kohei.yoshino)
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: