> * striking "milestone or" at the beginning of
> http://www.mozilla.org/bugs/
Working on it.
> * Hiding the "advanced" bug reporting form the Bugzilla front page and
> directing users to Bugzilla Helper
Not under my control.
> * sniffing the Gecko date token in the UA string of the build used to
> access Bugzilla Helper and notifying the user if the build is
> considered old
But often people use other browsers to submit bug reports, or even an
older version of Mozilla if their current one is too unstable. Much more
sensible would be to:
> * requiring a build id in Bugzilla Helper bug reports and checking the id
> for recentness
What time limit? I suggest three weeks. Code implemented - try it out :-)
> Currently, www.mozilla.org indeed encourages the use of milestones and
> makes nightly build appear scary. Rather than asking potential users
> (who might also be potential contributors!) take a hike, the importance
> of milestones could be downplayed and links could be made to good
> nightlies.
I think this is very important. Nightlies are now pretty good, and making
a milestone takes a lot of people's (especially Asa's) time. As more and
more stuff goes in, and things become more modular, you can't force each
group to "release" at the same time.
Gerv
