Bug #5427
Android app version is stuck at 38.0
| Status: | Closed | Start date: | 06/27/2015 | |
|---|---|---|---|---|
| Priority: | High | Due date: | 07/07/2015 | |
| Assignee: | amoghbl1 | % Done: | 0% | |
| Category: | - | |||
| Target version: | Orfox Alpha 2 | |||
| Component: |
Description
We need some sort of versioning scheme for Orfox... do we use 38, or reset it to 1.0?
History
#1 Updated by amoghbl1 over 2 years ago
With the regular mozilla convention, 38.0 is good, in order to know what esr it was built on.
I understand the problem that it's causing though, I think that Orfox itself should be called 0.0.x, followed by esr-38.0 .
With the new iteration x would be for the smallest iterations we release every time I trigger a jenkins build? And 0.1, 0.2 so on would be things we release into beta? And well, version 1.0 would be for the RC?
This is some custom versioning that I've just come up with, I don't know to what extent this would be good, need more view points on this.
#2 Updated by n8fr8 over 2 years ago
- Target version set to Orfox Alpha 2
#3 Updated by n8fr8 over 2 years ago
- Due date set to 07/07/2015
- Priority changed from Normal to High
amoghbl1 wrote:
With the regular mozilla convention, 38.0 is good, in order to know what esr it was built on.
Sure, that is just the version that was tagged in the release we built upon. We need to move the version forward for users to understand what is happening.
I understand the problem that it's causing though, I think that Orfox itself should be called 0.0.x, followed by esr-38.0 .
0.0.1-esr-38.0 ? How does Tor Browser handle this?
With the new iteration x would be for the smallest iterations we release every time I trigger a jenkins build? And 0.1, 0.2 so on would be things we release into beta? And well, version 1.0 would be for the RC?
Perhaps we should keep 38.0-esr-Orfox-0.0.1 or something, since we already have 38.0 as the leading value now.
This is some custom versioning that I've just come up with, I don't know to what >extent this would be good, need more view points on this.
We can run it by people briefly, but let's get it done in the next few days.
#4 Updated by amoghbl1 over 2 years ago
- Status changed from New to Resolved
#5 Updated by n8fr8 over 2 years ago
- Status changed from Resolved to Closed