Hi,
I want to know what are the Laserfiche patch release policies? , I mean, what is the criterion used by Laserfiche to release a new patch.
Hi,
I want to know what are the Laserfiche patch release policies? , I mean, what is the criterion used by Laserfiche to release a new patch.
Hi Luis,
As Tessa notes, there are a number of factors that go into determining when full official patches are deployed. These could include the time since the past deployment, number of issues, the presence of a specific high priority or severity issue, etc. For example, we generally assume we'll do an initial patch update 1-2 months following a main release in order to collect various issues that are likely to come up right off the bat. If there's a particularly critical issue though, we might bump up the schedule. After that, it becomes more ad hoc, deploying as we have sufficient need to do so, as well as a factor of our schedule for future releases - working on patches directly impacts our future releases so it's something we try to regulate a bit.
If a more critical issues arise in side one of these waiting periods, Support can occasionally provide a temporary workaround or hotfix to hold over until the next full patch update, although we try to limit those for the same reasons as regulating updates - it'll directly impact time available for future work. Obviously if a super-critical issue appears, that may cause us to bypass the prior timetable and put out an update ASAP, but that's pretty uncommon.
There are a lot of different policies and decisions involved with each patch, and they vary a lot depending on the specific products and context of the issues, so I'm not sure if there's a way to give a concrete answer to this. Do you have a specific question or concern?