Delphi 12.1 & New Quality Portal Released

-

The Delphi 12.1 update has been released. Besides a number of bug fixes, this release also has a few new features.



The most notable ones are the new Split Editor, which allows having multiple files opened side by side; and support for Android API 34.

You can find more information about what is new in this update at https://docwiki.embarcadero.com/RADStudio/Athens/en/12_Athens_-_Release_1

However, the greatest change for all Delphi developers is a new bug tracking portal that replaces the old one, still available in read-only mode at https://quality.embarcadero.com/.

The new portal is hosted in Atlassian Cloud https://embt.atlassian.net/servicedesk/customer/portals or through a redirect https://qp.embarcadero.com and is based on Jira Service Management (JSM), while the internal bug tracking system, which was also migrated to the cloud, was not changed and is running on Jira. This move to the cloud was inevitable, because Atlassian retired their Server line of products.

JSM is a lightweight bug tracking system, and there are some changes in the workflow and capabilities compared to Jira.

The user interface is much simpler, but in some parts also a bit more confusing to those of us accustomed to Jira. Namely, JSM is more of a customer support portal designed for managing customer requests and issues on an individual basis, and not so much oriented towards being a collaborative bug tracking system with shared issues.

Reported issues can be shared among multiple customers, but you have to explicitly share your report (fortunately, that is the default behavior) if you want others to see it.

Another nuisance is that once submitted, the report cannot be edited, and you can only post comments. So we should all remember to read our reports more carefully before clicking Send.

Once you log in, you will be able to choose what you want to report: New Feature, Bug, or Documentation Bug. What is not so obvious is how you can inspect already filed reports. This is hidden behind the Requests button in the top bar. In the pulldown menu, you will be able to select issues you have reported, all issues, and issues reported by Embarcadero Customers. This strange Embarcadero Customers entry is basically a special group that allows sharing reports between different reporters.



When you are submitting a new report, at the very bottom you will find a dropdown menu Share with:, where you have to select Embarcadero Customers (this is the default option) if you want to make that report visible to all. If you select No one option, then your report will not be visible to others.



Using the default, shared option, is preferred to allow others to see your issue like they always could, and spare them the trouble of reporting the same issue again. Sharing also allows others to comment, adding suggestions and workarounds.

Comments

  1. GuruApril 12, 2024 at 9:59 AM

    They keep changing their website address every few years. All links will be broken again now.

    ReplyDelete

Post a Comment

Popular posts from this blog

Coming in Delphi 12: Disabled Floating-Point Exceptions

-
Delphi 12 is in the works. One of its small features that will have a huge impact is a change in the default handling of floating-point exceptions, which will now be masked on all platforms. Previously, floating-point exception handling was different across platforms, and most notably on the Windows platform: In VCL and console applications, floating-point exceptions were not masked and would raise an exception. On the other hand, FireMonkey applications had all floating-exceptions masked by default, regardless of which platform they were running on. Basically if you haven't explicitly changed the exception mask in your code to some value other than the default, and you had code that attempted to divide some number with zero, you would get an EZeroDivide exception in previous Delphi versions on the Windows VCL application. In Delphi 12, there is no exception, and the result of such a division will be +INF . So the following code will no longer raise an exception. If you were r
Read more

Beware of loops and tasks

-
Loops and anonymous methods don't go hand in hand. Any variable that changes for each iteration will cause problems if it is used within an anonymous method. I explained the mechanism behind variable capturing in the post Mysterious Case Of Wrong Value , along with the problem it causes with loops and its solution. Commonly, anonymous methods are used as callbacks or event handlers, where there are no loops in the context where variable capture happens. While there is a possibility to have an unexpected—wrong—value in such scenarios, it is rather easy to debug them and understand the order in which some code is called, and why the captured value is wrong in a given place. With the rise of multi-threading usage, and especially the Parallel Programming Library and tasks, writing anonymous methods inside a loop becomes more common, and it is much easier to write code where a captured variable will have the wrong value. The biggest problem with such code is that it will be harder to
Read more

Catch Me If You Can - Part II

-
It has been quite some time since I wrote the Catch Me If You Can post about the inability of LLVM-backed compilers to catch non-call hardware exceptions. In other words, hardware exceptions raised by code written in the same block as the try...except exception handler. Since then, more LLVM-backed compilers have been added to Delphi, and with those, more reasons to change common coding practices... but still, very few developers know about the issue. The original article covered only try...except exception handlers, and exploring what exactly happens with implicit and explicit try...finally handlers was left as an exercise to the readers and to some future, now long overdue, post. And Now: All Hell Breaks Loose When you read about non-call hardware exceptions not being caught by an immediate try...except block, the implications might not look too serious. After all, while plenty of code can raise exceptions, try...except handlers are not that frequently used in places, as mo
Read more