my suggestion would be to introduce a regular update of Aspose.Pdf. In my opinion, it would be better when you offer your product weekly new for download, in which your fixes and updates are tested in ISTQB Standard. I have the feeling, that the programmer himself is the tester.
Furthermore, it is so that I as a programmer cannot forecast when you will have a new update of your product. Please also publish schedules as long you need for specific patches or bug fixes. The way the situation is at the moment, it is not very easy to plan for my own schedules.
As a normal release practice, we try to publish the new release of Aspose.Pdf for .NET in the first week of every month and every release under goes the detailed Unit testing cycles. However concerning to hotfixes/patches, they are only prepared if a fix for a very high priority/critical issue or an issue which is affecting many customers is required.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
Enables storage, such as cookies, related to analytics.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.
Sets consent for personalized advertising.
Cookie Notice
To provide you with the best experience, we use cookies for personalization, analytics, and ads. By using our site, you agree to our cookie policy.
More info
Enables storage, such as cookies, related to analytics.
Enables storage, such as cookies, related to advertising.
Sets consent for sending user data to Google for online advertising purposes.