Sparx Systems Forum
Enterprise Architect => General Board => Topic started by: Marc Vanstraelen on October 12, 2016, 10:56:03 pm
-
I was getting everything ready to migrate EA in our organisation from version 10 (build 1009) to version 12.1 (build 1230).
Now I see that Sparx just released the first non-beta build of version 13 (build 1305).
I see three options:
- Go ahead with the planned roll-out of version 12.1 as this is now stable, to give users the advantages of a set of new features;
- Immediately roll out EA13, to have even more new features (time-based modelling seems cool), but with the risk of bugs still to be resolved in new builds;
- Wait until EA13 has stabilised and remain on EA10 for now.
Considering that it has taken about 6 months between the initial release of version 12.1 (build 1224) and the final build 1230, I think it might be too soon yet to go for EA13 and it would be safer to wait until it has stabilised. Staying on EA10 would leave us out of some interesting recent features, so I think migrating to EA12.1 would be be best course of action.
What would you do? Do you have any comments / considerations / recommendations?
-
The big issue I see is their introduction of ribbons (argh!). That will impose the need for a whole new training set. So if you have "average users" you probably go directly to 13. OTOH you seem to be quite conservative (still on 10). So maybe you can postpone this training for quite some time and jump on board with V14.
q.
-
I'm still waiting a bit to upgrade my clients to v13.
They already released a newer version (1306) and I guess there will be some more (bugfix) releases following in the next few months.
So if you can bear to wait a few months I would recommend to go directly to v13 (saves the users one game of "easter egg" searching for menu options)
If you have to upgrade right now I would go to v 12.1
Geert
-
We stil stay on V12 and we know some issues to be fixed in V13, before we switch (maybe Build 1307).
-
My observation is that there are bugs in v12 that are only fixed in v13. So the rationale that v12 will have fewer bugs is false. Further more you will not get the newer MDGs (Archimate 3 et al) and you'll be stake with some broken models (new blah via wizard) that they missed updating from previous versions.
-
Considering that it has taken about 6 months between the initial release of version 12.1 (build 1224) and the final build 1230, I think it might be too soon yet to go for EA13 and it would be safer to wait until it has stabilised. Staying on EA10 would leave us out of some interesting recent features, so I think migrating to EA12.1 would be be best course of action.
Releasing of new builds isn't just making things stable. The timeline you mention for 12.1 has more to do with how long active development on 12.1 continued before we focused exclusively on 13.
-
As of yesterday, recommended that our organisation move to v13 (1305), only to find the SILENT upload of 1306 just after I sent the email.
NO comment...
Paolo
-
Silent?
It was paired with a mailout to our complete user base.
That's the digital equivalent of shouting it from the rooftops.
It looks like the forum may have been (edit - a little late), but everything else announces 1306 has been released.
-
Didn't get to me - a registered (personal) user.
I'll check if I'm the recipient for the organisational email for the organisation - I suspect procurement is... Are multiple contacts allowed against the customer account?
Paolo
-
As far as I know, you'll get future newsletters if you go to http://www.sparxsystems.com/press/newsletter/subscribe.html (http://www.sparxsystems.com/press/newsletter/subscribe.html)
-
Silent?
It was paired with a mailout to our complete user base.
That's the digital equivalent of shouting it from the rooftops.
It looks like the forum may have been (edit - a little late), but everything else announces 1306 has been released.
I got the email (twice) once as a VAR and a few days later as a registered user.
But must admit that it didn't struck me that there was a new version as I always keep an eye on the forum to know when a new version is released.
That's how we (professionals) make the difference from regular users you know. We can amaze them by telling exactly which the current version is and when it was released. 8)
Geert
-
As far as I know, you'll get future newsletters if you go to http://www.sparxsystems.com/press/newsletter/subscribe.html (http://www.sparxsystems.com/press/newsletter/subscribe.html)
So it was sent to subscribed users, not registered users....
As Hillary said to Donald... "Words matter!"
Paolo
-
"registered" was your word, not mine.
-
My bad, Simon.
BUT you DID say complete user base.
Complete would (at least) imply registered...
Complete user base includes registered users, Paolo is a registered user => Paolo should have got the email. "Modus ponens"
I recall once having to explain to some developers that if an item appeared in a more precise search it ALSO had to appear in the broader, encompassing, search. Their code didn't do that...
There are natural implications that hold.
Paolo
-
Yes, I used the wrong word too.
Even if we had a means of collecting the email addresses of our complete user base, it wouldn't be appropriate to send mail to all of them.
While we're being pedantic. Just going to the page I linked wont subscribe you to our mailing list. You actually need to enter your email address and click Subscribe. (Or an equivalent action that submits the form with that action.)
A release announcement on the forum (and even the website) reaches a very small minority of our customers. An announcement on our customer mailing list reaches a much higher number (hopefully a majority) of the people interested in the release new versions.
PS. Broader doesn't necessarily mean superset, although encompassing would. I hope you used the right words then, or even better a Venn diagram.
-
Sparx Systems generally doesn't send an email for the build releases, generally only major releases (like the recent release of v13).
In other news build 1307 has just been released ;-)
-
Sparx Systems generally doesn't send an email for the build releases, generally only major releases (like the recent release of v13).
In other news build 1307 has just been released ;-)
Yes, I noticed it...
Given what you said Tom, the standard procedure should be:
Post to forum, then if major version, announce to subscribers.
HTH, ;)
Paolo
-
I have side by side installs of 12.1 and 13.
Those considering updating can use this approach or have a set of people pilot the update.
-
I decided to roll out EA12.1 for the moment. Enough useful new features compared to EA10 that people will need to get familiar with.
We'll consider EA13 sometime next year.