Recommended Posts

No. Unless a showstopper forces a respin (which is extremely unlikely at this point), the June 24 build (RC3) is the Final build. As I've said before in another thread, Mozilla does true candidates, which is why none of the RCs contain "RC" in the version info.

The tree has long been closed, and all checkins since June 24 have been things that are not a part of the build. The nightlies are automatically spun every day, regardless of whether there has been any changes to the code, and they will continue to be automatically generated every day after 3.5 is released (at which point, they will be 3.5.1pre).

Edited by code.kliu.org
As I've said before in another thread, Mozilla does true candidates, which is why none of the RCs contain "RC" in the version info.
Which is interesting in the world of software development. I was ridiculed on another thread for pointing out that Mozilla's release candidates are truly candidates for release, unlike other software, like say Windows, where release candidates have absolutely zero chance of being final.
Which is interesting in the world of software development. I was ridiculed on another thread for pointing out that Mozilla's release candidates are truly candidates for release, unlike other software, like say Windows, where release candidates have absolutely zero chance of being final.

It's a bit like comparing apples and oranges though isn't it? Although I see your point.

Which is interesting in the world of software development. I was ridiculed on another thread for pointing out that Mozilla's release candidates are truly candidates for release, unlike other software, like say Windows, where release candidates have absolutely zero chance of being final.

You're right. With Windows, they generally pre-announce how many release candidates there will be. That, by the very definition of the term 'release candidate', means that they are not release candidates at all. How can RC1 be called a Candidate for Release if you've already announced there will be an RC2 long before RC1 came out. It's stupid really.

Microsoft should continue with the Beta tag until they are at the quality bar where the product could be released. At that point you compile a build and called it RC1. Assuming no show stoppers are found by the public in RC1, you use that very same build and rename it to Final. If bugs are found, you fix them and release a second RC. It's a no-brainer really.

Mozilla seems to do it this way which is a welcome change from Microsoft's backwards way of doing it.

Thanks, but I'll wait for the final version. :)

Which, from the looks of it, will almost certainly be bit-for-bit identical to RC3. ;)

