Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.planning
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Firefox 3.6 Release Candidate builds started
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mike Beltzner  
View profile  
 More options Jan 5 2010, 10:32 pm
Newsgroups: mozilla.dev.planning
From: Mike Beltzner <beltz...@mozilla.com>
Date: Tue, 5 Jan 2010 22:32:53 -0500
Local: Tues, Jan 5 2010 10:32 pm
Subject: Firefox 3.6 Release Candidate builds started
Print | Individual message | Show original | Report this message | Find messages by this author
Hey everyone,

Just wanted to follow up to let everyone know that after months of development, we've started builds for Firefox 3.6 Release Candidate builds. We're pretty excited.

This is the point where people start asking me about "oh, but what about this patch that didn't make it in?" That's a fine thing to ask, and soon enough I'll be filing bugs to get new flags created for the inevitable Firefox 3.6.1. In the meantime, if there's a patch you want considered for the dreaded status of "RC ridealong," please do so by sending me or another driver private email. Be sure to plead your case clearly: why do we need it? how do you know that it won't cause further performance or functional regressions? how long has it been baking on trunk with tests?

cheers,
mike


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google