Beta and release versions should identify as the same version.

Ability to identify which channel a user is on from the build.

Amount of changes required to existing tools and systems.

Ease of version comparisons between channels and releases.

No 'pre' as there are known issues with sites sniffing.

The following considerations are reflected in the versioning scheme: Unless major issues are discovered with the scheme, this is howīuilds in the assorted repositories will identify themselves: The repo is just for reference andĪvailable for cloning if a rapid response release

Fixes for newly-found issues which would prevent.

Were deemed ready but testing determined they in fact

Preffing off and backing out fixes/features which.

Landing spot fixes to get the product in a shipping.

Preffing off and backing out fixes/features.

On this channel it means a new version of Firefox has been Users willing to help test early versions of Firefoxĭuring the last round of stability refinement. Not branded as Firefox, uses 'Firefox Developer Edition' branding There are higher stability expectations versus Risk instability to see and test the latest fixes. Not branded as Firefox, uses 'Nightly' branding Risk massive instability to see and test the Mozilla developers and power users willing to Scope for this proposal and will be discussed soon. Project pages, feature tracking, and bug management are out of This document mainly covers the release process. The downstream repositories are part of the Project repositories and mozilla-central are part of the The repositories can generally be grouped into two overall Repository for code to generate officially released Validation of the mozilla-aurora stabilization

Stabilize work done on mozilla-central for releaseįix any issues that come up during the beta

This document discusses specifics related to Mozilla's Firefox development model.ĭiscussion should take place on dev-planning and changes Mozilla Firefox: Development Specifics Overview

Mozilla firefox developers