On 04/12/2017 Jim Jagielski wrote:
Say we release 4.1.5 and that build number is 9799. We then
release start doing betas and RCs for 4.2.0 and use 9800,
9801 and 9802. We then find out we need to release a 4.1.6.
Is that BUILD number now 9803?
This is an interesting scenario. The way it has worked so far are:
1. Only one development line is active.
2. For any stable release, the build number is higher than the previous
release.
3. The update system, based on your version (not build number), tells
you the build number and the URL of the latest available version. I am
fairly sure -but can't double-check now- that if the reported build
number is higher than the build number of the version you are currently
using, the update is triggered (so you see the "Updates available"
notification).
Now, can it work if we break assumption 1?
We are not interested in update URLs for Beta releases.
Having to release, say, a 4.1.6 when we already have 4.2.0-RC1 out is
really an edge case. Still, if this happens, I would:
- Just update the build number as you suggest
- Pay attention to the update feeds to avoid that feeds for 4.2.0 report
the existence of 4.1.6.
This would need a lot of care and future maintenance though, so my best
advice is: just keep supporting one development line and once we release
4.2.0-RC1 don't look back. At that point, don't release any 4.1.x
releases any longer.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
