October 6, 2015
A new hotfix for RAD Studio XE7 (but also Delphi XE7 and C++Builder XE7) is available on CodeCentral, but only for Update Subscription customers.
Called "
Summer 2015 XE7 Update Subscription Update
", a new hotfix for XE7 is available on CodeCentral. As you can guess from the name, we planned to release it a couple of weeks ago (well, they say October is part of Indian Summer in California). Anyway, the idea is to use a "season" name, rather than a number, to make it is easier to refer to different fixes released over a longer time period.
It is important to notice that this hotfix is available only for Update Subscription customers. This is part of the new model introduced by the company since earlier this year and you can read more about at www.embarcadero.com/products/rad-studio/update-subscription.
What is the rationale of this approach? Many of our customers told us that even if they are on Update Subscription they don't plan migrating all developers, and even less all existing projects, to the latest release, which is why offering fixes for some of the most critical bugs in older releases is relevant. Notice we don't plan to update target operating systems support in older releases, although some exceptions might happen. If you need to target the latest operating systems, particularly the mobile ones, staying current with RAD Studio will be an advantage.
However, if you have projects based on XE7, this hotfix can help with a few quite core issues, mostly in the RTL. The list of actual fixes (a dozen, all customer reported issues either on QP or QC), along with the download -- a whopping 670MB, please ignore the "Download 0 bytes reference" -- is available at:
cc.embarcadero.com/item/30410
We are currently working on fixes for XE6 (very similar to the XE7 set) and XE8 (mostly focusing on regressions already fixed in 10 Seattle). This work is done as part of the new Update Subscription model promise to offer fixes for past versions for up to 2 years, which is a significant change from the past approach.
posted by
marcocantu @ 2:50PM | 16 Comments
[0 Pending]
16 Comments
Summer 2015 XE7 Hotfix Available
Good news!
Comment by Rodrigo Farias Rezino on October 6, 15:59
Summer 2015 XE7 Hotfix Available
I just had a Clipper flashback with the naming
convention. :)
Thanks for following through on delivering updates for
(slightly) older versions.
Comment by Bruce McGee on October 6, 16:49
Summer 2015 XE7 Hotfix Available
Does this cover previous versions
that you get with the XE10
purchase?
Comment by John Doe on October 6, 19:35
Summer 2015 XE7 Hotfix Available
Naming after seasons? really? Does that mean that us
antipodean developers have to wait another six months
to get the fixes?
Comment by Alister Christie
[http://LearnDelphi.tv]
on October 6, 20:39
Summer 2015 XE7 Hotfix Available
@Alister : Maybe it's to give us 6 months' lead to
properly debug the hotfix.
Good move.
Comment by Peter Wright
[]
on October 6, 22:16
Summer 2015 XE7 Hotfix Available
I concur with Alister, seasons are opposite on the
other side of the world, so you confuse people for no
reason. Called it the 'October 2015 update' and you
won't confuse anyone.
Comment by Darren on October 7, 01:22
Summer 2015 XE7 Hotfix Available
Which summer of 2015? We had summer as of Jan 2015 and
approaching another summer in December 2015. Please
choose another naming convention that suits us all.
Comment by Francis Iacono on October 7, 02:58
Summer 2015 XE7 Hotfix Available
Sorry you guys down under... we'll consider a different naming
convention, without hemisphere related seasons.
Comment by Marco Cantu
[http://www.marcocantu.com]
on October 7, 06:47
Summer 2015 XE7 Hotfix Available
I have no subcription, but I have bought the
XE7Ent-License on a regular way.
Now 'Summer 2015 XE7 Hotfix' is out and I can't use
the Hotfix, because I have no subcription. So I have
to pay twice for the bugs.
Please find a customer-friendly solution, for
customers without subscription to get a 'bugfree'
Rad-Studio ( Only Bugfixes - no new features)
Currently I feel like a 'second quality customer'...
Comment by JIM on October 7, 10:40
Summer 2015 XE7 Hotfix Available
Marco,
Please, Is that HotFix solve the issue related
here https://quality.embarcadero.com/browse/RSP-
9568?
Regards.
Comment by Rogerio on October 15, 14:07
Summer 2015 XE7 Hotfix Available
I concur with JIM. I am also not a subscription owner
BUT if this means the hotfix will not update my XE7Ent
version and this hotfix has bug fixes then the value
of this product, to me, is lessened.
To me this is equivalent to a sale without long term
warranty/guarantee. That this product is not suitable
for use.
It is my belief that the subscription model is flawed
from a customers perspective but may be a great money
maker from Embarcadero's perspective.
When I buy a product I invest my or my company's hard
earned cash in the quality of the item I bought and
fully expect it to be fixed if it is broken.
Just my 2 cents
Comment by Kelvin on October 16, 13:39
Re: RSP- 9568
Rogerio, the out of memory issue wasn't due to a memory
leak, but to overall memory consumption. RAD Studio 10
Seattle has a complete solution, made of different pieces,
very hard to back port any of it -- and keeping compatibility.
Comment by Marco Cantu
[http://www.marcocantu.com]
on October 29, 08:36
Summer 2015 XE7 Hotfix Available
Kelvin,
you write "the value of this product is lessened". How so? In
the past, Embarcadero never released a hotfix after the a new
version was released. We are providing some "extra value",
not diminishing the existing product in any way.
You also write "this is equivalent to a sale without a long term
warranty"... and this is true. As most hardware and software,
you have a basic warranty included in the product, but for an
extended warranty you need to pay an extra. This is exactly
what Update Subscription is for. It is a way to get newer
releases and long-timer updates for current and older
releases.
-Marco
Comment by Marco Cantu
[http://www.marcocantu.com]
on October 29, 11:11
Summer 2015 XE7 Hotfix Available
Marco,
Embarcadero has released updates for older products
after the new version was out. If not via hotfix then
by posting the changes so that we as developers can
update ourselves. I believe the last Delphi 7 fix for
the security vulnerability comes to mind.
As for lessening the product value I refer to the fact
that when I create an app I generally do it with the
express intent of long term use. I still have apps
created in Delphi 7 (some were originally created in
version 3) that I support for any bugs found. Keeping
in mind that due to a customers use they may only find
that bug if a particular sequence of events occur.
That does not mean I provide them with any new
features only fixes to a bug that existed at the time
they bought or paid for the product. I have been a
Delphi developer since version 1 and now, with regrets
finally move away. Based on this support model I
cannot, in good conscience provide applications as is
where is. Sorry
To put this is perspective I liken it to all the auto
industry issues in the past couple of years where
defects were found long after people's warranties were
expired. Recall notices were still issued to
repair/replace. A product must be fixed if it was
significant and it existed at time of sale. Just
saying by the next version cuz it fixes all the
problems of the old is not standing behind the product
you actually sold.
Anyway I wrote this just to clarify my personal
opinion for you and wish you well into the future. To
your co-workers and yourself thanks for many years of
a great creative product.
Comment by Kelvin on November 9, 15:08
Summer 2015 XE7 Hotfix Available
First, thanks for following through on the update
hotfix.
Next about the non-subscription purchases. When I
first started creating applications (30 years ago)
I did it without knowledge of quality standards of
other software companies. I "lived under a rock"
in a sense. One day I discovered that some
software company did not fix bugs but allowed them
and there was an attitude that bugs "we to be
expected and tolerated". I was surprised because
my "under the rock" belief was that a company had
an obligation to fix bugs because the customer paid
for a working product. 30 years later I still hold
on to the idea that software "should not" have bugs
and that bugs must be fixed as a high priority on
the basis that the software developer has to hold
his end of the sale. Many people say "all software
has bugs" but that's just an excuse to not fix
them.
Comment by Bill Egge
[http://www.eggcentric.com]
on November 12, 19:41
Summer 2015 XE7 Hotfix Available
Hello,
I totally agree with the guys who say that a product
that has bugs when I buy it should be repaired for
free. I started with Turbo Pascal long time ago and
went through Delphi and now I'm in Firemonkey. The
last versions called XE sometimes were very
disappointing. We bought versions which promised
features for mobile devices, but didn't support them
properly (cameras, bluetooth, other sensors). Many of
the features came only with a later version. We now
split between Delphi and java, because there we can
rely on getting support for new devices immediately.
In Delphi there isn't even a usable help function. I'm
much quicker using google. And now you even stop the
support for customers that bought your product and
expect to get bugs fixed for free. If I would do this
to my customers they would just turn to other
companies and that's understandable.
So please think this over in a sense of a fair
relationship.
Comment by Udo Gromoll
[http://www.gromoll.de]
on February 4, 13:31
Post Your Comment
Click
here for posting
your feedback to this blog.
There are currently 0 pending (unapproved) messages.
