Closed Bug 31917 Opened 25 years ago Closed 24 years ago

Update credits

Categories

(mozilla.org :: Miscellaneous, task, P3)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: BenB, Assigned: endico)

References

()

Details

(Whiteboard: [PDT-])

The page hasn't been updated for a long time (has it ever?). Please process all requests to news://news.mozilla.org/netscape.public.mozilla.patches> / <credits@mozilla.org>.
beta1 nomination
Keywords: beta1
Target Milestone: M15
this is Dawn's realm, reassigning to her
Assignee: mitchell → endico
Whiteboard: [PDT-]
yes. Would be great to get done. But will not hold beta for this. Putting on PDT- radar for beta1.
Maybe it will make it for beta1 *shipping* nevertheless, because fortunately, the <about:> page currently uses a direct link to <http://www.mozilla.org/credits/>, not the distributed <chrome://...credits.html>. Dawn, tell me, if I can help you. Most posts expired, so I don't even have the data.
arrgh, i was told that our newsgroup posts wouldn't expire. I can get access to the archive though. I've been putting off making additions because people want me to redo the list so it only reflects people that make contributions directly to the browser. The list currently lists contributors to other projects like perldap, bugzilla, grendel, etc.
Dawn, I agree, that such a reordering is necessary. Is there a bug on it? I'd extend it to categories of contributions: source code (maybe even separate feature and bugfixing), documentation and bug reporting/triaging. But does this mean, this bug won't be fixed before the reordering? I guess, the update won't need much more time than 1 hour.
This is not an M15 stability blocker... so I'm pushing it to M16 to facilitate a branching.
Target Milestone: M15 → M16
Dawn: ping? Adding nsbeta3 keyword. Gerv
Keywords: nsbeta3
the credits list is up to date
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
oops. that was too terse. Everyone who has asked to be added to the credits list has been added. Marking this bug fixed.
changing target milestone to null. it doesn't make sense to use m milestones for this component. I'm deleting them.
Target Milestone: M16 → ---
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.