I've been a very happy
Telerik customer for many years and have built numerous sophisticated
applications with Telerik Controls. I've also begun using Sitefinity as a key
part of my Web strategy. The Sitefinity release dates have corresponded with
the release dates of the Telerik Controls. Going forward I strongly recommend
that Sitefinity to branched off to have its own release cycle.
The reason for this
suggestion is that Sitefinity is an full-featured Application rather than a set
of Controls and as such is both complex and requires broader levels of testing
As a case in point,
I had my Sitefinity 4.4 Ecommerce site all set up and running fine ready to be
rolled out to customers. I decided to postpone opening it live until after 5.0
was released to be able to add the digital downloads product features and so as
not to have downtime on the site during the upgrade. Unfortunately, after
upgrading there have been a number of problems and bugs affecting my Ecommerce
store which won't be fixed until the 5.1 service pack. I greatly appreciate the
time Telerik Support have spent helping me and providing workarounds for things
like Checkout User Login until 5.1 is released. Since my Ecommerce store can't
wait until an unknown date of 5.1, I've opened it, bugs and all.
I've spent way too much time troubleshooting problems with 5.0, I would have been
better staying with 4.4. I would be willing to be patient about new features being added didn't expect parts of the site that worked in 4.4 to stop
Also, based on forum discussions, there are a number of people (myself
included) who have had the upgrade process complicated by confusing
documentation (for example around Forms Authentication vs the new Claims Authentication
and what the Web.config should look like). Part of that issue is that the
Documentation is not adequately written in places and there some earlier Sitefinity documentation was simply incorrect (for example incorrect
Authorize.net Payment Gateway settings which were quickly corrected after I
brought it to the attention of Telerik Support).
All of this points
to a need for greater testing of the product before release and more time to
create proper documentation. The type of documentation required for a Product
like Sitefinity and all of it's interlocking modules is more more detailed than
the documentation for how to use a RadGrid. Telerik needs to approach the Sitefinity documentation from a very different technical writing style.
Locking the Sitefinity release date to the same release timeline with the rest of the Telerik Controls can mean
releasing a less than optimal product. I for one would rather wait longer and
receive a stable upgrade with clear instructions on installation and use than
spend time addressing issues that break my existing fully operational site. Stability has to be job one for any upgrade.
I hope that Telerik
management will consider this moving forward as a way to best support