v15 contains no bug fixes?

[MaXyM]

Am I blind or v15 beta contains no bugfixes at all? only changes / new features instead.
I reported a lot of bugs, found in v13.5, v14 and v14.1 which remains unfixed.
In one of recent emails from Sparx they wrote they are "hoping" to include some of those fixes in next release. Unfortunately I cannot confirm any of them.

What is happening? Is it normal for betas to not include bugfixes or it's common for all versions?

BTW where to find element "overview" window in v15 (this one which contain some general information about selected element in pure plain text)

[qwerty]

Well, if you are busy implementing more useless features there isn't any time left for making bug fixes. Seems logical to me.

q.

[bknoth2]

The bugs and obliviousness to the user experience may bring EA down, in my humble opinion. I'm going to show another company how to use it to develop a model of their system today, but my message will be "modeling is a very powerful technique, but EA is so quirky you should evaluate other tools as well). I'm a die-hard EA user, but I can't imagine how newcomers deal with all the quirks.

[Glassboy]

That makes sense to me.  Implement all your new features.  Take a stock take of the defects and see which ones still exist and target x.1 or x.2 to address them.  The new features may replace components with defects.  Why create yourself a regression testing nightmare.

[Eve]

There are a lot of bug fixes in EA 15.

I'm sorry to hear that the issues you reported haven't been addressed.

[MaXyM]

TBH I cannot see any bug listed in changelog.

Here is small selection of issues I've reported and are not fixed in v15:
* Missing "All connectors type" from Legend
* Legend doesn't work for Information Flow connectors
* CommunicationPath remains not traceable
* if port has name and alias set, both are displayed on diagram

Yeah.. I'm sorry too. Those are not "my" issues. Everyone might be affected by them easily.

On the other hand I got email response from Sparx support, that one of issues reported by me (related to database RE) is already marked as fixed, but did not get into build. I don't know what about the rest 20 bugs reported, but maybe one day...

[Eve]

TBH I cannot see any bug listed in changelog.

That doesn't mean that no bugfixes where included.

Yeah.. I'm sorry too. Those are not "my" issues. Everyone might be affected by them easily.

I didn't mean to suggest that they only impacted you. Only that you reported them.

* Missing "All connectors type" from Legend

Is there any reason why an option not existing is a bug?

* CommunicationPath remains not traceable

There are plenty of connector types that aren't listed in the traceability window.

* Legend doesn't work for Information Flow connectors

Sounds like a bug, but not one that's going to prevent you from modeling.

* if port has name and alias set, both are displayed on diagram

Despite someone here confirming the behavior is what you described, I have a feeling that it has something to do with the 'Use alias field for role' option on the behavior preferences page. The '/' denotes the role. "Fixing" it for you may be the exact opposite for other users.

As I said, I'm sorry that the issues you reported haven't been changed and for the impression you have that we aren't fixing issues in general.

[MaXyM]

Are you answering on behalf of Sparx?
Because all those issues has been already confirmed by Sparx support as issues to be fixed in future release(s).

Any way:

Is there any reason why an option not existing is a bug?

Because:
1. I had existed in v13.5, but removed with no reason in v14
2. Similar option still existing for elements. Again, missing this option for connector is unjustified
3. if I can color different type of connectors using the same filter (ie tagged value), I need to create multiple redundant Legends.
4. besides this option does not exists on the list, it's still possible to achieve this feature, by not touching connector type drop-list: so drop-list shows "Aggregation" while a Legend behaves like "all types".

Isn't it enough?

Sounds like a bug, but not one that's going to prevent you from modeling.

You missed the fact, that a Legend is not a modeling tool but diagramming one.

Despite someone here confirming the behavior is what you described, I have a feeling that it has something to do with the 'Use alias field for role' option on the behavior preferences page. The '/' denotes the role. "Fixing" it for you may be the exact opposite for other users.

No. Whatever I select, it doesn't show values properly.
Here are settings you are talking about. It's pretty clear that it should give possibility to display Alias only without name.


At first, those options are valid only on diagrams for which 'Use alias if available' is enabled. So, why alias is rendered next to name if this option is disabled?

At second, if 'Use alias if available' is enabled, there is no option to suppress displaying a name. Doesn't matter what combination of option I use.
I don't know what 'Alias only' means for you, but for me it means alias only, without name.

Also EA manual says: "Select the checkbox to use the Alias property of instances of elements to show the Role property". Mentioned issue appears on classifiers too.

So... it seems like 3 bugs in one feature. Achievement acquired

And to back to the topic:

TBH I cannot see any bug listed in changelog.

That doesn't mean that no bugfixes where included.

Really?
From announcement post:

For a full list of features and fixes included please see:

and from history page:

Changes and fixes for Build 1500 BETA

[Eve]

I trying to demonstrate why those issues can't necessarily get a quick fix in our next build. They aren't that straight forward. Even if an initial investigation from support says it's an issue, a more detailed investigation may reveal that it is that way for a reason. Or, the other very likely explanation is that there are more important things to fix.

[MaXyM]

There are bugs which fixing is a matter of a minute literally, especially since I've provided ready to use solution. In this particular case I'm thinking about a bug which lays in query being sent to Postgres database during its RE, which results in loading unneeded system objects (when option ignore system objects is enabled). It's just a matter of replacing one field by another in the query condition. Reported more than year ago...

Sorry to say, but your argumentation, while might be valid in some cases, is not applicable for several others.

Even if an initial investigation from support says it's an issue, a more detailed investigation may reveal that it is that way for a reason. Or, the other very likely explanation is that there are more important things to fix.

Then it should be communicated to a reporter (to us in this case), shouldn't it?. Sparx is paid for the product AND for a SUPPORT. We are paying the fee for 4 years now, finding that the support is close to none, considering that no single bug we reported during this time has been fixed. Instead of this more and more things broke as time flies.

[MaXyM]

v15 beta2 released.
Thank you for extensive change log:

General bug fixes based on feedback

Of course no fixes for issues mentioned in this thread have been included.

Edit:
I found however two issues fixed:
IssueID: 18048589 - Imported database tables are not properly stereotyped. In result are not seen by Database Builder.
IssueID: 18090358 - Discrepancy in a names of tagged values which define Owner (schema), DBversion and Tablespace. It ended up with duplicates of tagged values, which were named upper case, lower case, mixed case

[Geert Bellekens]

v15 beta2 released.
Thank you for extensive change log:

General bug fixes based on feedback

Of course no fixes for issues mentioned in this thread have been included.

Yeah, that really like saying: "We did a bunch of stuff but can't be bothered to actually list what we did" 
Last time we complained about not getting any release notes with a new beta version, so I guess they setup a new policy requiring each release to have release notes; and this is the result. Technically there are release notes so...

People are the same everywhere

Geert