Release Changes

9 posts, 0 answers
  1. John S.
    John S. avatar
    90 posts
    Member since:
    Aug 2004

    Posted 24 Apr 2007 Link to this post

    Hello,

    Is it safe to assume that if I use the Prometheus controls in a current project that following releases up til the final release will be compatable?

    For instance if I use a Prometheus splitter today then next 'beta' release will I have to adjust my project because some properties or methods have been changed.

    By the way, I am very excited about the path telerik is taking. It seems to be very forward looking.

    Thanks,
    John
  2. Todd Anglin
    Todd Anglin avatar
    2040 posts
    Member since:
    Aug 2005

    Posted 24 Apr 2007 Link to this post

    John,

    That is a generally safe assumption and something we'll do our best to deliver. Nonetheless, one of the key "risks" of using "Prometheus" during the beta is that there may be some changes of the nature you described as more complicated controls are brought into the suite (such as RadGrid and RadEditor).

    We want to make sure the framework is as efficient as possible for years of superior performance and support, and to do that some changes to the "Prometheus" core may be required over the next year. If those changes are required, though, we'll definitely help you migrate by providing clear upgrade instructions.

    Does that help?

    Thanks~
    Todd
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. John S.
    John S. avatar
    90 posts
    Member since:
    Aug 2004

    Posted 24 Apr 2007 Link to this post

    Todd,

    Yes that helps in one way but brings up another question.

    1. Let's say I have a project scheduled to deliver in July and I use the Prometheous controls in it.
    2. I finish it, install it, and don't hear from them for a short amount of time, let's say a month or two, at which time they need a very simple change.
    3. In the mean time 2 new updates have happened to the control set and it breaks some things in this project, fixable, but nonetheless breaks.
    4. At this point I have to put in a significant amount of time to update a project that would usually have taken me less than an hour to change.
    That situation is my concern.

    Typically, I wouldn't use a beta control because of this reason; however, telerik has introduced this 'Go-Live' beta idea which is very confusing to me.

    The 'Go-Live' beta  seems equivelant to a person going in for a clinical drug trial with a disclaimer saying there are major risks and then the doctor leaning over and saying "don't worry, this is not your standard drug trial, you'll be fine" The patient then thinks ahhhhh this is safe, I'll take the drug. A month later the patient dies and the doctors tell the familiy "but it was a clinical study....we told you the risks upfront"

    I am not trying bad-mouth what you are doing....I want to use these new controls (and probably will); however, I don't understand why you just didn't call it a beta.

    Thanks,
    John

  5. Stuart Hemming
    Stuart Hemming avatar
    1622 posts
    Member since:
    Jul 2004

    Posted 24 Apr 2007 Link to this post

    TBH John, I think the problem is going you outline is going to exist for longer than just the beta period. I don't think, from what I've read, that there is much danger of moving away from a single assembly.

    --
    Stuart
  6. surfer
    surfer avatar
    585 posts
    Member since:
    Jul 2003

    Posted 24 Apr 2007 Link to this post

    The Go-Live thing was first introduced by Microsoft with the Atlas Beta I believe. In words, Go Live is explained here:

    http://msdn2.microsoft.com/en-us/netframework/aa663302.aspx

    I am not sure what this means in telerik world, but most questions are answered here (Prometheus FAQ):

    http://www.telerik.com/products/aspnet-prometheus/faq.aspx

    But  yeah, Beta, CTP, Refresh, Go-Live... it is really hard to figure out what is beta nowadays. And Google services stay in betas forever (Gmail).
  7. John S.
    John S. avatar
    90 posts
    Member since:
    Aug 2004

    Posted 24 Apr 2007 Link to this post

    Surfer,

    I hadn't seen the use of the word 'Go-Live' before; thanks for bringing that up to me.

    I got the feeling from what I read about Prometheous is the beta tag is there because other controls will be added to the 'one' assembly. My question was raised because I thought it may imply the current controls are really finished except for behind the scenes stuff that may need to be fixed but won't affect the current feature set.

    In any case, it probably seems like I am making a bigger deal about things than I really mean to. Sometimes converstional stuff translated to a forum comes across with a more than intended serious tone.

    Regards,
    John
  8. surfer
    surfer avatar
    585 posts
    Member since:
    Jul 2003

    Posted 24 Apr 2007 Link to this post

    From what I see in the current architecture, I feel no major changes will occur. Prometheus controls match almost verbatim Mcrisoft Ajax Extensions server-side and client-side specs (which is a good thing) and adhere to the standards Microsoft Ajax Contols are using, so I do not anticipate major changes. The Prometheus FAQ supports this opinion as well.
  9. Todd Anglin
    Todd Anglin avatar
    2040 posts
    Member since:
    Aug 2005

    Posted 24 Apr 2007 Link to this post

    Hi guys-

    Let me try to address a few questions that have been raised here:
    1. "Prometheus" will not be moving away from the single assembly introduced in Q1. All future controls will be added to this assembly.
    2. The "Go Live" license terminology was originally introduced by Microsoft a few years ago. For Telerik this term means that you can safely use the controls in production environments and expect full product support (more than what Microsoft implies with their license).
    3. The core of "Prometheus" that is shared across most of the controls is very stable and should not change going forward. We are very committed to maintaining backwards compatibility and minimizing the hurdles to adopting these new controls.
    Hopefully that helps clear up some of the confusion. Definitely refer to the official FAQ for full details and answers.

    Thanks~
    Todd

  10. John S.
    John S. avatar
    90 posts
    Member since:
    Aug 2004

    Posted 24 Apr 2007 Link to this post

    Todd,

    Thanks!

    John.
Back to Top
UI for ASP.NET Ajax is Ready for VS 2017