On a day like today with a major quarterly release, I often wonder what kind of manpower it takes to pull it off; and what kind of manpower (or womanpower) telerik has available to do it. I've been surprised to see that the forums are still somewhat alive with telerik support contributions today - since I'd figured everyone would be doing their part to get the release out on time. So my first question is...how many people currently work at telerik?
My next question is with respect to the process by which releases are published. I'm sure I can't even fathom all the steps that are required in order to do a release, but I'd sure be curious to hear what they all are, and in what order they happen. I only mention it because I'm sure that the .dll's and other folders are sitting ready to go the morning of the release but other preparations are made so that all hell doesn't break loose once the code is out there.
That being said, I'm quite sure that many developers would simply like to get their hands on the new stuff and wouldn't be worried about a 12-24 hour delay in the supporting materials (documentation, QSF, etc.). I'm sure it sounds petty to whine about waiting until the end of the day (it's 6pm EST now and no release yet) for the release; however, when telerik announced the March 21 release date a few months ago I'm sure I wasn't the only one that circled that date as one to do a whole lot of updates (and perhaps start on some new projects). It's just a little unfortunate in my own case, and maybe a few others (or maybe quite a few others), that a whole day has been "wasted" (for lack of a better word) waiting for the published release.
My second question was in the above paragraphs somwhere ;)
Just my thoughts, anyway.
My next question is with respect to the process by which releases are published. I'm sure I can't even fathom all the steps that are required in order to do a release, but I'd sure be curious to hear what they all are, and in what order they happen. I only mention it because I'm sure that the .dll's and other folders are sitting ready to go the morning of the release but other preparations are made so that all hell doesn't break loose once the code is out there.
That being said, I'm quite sure that many developers would simply like to get their hands on the new stuff and wouldn't be worried about a 12-24 hour delay in the supporting materials (documentation, QSF, etc.). I'm sure it sounds petty to whine about waiting until the end of the day (it's 6pm EST now and no release yet) for the release; however, when telerik announced the March 21 release date a few months ago I'm sure I wasn't the only one that circled that date as one to do a whole lot of updates (and perhaps start on some new projects). It's just a little unfortunate in my own case, and maybe a few others (or maybe quite a few others), that a whole day has been "wasted" (for lack of a better word) waiting for the published release.
My second question was in the above paragraphs somwhere ;)
Just my thoughts, anyway.