News for hackers. Stuff that matters.

A comment on Firefox moving to 4 week releases. Parent comment

Re:Firefox moving to 4 week releases by lenkite on Tuesday September 17, 2019 @05:25PM (#21000244)
Well, I don't get an idea if my extension would break changing from version 2019-10 -> 2019-11 without reading the release notes.

I would know it there is a big chance of breakage if I moved from 76.0.0 -> v77.0.0 and I am reasonably certain it won't break if I moved from 76.0.0 -> 76.0.1

[ Parent | on HN ]
Re:Firefox moving to 4 week releases by diegoperini on Wednesday September 18, 2019 @12:40PM (#21007127)
But if a website breaks, you can get more idea about why it happened by comparing your current browser's calendar version to the latest update. For example, you will know you are behind x years of updates. With semantic versioning, you don't know how old you have not been updating your installation.

Since there are more websites than extensions, the utilitarian approach would be to choose 2019-10 over 76.0.0.

[ Parent | on HN ]
Re:Firefox moving to 4 week releases by lenkite on Thursday September 19, 2019 @08:41AM (#21015591)
One approach is proactive and the other reactive. Unless, one checks the release notes every 4 weeks... I would argue the utilitarian approach is exactly the other way. Verify and test if there is an API break with a major version change. Whether the browser is 2 years or 10 years old shouldn't make a difference.
[ Parent | on HN ]