Maybe today at the developer meeting you could ask each developer to summarize the significant changes in their service(s) since the Feb release? (But someone else will have to take notes--I unfortunately have a conflicting meeting.) For future releases, it would be good to have a less interventional way to collect this information, like maybe release notes or something similar. Nomi On May 29, 2013, at 9:42 AM, Thomas Brettin <[email protected]> wrote:
Right, I don't plan on going through the commits either. I don't have a change list. It would have to be constructed by talking with each developer.
On May 29, 2013, at 11:41 AM, Nomi Harris <[email protected]> wrote:
Sure, I can put together an announcement if you send me a change list. (Combing the git commits is not a useful way to get that. There have been thousands of commits since Feb., most of which are not interesting to anyone outside of KBase.) Nomi
On May 29, 2013, at 9:39 AM, Thomas Brettin <[email protected]> wrote:
I was wondering last night if you are going to prepare the text for the updates to the public site?
On May 29, 2013, at 11:36 AM, Nomi Harris <[email protected]> wrote:
How is the release coming along? Have the updated services been pushed to production? Do we need to update some of the downloads on https://www.kbase.us/developer-zone/downloads/ ?
Any changes needed on https://www.kbase.us/developer-zone/services/ ? (BTW, I just noticed that something funny has happened with the fonts on that page--the service names are now in a different font, and no longer bold.)
When the release is ready, I'd like to put up an announcement on kbase.us. How can I get a summary of what's changed in this release?
Thanks, Nomi Harris Project Manager, KBase