If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Announcement
Collapse
No announcement yet.
Mozilla Shifting Firefox To A Four-Week Release Cycle
Whether you need it or not, right? If there's no reason to patch the stable in between significant releases, then don't go through the motions. As it is I look at changelogs for things and if I don't care, I don't do it. It takes me nearly two hours to build Firefox these days with PGO+LTO so there's got to be a good reason for me. Twice, because glibc is currently dissimilar in the two distros I use. I have enjoyed stabilizing on 69.0 for the past 15 days (i.e. no patch level releases in that time to second guess) :-)
Releases for the sake of release schedules are just spinning wheels.
Thank god, we were starting to lag behind Chrome's version numbers. Suck it, Google!
I hate marketing-oriented versioning so much. It undermines the reason behind versioning, which is letting people using software know what scope of changes to expect when updating. People should just stick to semver and call it a day.
I hate marketing-oriented versioning so much. It undermines the reason behind versioning, which is letting people using software know what scope of changes to expect when updating. People should just stick to semver and call it a day.
I think date-based is probably better than semvar here, and really for anything with a particular release schedule like the Kernel
Almost. For some reason their releases feel buggy at times.
One of them would basically crash after installing and rebooting the machine, leaving me with an unusable desktop. Do they really do QA during the set schedule?
Comment