For Mozilla, the process can vary. As people would recall, the Firefox 1.0 RCs were really glorified betas and were not true candidates. The current project drivers very much like the idea of a true RC (in part because it makes it easier for QA to sign off on things: if you spin a new build after an RC, you need to test that build anyway to make sure something weird didn't happen during build or packaging, etc.).

As for Microsoft, they have intentionally "grade-inflated", and they have a very good reason to do so. Raymond Chen wrote an article explaining this (sorry, don't have the link handy) that basically boiled down to this: Microsoft had a problem where people didn't pay attention to the betas, and there was one incident, back when Microsoft's RCs were true candidates that they got an important piece of feedback only after the RC came out, at which point it was too late in the process to make those sorts of changes without incurring a lot of extra cost. So they had to grade-inflate, and what used to be late betas are now RCs, and what used to be RCs are now escrow builds. The idea is that more people are more willing to test and give feedback if it says "RC" than if it says "beta". Though I think that with the current overuse of the "beta" label (e.g., Google's notorious perpetual betas), the need for this grade inflation has decreased somewhat in recent years.

You're right. With Windows, they generally pre-announce how many release candidates there will be. That, by the very definition of the term 'release candidate', means that they are not release candidates at all. How can RC1 be called a Candidate for Release if you've already announced there will be an RC2 long before RC1 came out. It's stupid really.

Microsoft should continue with the Beta tag until they are at the quality bar where the product could be released. At that point you compile a build and called it RC1. Assuming no show stoppers are found by the public in RC1, you use that very same build and rename it to Final. If bugs are found, you fix them and release a second RC. It's a no-brainer really.

Mozilla seems to do it this way which is a welcome change from Microsoft's backwards way of doing it.

I agree. I never understood Microsoft's way of doing this. It really doesn't make any sense at all.

Perhaps. It's only a day away, anyway. I think I can hold out with version 3.0.11 until the version 3.5 is released. :p

Yeah, I really can't wait. I still think that the Tab Previews they chose would have been better served if they used Showcase Tab as a base instead of the add in they chose, but that's my only gripe, and is admittedly miner. Showcase though is an AMAZING add in though.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • As I've been usually saying lately - we all can thank "AI" for this.
    • Friday Windows 11 preview builds are here. Insiders in the Experimental (formerly Dev) and Beta Channel can download builds 26300.8697 and 26220.8690. My Windows11 device on the Preview Channel just got 26220.8728. My guess is this build is a nightly update from 26220.8690.
    • Traffic has a surprisingly unexpected impact on your surroundings by Sayan Sen Image by Radik 2707 via Pexels A collaborative study by researchers from several Israeli institutions found that everyday pollution from traffic and industrial activity measurably changed the atmospheric electric field over the Tel Aviv metropolitan area, providing new evidence of how human activity can influence the lower atmosphere. The research was led by Dr. Roy Yaniv of the Hebrew University of Jerusalem and the Gertner Institute at Sheba Medical Center, Dr. Assaf Hochman of the Fredy & Nadine Herrmann Institute of Earth Sciences at the Hebrew University, and Prof. Yoav Yair of Reichman University. The study also involved Itay Froomer, a student from Hadera High School and the Israeli Museum of Medicine and Science (Technoda), who carried out the work as part of the Ministry of Education's 5-unit physics research track. The researchers focused on the atmospheric electric field under fair-weather conditions. Even in the absence of storms, a weak electric field naturally exists between Earth's surface and the atmosphere. One of the main ways scientists measure this field is through the Potential Gradient (PG), which is the inverse of the vertical component of the electric field. PG is a key part of the global electric circuit, a planet-wide system of electrical currents maintained by thunderstorms and electrified clouds around the world. Scientists have long known that the atmospheric electric field can be influenced by factors ranging from large-scale atmospheric processes to local weather conditions such as dust, fog and clouds. Human-made pollution is also known to play a role, but understanding exactly how urban emissions affect the electric field close to the ground has remained an area of ongoing research. To investigate this relationship, the team analyzed measurements from a newly installed electric field mill, an instrument used to continuously monitor the strength of the atmospheric electric field. The instrument was installed at the Center for Technological Education (Roter House) in Holon and became operational in August 2024. It was funded by Israel's Ministry of Education and the Holon municipality. The electric field mill forms part of a broader monitoring network that includes nearby meteorological stations and air-quality monitoring sites. This allowed researchers to compare electric field measurements with detailed weather data and pollution records to better understand what was driving changes in the Potential Gradient. The study focused on two major urban pollutants: fine particulate matter (PM2.5) and nitrogen oxides (NOx), both commonly produced by vehicle traffic and industrial activity. PM2.5 refers to microscopic airborne particles small enough to remain suspended in the atmosphere for extended periods, while NOx is a group of gases released during fuel combustion. Researchers examined daily, weekly and seasonal patterns in the atmospheric electric field and compared them with changes in pollutant concentrations. Their analysis revealed a clear relationship between NOx levels and changes in the Potential Gradient, particularly during morning and evening rush hours when traffic emissions were at their highest. “What we observe is a direct physical link between emission peaks and electrical variability,” explained Dr. Roy Yaniv. “NOx reduces atmospheric conductivity very quickly, so the electric field responds almost instantaneously during traffic rush hours.” Atmospheric conductivity describes how easily electrical charges move through the air. According to the researchers, nitrogen oxides rapidly alter this conductivity, causing a near-immediate response in the electric field. PM2.5, however, was associated with a delayed response. The researchers attributed this difference to the particles' longer atmospheric residence time, meaning they remain in the atmosphere for longer periods, as well as their different microphysical interactions with surrounding air and atmospheric components. The study also identified a pronounced "weekend effect." In Israel, traffic volumes and some industrial activity decline significantly on Fridays and Saturdays. During these periods, concentrations of both NOx and PM2.5 dropped, and corresponding changes were observed in the atmospheric electric field. “The weekend signal demonstrates just how sensitive the electric field is to changes in human activity,” the researchers noted. “When emissions decline, the electrical environment adjusts at once, providing a high-resolution indicator of urban atmospheric conditions.” The findings showed that pollution levels can influence not only the chemical composition of the atmosphere but also its electrical properties. Researchers said the results strengthened the case for using atmospheric electricity as an additional tool for environmental monitoring, particularly in densely populated urban areas where anthropogenic, or human-caused, influences are most pronounced. The study also pointed to potential public health applications. By combining air-quality measurements with observations of atmospheric electricity, researchers said they could gain a more complete picture of how urban atmospheric conditions change over time. “Integrating air-quality data with electric-field measurements gives us a clearer picture of how the lower atmosphere evolves moment by moment,” the researchers added. “It’s a framework that can support both scientific insight and practical environmental decision-making.” Beyond the scientific findings, the project highlighted a collaboration between universities, public institutions and secondary education. Researchers said the work demonstrated how students could take part in real-world environmental research while contributing to studies of air quality, atmospheric processes and their potential effects on society. Source: Hebrew University, ScienceDirect This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
    • We aren't even at the all-star game and Microsoft is talking about an update that will most likely be released during the World Series if not after. A lot can happen in the world between now and the 2026 World Series, including the 2026 FIFA Cup. Tell me about it again after the FIFA Cup is concluded. That should allow plenty of time to prepare for it.
    • Great, tell me when I have a "Bad Pool Caller" elsewhere not in Windoze.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      540
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      72
  • Tell a friend

    Love Neowin? Tell a friend!