Re: TCK Dog
/matt grumbles about Joe burning up the electricity in his basement Joe, you've gone above and beyond. thanks On Feb 21, 2008, at 9:02 AM, Prasad Kashyap wrote: Most definitely. Thank you Joe for shouldering such a big responsibility for the project. Cheers Prasad On Wed, Feb 20, 2008 at 4:58 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: On Feb 20, 2008, at 1:15 PM, Jay D. McHugh wrote: I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Cool. Thanks a lot Jay! I think we all owe Joe a big thanks. He's done a great job keeping our TCK status in the green... --kevan
Re: TCK Dog
Most definitely. Thank you Joe for shouldering such a big responsibility for the project. Cheers Prasad On Wed, Feb 20, 2008 at 4:58 PM, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Feb 20, 2008, at 1:15 PM, Jay D. McHugh wrote: > > > I've been referred to as a puppy before :) > > > > But I'd be happy to graduate to TCK Dog. And, I already have my NDA > > registered. I am still trying to get my local TCK build environment > > set up though. > > > > But as long as I was able to transition into the role with some > > help, I'll volunteer. > > Cool. Thanks a lot Jay! > > I think we all owe Joe a big thanks. He's done a great job keeping our > TCK status in the green... > > --kevan >
Re: TCK Dog
Yeah, thanks Joe for all the hard work you have done on TCK! Paul On Feb 20, 2008, at 4:58 PM, Kevan Miller wrote: On Feb 20, 2008, at 1:15 PM, Jay D. McHugh wrote: I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Cool. Thanks a lot Jay! I think we all owe Joe a big thanks. He's done a great job keeping our TCK status in the green... --kevan
Re: TCK Dog
On Feb 20, 2008, at 1:15 PM, Jay D. McHugh wrote: I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Cool. Thanks a lot Jay! I think we all owe Joe a big thanks. He's done a great job keeping our TCK status in the green... --kevan
Re: TCK Dog
I'd be glad to help you transition ... maybe even eager, enthusiastic, exuberant :-) ! Thanks Jay! Joe Jay D. McHugh wrote: I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Jay Joe Bohn wrote: I've been the TCK Dog for about a year now, through 2.0, 2.0.1, 2.0.2 and most recently 2.1. I think it's time for a change. This activity primarily involves: 1) Building the images and accounting for changes in the various branches that require comparable changes in the test harness. 2) Applying updated Sun patches, exclude lists, etc... as necessary (this was a bigger issue when we were initially getting certified for Java EE 5 but has since dropped off. I expect it will pick up again with Java EE 6 in the future). 3) Running tests as necessary for various releases, projects, components, specs, etc... 4) Monitoring/advertising test results 5) Fixing problems in either the harness, test plans, and/or Geronimo code as necessary. 6) Working with other teams that sometimes rely on the Geronimo TCK validation (such as OpenEJB and MyFaces) 7) Summarizing results and criteria for Sun Certification We've discussed automating some of these activities in the past (such as running tests with GBuild). However, I don't believe that is working at the moment so it's pretty much a manual effort. Fortunately we now have automated Geronimo Builds and a limited number of tck tests to highlight pervasive problems. We've also had terrific involvement from the whole team in resolving tck failure issues (thank you to all those that monitor and respond to the TCK list :-) ). With 2.1.1 coming up it would be a great time for some new blood to get involved. Joe
Re: TCK Dog
I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Jay Joe Bohn wrote: I've been the TCK Dog for about a year now, through 2.0, 2.0.1, 2.0.2 and most recently 2.1. I think it's time for a change. This activity primarily involves: 1) Building the images and accounting for changes in the various branches that require comparable changes in the test harness. 2) Applying updated Sun patches, exclude lists, etc... as necessary (this was a bigger issue when we were initially getting certified for Java EE 5 but has since dropped off. I expect it will pick up again with Java EE 6 in the future). 3) Running tests as necessary for various releases, projects, components, specs, etc... 4) Monitoring/advertising test results 5) Fixing problems in either the harness, test plans, and/or Geronimo code as necessary. 6) Working with other teams that sometimes rely on the Geronimo TCK validation (such as OpenEJB and MyFaces) 7) Summarizing results and criteria for Sun Certification We've discussed automating some of these activities in the past (such as running tests with GBuild). However, I don't believe that is working at the moment so it's pretty much a manual effort. Fortunately we now have automated Geronimo Builds and a limited number of tck tests to highlight pervasive problems. We've also had terrific involvement from the whole team in resolving tck failure issues (thank you to all those that monitor and respond to the TCK list :-) ). With 2.1.1 coming up it would be a great time for some new blood to get involved. Joe
TCK Dog
I've been the TCK Dog for about a year now, through 2.0, 2.0.1, 2.0.2 and most recently 2.1. I think it's time for a change. This activity primarily involves: 1) Building the images and accounting for changes in the various branches that require comparable changes in the test harness. 2) Applying updated Sun patches, exclude lists, etc... as necessary (this was a bigger issue when we were initially getting certified for Java EE 5 but has since dropped off. I expect it will pick up again with Java EE 6 in the future). 3) Running tests as necessary for various releases, projects, components, specs, etc... 4) Monitoring/advertising test results 5) Fixing problems in either the harness, test plans, and/or Geronimo code as necessary. 6) Working with other teams that sometimes rely on the Geronimo TCK validation (such as OpenEJB and MyFaces) 7) Summarizing results and criteria for Sun Certification We've discussed automating some of these activities in the past (such as running tests with GBuild). However, I don't believe that is working at the moment so it's pretty much a manual effort. Fortunately we now have automated Geronimo Builds and a limited number of tck tests to highlight pervasive problems. We've also had terrific involvement from the whole team in resolving tck failure issues (thank you to all those that monitor and respond to the TCK list :-) ). With 2.1.1 coming up it would be a great time for some new blood to get involved. Joe
Re: TCK Dog
On Jul 28, 2006, at 4:30 PM, Joe Bohn wrote: Kevan, Sorry for being so late with this response, but I was thinking that I should probably get involved some with the TCK (to help address your desire for broader participation across the project and get some much deserved personal relief). I just faxed my NDA for confidential materials. I'll let you know when I get my authorization. Hey Joe, That's great! Thanks. --kevan Kevan Miller wrote: On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. What do you think? I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. So, it's not one dog, but several... Although I certainly had a lot of help from you, David J, and Dain, It'd be great to see a broader base of participation... I see the following pieces: 1) Keeping builds running through Continuum 2) Keeping tests running through GBuild 3) Monitoring/advertising test results. 4) Fixing problems It's #4 that can be the killer and where we should be working as a team... but the others can eat up time, also. I have #1 going for 1.1.1-SNAPSHOT and 1.2-SNAPSHOT. Hope to get #2 going later today... Now, would be a great time for getting more people involved... --kevan
Re: TCK Dog
Kevan, Sorry for being so late with this response, but I was thinking that I should probably get involved some with the TCK (to help address your desire for broader participation across the project and get some much deserved personal relief). I just faxed my NDA for confidential materials. I'll let you know when I get my authorization. Thanks, Joe Kevan Miller wrote: On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. What do you think? I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. So, it's not one dog, but several... Although I certainly had a lot of help from you, David J, and Dain, It'd be great to see a broader base of participation... I see the following pieces: 1) Keeping builds running through Continuum 2) Keeping tests running through GBuild 3) Monitoring/advertising test results. 4) Fixing problems It's #4 that can be the killer and where we should be working as a team... but the others can eat up time, also. I have #1 going for 1.1.1-SNAPSHOT and 1.2-SNAPSHOT. Hope to get #2 going later today... Now, would be a great time for getting more people involved... --kevan
Re: TCK Dog -- monitoring results
I have been remiss in my TCK duties. I'll reset my TCK e-mail and watch for JIRAs. David Blevins wrote: On Jul 10, 2006, at 11:19 AM, Kevan Miller wrote: On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. [...] I see the following pieces: 3) Monitoring/advertising test results. You have any ideas on what we can do raise awareness of what is going on with our tck status, or track what's not being worked on? Hey all you committers, any suggestions? Do you actually peek at the results on a regular basis? If not, do you have any suggestions on what would be the best way to communicate TCK status? -David
Re: TCK Dog -- monitoring results
On Jul 10, 2006, at 3:38 PM, David Blevins wrote: On Jul 10, 2006, at 11:19 AM, Kevan Miller wrote: On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. [...] I see the following pieces: 3) Monitoring/advertising test results. You have any ideas on what we can do raise awareness of what is going on with our tck status, or track what's not being worked on? Some sort of jira reporting system (as Alan mentioned) would be useful for tracking problems. The GBuild summary reports certainly help out a lot. Biggest problem is probably getting from the report to having enough data to start categorizing/diagnosing the problem. --kevan Hey all you committers, any suggestions? Do you actually peek at the results on a regular basis? If not, do you have any suggestions on what would be the best way to communicate TCK status? -David
Re: TCK Dog
On Jul 10, 2006, at 3:33 PM, Alan D. Cabrera wrote: Kevan Miller wrote: On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. What do you think? I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. So, it's not one dog, but several... Although I certainly had a lot of help from you, David J, and Dain, It'd be great to see a broader base of participation... I see the following pieces: 1) Keeping builds running through Continuum 2) Keeping tests running through GBuild 3) Monitoring/advertising test results. 4) Fixing problems It's #4 that can be the killer and where we should be working as a team... but the others can eat up time, also. I have #1 going for 1.1.1-SNAPSHOT and 1.2-SNAPSHOT. Hope to get #2 going later today... Now, would be a great time for getting more people involved... We have a special Jira project for #4, no? Not that this solves the problem but, I was just wondering. No, not that I'm aware of. I thought there were issues getting a Jira set up with necessary permissions. Would be really nice, though... I've just been using our tck mailing list for this... --kevan
Re: TCK Dog -- monitoring results
On Jul 10, 2006, at 11:19 AM, Kevan Miller wrote: On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. [...] I see the following pieces: 3) Monitoring/advertising test results. You have any ideas on what we can do raise awareness of what is going on with our tck status, or track what's not being worked on? Hey all you committers, any suggestions? Do you actually peek at the results on a regular basis? If not, do you have any suggestions on what would be the best way to communicate TCK status? -David
Re: TCK Dog
Kevan Miller wrote: On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. What do you think? I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. So, it's not one dog, but several... Although I certainly had a lot of help from you, David J, and Dain, It'd be great to see a broader base of participation... I see the following pieces: 1) Keeping builds running through Continuum 2) Keeping tests running through GBuild 3) Monitoring/advertising test results. 4) Fixing problems It's #4 that can be the killer and where we should be working as a team... but the others can eat up time, also. I have #1 going for 1.1.1-SNAPSHOT and 1.2-SNAPSHOT. Hope to get #2 going later today... Now, would be a great time for getting more people involved... We have a special Jira project for #4, no? Not that this solves the problem but, I was just wondering. Regards, Alan
Re: TCK Dog
On Jul 10, 2006, at 1:55 PM, David Blevins wrote: Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. What do you think? I certainly agree with that... I would also hope that we can work on distributing the burden, a bit. So, it's not one dog, but several... Although I certainly had a lot of help from you, David J, and Dain, It'd be great to see a broader base of participation... I see the following pieces: 1) Keeping builds running through Continuum 2) Keeping tests running through GBuild 3) Monitoring/advertising test results. 4) Fixing problems It's #4 that can be the killer and where we should be working as a team... but the others can eat up time, also. I have #1 going for 1.1.1-SNAPSHOT and 1.2-SNAPSHOT. Hope to get #2 going later today... Now, would be a great time for getting more people involved... --kevan
TCK Dog
Kevan, you've been tck dog for six months now. Having built the system and done the job myself, I know you're not going to survive another six months. We definitely need to get someone else to take that job for a while. What do you think? -David
