Hi

That is a great question..!

While there is a schedule for the full versions (141, 142 etc) that can be seen at https://whattrainisitnow.com/calendar/, the dot releases are done as needed to fix unforeseen security and stability issues.

Paul,

Thanks for the quick response.

Sure, the dot releases are only done as needed. So does that mean the same day the issue is discovered, the fix happens and the patch is release? Does it sometimes take awhile to find and fix the problem? If the answer to the first question is yes, then there's nothing to announce. If it's the second question, then an announcement somewhere that can be monitored would be nice. It's not like there's never been a .1 patch followed by a .2 patch a few days later. The release schedule is hectic enough, so knowing a fix is in the pipeline would be helpful.

Cheers.

It depends on the issue and the urgency around it plus how quickly it can be fixed, tested and released.

If the issue is lower priority or there are several smaller low priority issues, it might take a few days to do one update rather than lots of small updates.

If the issue is higher priority it will be made available as soon as it is ready.

The focus is on getting a dot released out, but certainly if we have people asking about a particular problem here in the support forum and we are aware of an update to fix it, we will try to make people aware as soon as we are able.

Paul Where would the link to releases normally be found? I was looking for something like the link you included in your last reply and was unsuccessful finding it.

Also, I've noticed the releases off schedule tend to be fixes required shortly after a release. This would suggest that there was insufficient testing done to catch the issue in test mode. I don't see any kind of full volume testing comparing production to test on the release schedule. Can you explain how you can tell testuing has covered all the bases? Has any analysis been done on the frequency of fix releases by programmer or on the nature of the release and post release issue to try to pin point the reason for the fix so it can be addressed? Are full reviews done on every release that created a subsequent issue for production? What steps are being taken to eliminate fix releases?

I used to manage the release process for our shop. I was the mean traffic cop that forced programmers to follow the rules and they didn't like it very much. But, our oncall dropped to almost zero which saved the company thousands of dollars plus there was many more savings which were appreciated by the people impacted and we had a stable and reliable system. It took a while but the programmers began to see that they too benefited from the initiatives I was enforcing and they came around and ultimately supported the traffic cop role as it was working.

These unexpected releases just destroy my productivity and cost me a great deal of money. I'm tempted to use a different browser but I would prefer to continue with firefox.

Thanks for your assistance.