Short bio: Computer Scientist, FOSS supporter (read more)
Tux Machines (TM)-specific
Recently Mozilla implemented a rapid release process, where we release a version of Firefox every 6 weeks. This has involved changing a number of our processes. It’s also raised some new issues. For example, some enterprises find the idea of rapid browser change to be disconcerting at best and potentially unmanageable at worst. Add-on compatibility is another. I acknowledge these issues are complex and difficult. There is work to be done to make the rapid release process smoother and hopefully more useful to more of our userbase. I’d like to describe why I believe the rapid release process is important enough to pursue despite these difficulties.
Before Mozilla instituted the rapid release process, we would sometimes have new capabilities ready for nearly a year before we could deliver them to people. Web developers would have to wait that year to be able to make their applications better.