Release of patches for X#
Posted: Wed Oct 06, 2021 10:01 am
Hi,
I have to raise this topic, because at the moment for the enterprise (FOX subscriber), which I represent, it has become critical.
I will describe the background.
As most of you probably know, transporting a real application from VO to X#, which is currently in production, is not an easy task. Customer requests come in and you are forced to synchronize the VO code with the X# code so that when you release the same application in X# it contains all the latest changes.
For this reason, my team chose this summer, because traditionally in the summer business activity decreases slightly (fewer requests from customers). We started in late spring and by the end of the summer we had converted two of our three biggest apps to X#. During testing, two serious problems were found that we cannot get around (stack corruption when using some types of structures and the use of the M-> prefix in codeblock expressions). For these problems, I created git tickets and the X# developers have successfully fixed it. But there is still no official version with this fixes. The last official version 2.8c was released in early July this year.
At the same time, in view of the increasingly complicated synchronization between VO and X# projects, we decided to implement all the latest requests from customers only in X#. Otherwise, we would have to postpone the migration to X# until next summer. But by that time, a huge number of changes have accumulated in the VO project that cannot be trivially transported. As a result, all current work continues only in X#. But we cannot even conduct full-fledged internal testing, let alone distribute the version to customers.
In this regard, I have an acute question about the release of critical fixes for X#. It is good practice to promptly release critical patches that apply to officially released versions of the product. And innovations and fixes of less critical problems can be postponed until the next official version. We are all developers and we understand that adding innovations can bring new hidden problems. Therefore, it is important to release critical patches specifically for the released version, the less critical problems of which are already known and the developer has somehow solved them. Is it realistic to have such a process for releasing X# versions?
We waited for the version in August (it was not critical yet). Then in September (there was news that it would probably be at the end of September). That did not happen. There was also a message that this will not happen this week either.
At the moment, my team does not understand when the fixes in X# will be released. In this regard, there is also a concern that when we release our product and some serious problem related to X# is found in it, then there is no certainty that we will receive a fix within a reasonable time. This is a matter of grave concern to us.
Best regards,
Leonid
I have to raise this topic, because at the moment for the enterprise (FOX subscriber), which I represent, it has become critical.
I will describe the background.
As most of you probably know, transporting a real application from VO to X#, which is currently in production, is not an easy task. Customer requests come in and you are forced to synchronize the VO code with the X# code so that when you release the same application in X# it contains all the latest changes.
For this reason, my team chose this summer, because traditionally in the summer business activity decreases slightly (fewer requests from customers). We started in late spring and by the end of the summer we had converted two of our three biggest apps to X#. During testing, two serious problems were found that we cannot get around (stack corruption when using some types of structures and the use of the M-> prefix in codeblock expressions). For these problems, I created git tickets and the X# developers have successfully fixed it. But there is still no official version with this fixes. The last official version 2.8c was released in early July this year.
At the same time, in view of the increasingly complicated synchronization between VO and X# projects, we decided to implement all the latest requests from customers only in X#. Otherwise, we would have to postpone the migration to X# until next summer. But by that time, a huge number of changes have accumulated in the VO project that cannot be trivially transported. As a result, all current work continues only in X#. But we cannot even conduct full-fledged internal testing, let alone distribute the version to customers.
In this regard, I have an acute question about the release of critical fixes for X#. It is good practice to promptly release critical patches that apply to officially released versions of the product. And innovations and fixes of less critical problems can be postponed until the next official version. We are all developers and we understand that adding innovations can bring new hidden problems. Therefore, it is important to release critical patches specifically for the released version, the less critical problems of which are already known and the developer has somehow solved them. Is it realistic to have such a process for releasing X# versions?
We waited for the version in August (it was not critical yet). Then in September (there was news that it would probably be at the end of September). That did not happen. There was also a message that this will not happen this week either.
At the moment, my team does not understand when the fixes in X# will be released. In this regard, there is also a concern that when we release our product and some serious problem related to X# is found in it, then there is no certainty that we will receive a fix within a reasonable time. This is a matter of grave concern to us.
Best regards,
Leonid