As per a request, I've renamed the two spread sheets. The original KBase Services has been renamed to KBase Services Year 1 The new KBase Services II has been renamed to KBase Services As we need to pull things forward from the Year 1 workbook, lets to so, but not until it is needed. This way, we know it's essential. Best, Tom On Sep 24, 2013, at 9:33 AM, Thomas Brettin <[email protected]> wrote:
Let's see how it works in practice.
Thanks Miriam, Shane.
Tom
On Sep 24, 2013, at 8:40 AM, Shane Canon <[email protected]> wrote:
I like this approach (i.e. <state><attempt>/<person>) since it cuts back on column bloat. Even for a mini-build I think it is useful.
--Shane
On Sep 24, 2013, at 5:02 AM, "Land, Miriam L." <[email protected]> wrote:
To be clear, I haven't always been in full compliance with my own request. Rather than doubling the number of columns in the spreadsheet, I was hoping that we could provide a little more information in the column we currently use.
Steve Moulton started using failed/steve, passed2/steve, passed3/steve for a series of deploys and redeploys. It was very helpful. If I had been consistent on using passed/miriam, passed2/miriam, passed3/miriam, then it would be clearer which version was tested and ready.
This may be an undo burden for a mini build where we have a limit of one deploy and one redeploy. In addition we use separate columns for each stage. I had a selfish interest in improving communication and developing habits that would help me in future builds.
I am willing to withdraw my request if it seems unreasonable for the current build.
Miriam
On 9/23/13 3:38 PM, "Thomas Brettin" <[email protected]> wrote:
Can you add what you need?
Thanks.
Tom
On Sep 23, 2013, at 2:37 PM, "Land, Miriam L." <[email protected]> wrote:
It would help me out if a name or initials plus a date/version were included in the spreadsheet when deployment and testing were done. It will help me communicate with the right person and help keep track of which version is being tested. After the last build, I wasn't sure if anything was deployed after I left and was untested.
Thanks.
Miriam
On 9/23/13 1:44 PM, "Yu, Dantong" <[email protected]> wrote:
OK. Let me look at both shock and awe service. Dantong
On 9/23/13 1:42 PM, "Thomas Brettin" <[email protected]> wrote:
Dantong,
Can you look into something else? Shock service or awe service?
Tom
On Sep 23, 2013, at 12:39 PM, "Yu, Dantong" <[email protected]> wrote:
I will build m5nr today. Thanks Dantong
On 9/23/13 12:40 PM, "Thomas Brettin" <[email protected]> wrote:
We need to regroup the team. There are a number of items that are lingering.
1) The last build, we need to get the ubuntu image posted. To do this we need some indication from Miriam that it's been adequately tested. We need Tom or Neal to modify the kbase.us download site to point at it.
2) We need to agree to get the mac dmg out the door, or say we're not going to get it done.
3) we need to start running mini-builds. We're already totally missed two weeks. I'd like to start one today. We have the following
m5nr communities_api invocation_service shock_service awe_service
The latter two are just installers, but should be tested in the test environment.
4) we need someone to act as the primary coordinator of these minor releases.
Please advise me of your availability and willingness to work on releases this this week and each following week until the SAC.
Tom
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team
_______________________________________________ Release-team mailing list [email protected] https://lists.kbase.us/mailman/listinfo/release-team
_______________________________________________ sysadmins mailing list [email protected] https://lists.kbase.us/mailman/listinfo/sysadmins