You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Joe Bohn <jo...@earthlink.net> on 2008/02/20 18:01:37 UTC
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
Posted by Joe Bohn <jo...@earthlink.net>.
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
Posted by Paul McMahan <pa...@gmail.com>.
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
Posted by Matt Hogstrom <ma...@hogstrom.org>.
/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
> <ke...@gmail.com> 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
Posted by Prasad Kashyap <go...@gmail.com>.
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 <ke...@gmail.com> 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
Posted by Kevan Miller <ke...@gmail.com>.
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
Posted by "Jay D. McHugh" <ja...@gmail.com>.
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
>
>