Closed
Bug 809325
Opened 12 years ago
Closed 12 years ago
change version number to reflect not production-ready state
Categories
(Firefox OS Graveyard :: Gaia, defect, P1)
Tracking
(blocking-basecamp:+, firefox19 fixed, b2g18 fixed)
People
(Reporter: isandu, Assigned: fabrice)
Details
(Keywords: unagi)
Attachments
(2 files)
685 bytes,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
43.36 KB,
image/png
|
Details |
We need to change the version number that is shown in Settings to something less than 1 to avoid impression to press that this is early preview of v1.
Comment 1•12 years ago
|
||
Evelyn said it's in Gecko at <mc-root>/gecko/b2g/confvars.sh Line#13.
Dave/Chris, do you want all traces of 1.0 removed, or something like "1.0prelease" ok?
Updated•12 years ago
|
blocking-basecamp: --- → ?
Comment 2•12 years ago
|
||
I'm fine with "1.0-prelease" or "developer build 1.0". Any issue with either one of these?
Comment 3•12 years ago
|
||
just to prevent any accidental confusion, why not "developer build 0.1". Basically..don't have a "1.0" or "V1, which if someone looks too quickly looks like a full release.
Gaia Triage: steering committe decision, +ing (though I would disagree personally, but moving on)
blocking-basecamp: ? → +
Comment 5•12 years ago
|
||
(In reply to David Slater from comment #3)
> just to prevent any accidental confusion, why not "developer build 0.1".
> Basically..don't have a "1.0" or "V1, which if someone looks too quickly
> looks like a full release.
I'm fine with this, but I find it odd to go from 0.1 directly to a version 1.0 release. I'll defer to Alex and others in release management on the best way to handle the numbering.
Comment 6•12 years ago
|
||
I should say, all I'm really concerned with is clearly communicating "not a final product; this is an early preview" message. How we do that I have little opinion on. So call it a "0.1" or a "Developer Preview" or just nothing at all, however you want to do it.
Comment 7•12 years ago
|
||
The version is the target version we're developing for (as with Firefox versions, which just include a1 or a2 next to the version to denote Nightly/Aurora)..
Let's just append "-prerelease" to the version to make it clear (as suggested in Comments 1/2). David - can you help reassign?
Assignee: nobody → dscravaglieri
Priority: -- → P1
Assignee | ||
Comment 8•12 years ago
|
||
Changes the version number to 1.0.0-prelerease
Assignee: dscravaglieri → fabrice
Attachment #679890 -
Flags: review?(21)
Assignee | ||
Comment 9•12 years ago
|
||
Attachment #679890 -
Flags: review?(21) → review+
Assignee | ||
Comment 10•12 years ago
|
||
Comment 11•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Keywords: checkin-needed
Comment 12•12 years ago
|
||
status-b2g18:
--- → fixed
status-firefox19:
--- → fixed
Keywords: checkin-needed
Target Milestone: --- → B2G C1 (to 19nov)
Comment 13•12 years ago
|
||
Verified on Unagi device Build ID: 20130112070202 v 1.0.0-Prerelease
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•