You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kato-dev@incubator.apache.org by Carmine Cristallo <ca...@gmail.com> on 2009/03/09 11:03:24 UTC
JIRA components!
Hi all!
Here's the list of the components to be created on Jira.
- TCK (for the Test Compliance Toolkit)
- API (for the API specification)
- RI (for the Reference Implementation)
- HARNESS (for the test harness)
- NMAT (for the Native Memory Analysis Tool)
- RTEX (for the RunTime Explorer)
- PROCEX (for the Process Explorer)
- RTI (for the RunTime Investigator)
- JDICONN (for the JDI Connector).
I've created a JIRA task for this item. Ant/Robert... was this the
right thing to do?
Thank you!
Carmine
Carmine
On Tue, Mar 3, 2009 at 3:37 PM, Carmine Cristallo
<ca...@gmail.com> wrote:
> Hello!
> I'm starting to think about what the component structure will look
> like. In one of his previous postings, Steve suggested the following:
>
>> Create components in the Kato Jira instance. We have the following obvious areas - is this a reasonable split?
>> - Test Compliance Kit. Items under this component would cover TCK development and issues arrising about execution validity.
>> - API specification - items here would cover user story creation, bugs in the spec and spec development
>> - Reference Implementation (nuf said)
>> - Test Harness. The TCK is only one part of the test suite. What we are developing needs a complex test setup and execution environment - its big enough to need its own component
>
> I would also suggest one component for each of the demo tools we will
> create, although these may be created at a later stage, since the
> tools boundaries are still far from being definite.
>
> What do you think? I would like to call a vote on this list on Friday,
> so please post your comments before then.
>
> Thank you!
>
>
>
> Carmine
>
Re: JIRA components!
Posted by ant elder <an...@gmail.com>.
I've update JIRA so that all kato developers have admin rights to the kato
project so you can do these types of things yourselves. Logon to JIRA and go
to the kato jira project home page and around the middle of the page you
should now see the new "Administer Project" option. Right now the
kato-developers group is the mentors, ccristal, and sgoyal, if others of you
have jira id's contact one of those to get your id added to the
kato-developers group.
...ant
On Thu, Mar 12, 2009 at 5:03 PM, Carmine Cristallo <
carminecristallo@gmail.com> wrote:
> I've created task INFRA-1938 for both the components and the versions:
> https://issues.apache.org/jira/browse/INFRA-1938
>
> Carmine
>
> On Thu, Mar 12, 2009 at 4:56 PM, Carmine Cristallo
> <ca...@gmail.com> wrote:
> > Hmmm... that must be why... ;-)
> >
> > Carmine
> >
> > On Thu, Mar 12, 2009 at 4:54 PM, Steve Poole <sp...@googlemail.com>
> wrote:
> >> Shouldn't this request go on the infrastructure project rather than the
> >> Kato one?
> >>
> >>
> >> On Thu, Mar 12, 2009 at 11:29 AM, Carmine Cristallo <
> >> carminecristallo@gmail.com> wrote:
> >>
> >>> Robert, Ant,
> >>> I created a JIRA issue about the creation of the components for Kato a
> >>> few days ago (see https://issues.apache.org/jira/browse/KATO-1 ). Is
> >>> there any further step I need to take to have the components created
> >>> on JIRA?
> >>> Thank you!
> >>>
> >>> Carmine
> >>>
> >>> On Mon, Mar 9, 2009 at 11:03 AM, Carmine Cristallo
> >>> <ca...@gmail.com> wrote:
> >>> > Hi all!
> >>> > Here's the list of the components to be created on Jira.
> >>> >
> >>> > - TCK (for the Test Compliance Toolkit)
> >>> > - API (for the API specification)
> >>> > - RI (for the Reference Implementation)
> >>> > - HARNESS (for the test harness)
> >>> > - NMAT (for the Native Memory Analysis Tool)
> >>> > - RTEX (for the RunTime Explorer)
> >>> > - PROCEX (for the Process Explorer)
> >>> > - RTI (for the RunTime Investigator)
> >>> > - JDICONN (for the JDI Connector).
> >>> >
> >>> > I've created a JIRA task for this item. Ant/Robert... was this the
> >>> > right thing to do?
> >>> > Thank you!
> >>> >
> >>> > Carmine
> >>> >
> >>> >
> >>> > Carmine
> >>> >
> >>> >
> >>> > On Tue, Mar 3, 2009 at 3:37 PM, Carmine Cristallo
> >>> > <ca...@gmail.com> wrote:
> >>> >> Hello!
> >>> >> I'm starting to think about what the component structure will look
> >>> >> like. In one of his previous postings, Steve suggested the
> following:
> >>> >>
> >>> >>> Create components in the Kato Jira instance. We have the following
> >>> obvious areas - is this a reasonable split?
> >>> >>> - Test Compliance Kit. Items under this component would cover TCK
> >>> development and issues arrising about execution validity.
> >>> >>> - API specification - items here would cover user story creation,
> bugs
> >>> in the spec and spec development
> >>> >>> - Reference Implementation (nuf said)
> >>> >>> - Test Harness. The TCK is only one part of the test suite. What we
> are
> >>> developing needs a complex test setup and execution environment - its
> big
> >>> enough to need its own component
> >>> >>
> >>> >> I would also suggest one component for each of the demo tools we
> will
> >>> >> create, although these may be created at a later stage, since the
> >>> >> tools boundaries are still far from being definite.
> >>> >>
> >>> >> What do you think? I would like to call a vote on this list on
> Friday,
> >>> >> so please post your comments before then.
> >>> >>
> >>> >> Thank you!
> >>> >>
> >>> >>
> >>> >>
> >>> >> Carmine
> >>> >>
> >>> >
> >>>
> >>
> >
>
Re: JIRA components!
Posted by Carmine Cristallo <ca...@gmail.com>.
I've created task INFRA-1938 for both the components and the versions:
https://issues.apache.org/jira/browse/INFRA-1938
Carmine
On Thu, Mar 12, 2009 at 4:56 PM, Carmine Cristallo
<ca...@gmail.com> wrote:
> Hmmm... that must be why... ;-)
>
> Carmine
>
> On Thu, Mar 12, 2009 at 4:54 PM, Steve Poole <sp...@googlemail.com> wrote:
>> Shouldn't this request go on the infrastructure project rather than the
>> Kato one?
>>
>>
>> On Thu, Mar 12, 2009 at 11:29 AM, Carmine Cristallo <
>> carminecristallo@gmail.com> wrote:
>>
>>> Robert, Ant,
>>> I created a JIRA issue about the creation of the components for Kato a
>>> few days ago (see https://issues.apache.org/jira/browse/KATO-1 ). Is
>>> there any further step I need to take to have the components created
>>> on JIRA?
>>> Thank you!
>>>
>>> Carmine
>>>
>>> On Mon, Mar 9, 2009 at 11:03 AM, Carmine Cristallo
>>> <ca...@gmail.com> wrote:
>>> > Hi all!
>>> > Here's the list of the components to be created on Jira.
>>> >
>>> > - TCK (for the Test Compliance Toolkit)
>>> > - API (for the API specification)
>>> > - RI (for the Reference Implementation)
>>> > - HARNESS (for the test harness)
>>> > - NMAT (for the Native Memory Analysis Tool)
>>> > - RTEX (for the RunTime Explorer)
>>> > - PROCEX (for the Process Explorer)
>>> > - RTI (for the RunTime Investigator)
>>> > - JDICONN (for the JDI Connector).
>>> >
>>> > I've created a JIRA task for this item. Ant/Robert... was this the
>>> > right thing to do?
>>> > Thank you!
>>> >
>>> > Carmine
>>> >
>>> >
>>> > Carmine
>>> >
>>> >
>>> > On Tue, Mar 3, 2009 at 3:37 PM, Carmine Cristallo
>>> > <ca...@gmail.com> wrote:
>>> >> Hello!
>>> >> I'm starting to think about what the component structure will look
>>> >> like. In one of his previous postings, Steve suggested the following:
>>> >>
>>> >>> Create components in the Kato Jira instance. We have the following
>>> obvious areas - is this a reasonable split?
>>> >>> - Test Compliance Kit. Items under this component would cover TCK
>>> development and issues arrising about execution validity.
>>> >>> - API specification - items here would cover user story creation, bugs
>>> in the spec and spec development
>>> >>> - Reference Implementation (nuf said)
>>> >>> - Test Harness. The TCK is only one part of the test suite. What we are
>>> developing needs a complex test setup and execution environment - its big
>>> enough to need its own component
>>> >>
>>> >> I would also suggest one component for each of the demo tools we will
>>> >> create, although these may be created at a later stage, since the
>>> >> tools boundaries are still far from being definite.
>>> >>
>>> >> What do you think? I would like to call a vote on this list on Friday,
>>> >> so please post your comments before then.
>>> >>
>>> >> Thank you!
>>> >>
>>> >>
>>> >>
>>> >> Carmine
>>> >>
>>> >
>>>
>>
>
Re: JIRA components!
Posted by Carmine Cristallo <ca...@gmail.com>.
Hmmm... that must be why... ;-)
Carmine
On Thu, Mar 12, 2009 at 4:54 PM, Steve Poole <sp...@googlemail.com> wrote:
> Shouldn't this request go on the infrastructure project rather than the
> Kato one?
>
>
> On Thu, Mar 12, 2009 at 11:29 AM, Carmine Cristallo <
> carminecristallo@gmail.com> wrote:
>
>> Robert, Ant,
>> I created a JIRA issue about the creation of the components for Kato a
>> few days ago (see https://issues.apache.org/jira/browse/KATO-1 ). Is
>> there any further step I need to take to have the components created
>> on JIRA?
>> Thank you!
>>
>> Carmine
>>
>> On Mon, Mar 9, 2009 at 11:03 AM, Carmine Cristallo
>> <ca...@gmail.com> wrote:
>> > Hi all!
>> > Here's the list of the components to be created on Jira.
>> >
>> > - TCK (for the Test Compliance Toolkit)
>> > - API (for the API specification)
>> > - RI (for the Reference Implementation)
>> > - HARNESS (for the test harness)
>> > - NMAT (for the Native Memory Analysis Tool)
>> > - RTEX (for the RunTime Explorer)
>> > - PROCEX (for the Process Explorer)
>> > - RTI (for the RunTime Investigator)
>> > - JDICONN (for the JDI Connector).
>> >
>> > I've created a JIRA task for this item. Ant/Robert... was this the
>> > right thing to do?
>> > Thank you!
>> >
>> > Carmine
>> >
>> >
>> > Carmine
>> >
>> >
>> > On Tue, Mar 3, 2009 at 3:37 PM, Carmine Cristallo
>> > <ca...@gmail.com> wrote:
>> >> Hello!
>> >> I'm starting to think about what the component structure will look
>> >> like. In one of his previous postings, Steve suggested the following:
>> >>
>> >>> Create components in the Kato Jira instance. We have the following
>> obvious areas - is this a reasonable split?
>> >>> - Test Compliance Kit. Items under this component would cover TCK
>> development and issues arrising about execution validity.
>> >>> - API specification - items here would cover user story creation, bugs
>> in the spec and spec development
>> >>> - Reference Implementation (nuf said)
>> >>> - Test Harness. The TCK is only one part of the test suite. What we are
>> developing needs a complex test setup and execution environment - its big
>> enough to need its own component
>> >>
>> >> I would also suggest one component for each of the demo tools we will
>> >> create, although these may be created at a later stage, since the
>> >> tools boundaries are still far from being definite.
>> >>
>> >> What do you think? I would like to call a vote on this list on Friday,
>> >> so please post your comments before then.
>> >>
>> >> Thank you!
>> >>
>> >>
>> >>
>> >> Carmine
>> >>
>> >
>>
>
Re: JIRA components!
Posted by Steve Poole <sp...@googlemail.com>.
Shouldn't this request go on the infrastructure project rather than the
Kato one?
On Thu, Mar 12, 2009 at 11:29 AM, Carmine Cristallo <
carminecristallo@gmail.com> wrote:
> Robert, Ant,
> I created a JIRA issue about the creation of the components for Kato a
> few days ago (see https://issues.apache.org/jira/browse/KATO-1 ). Is
> there any further step I need to take to have the components created
> on JIRA?
> Thank you!
>
> Carmine
>
> On Mon, Mar 9, 2009 at 11:03 AM, Carmine Cristallo
> <ca...@gmail.com> wrote:
> > Hi all!
> > Here's the list of the components to be created on Jira.
> >
> > - TCK (for the Test Compliance Toolkit)
> > - API (for the API specification)
> > - RI (for the Reference Implementation)
> > - HARNESS (for the test harness)
> > - NMAT (for the Native Memory Analysis Tool)
> > - RTEX (for the RunTime Explorer)
> > - PROCEX (for the Process Explorer)
> > - RTI (for the RunTime Investigator)
> > - JDICONN (for the JDI Connector).
> >
> > I've created a JIRA task for this item. Ant/Robert... was this the
> > right thing to do?
> > Thank you!
> >
> > Carmine
> >
> >
> > Carmine
> >
> >
> > On Tue, Mar 3, 2009 at 3:37 PM, Carmine Cristallo
> > <ca...@gmail.com> wrote:
> >> Hello!
> >> I'm starting to think about what the component structure will look
> >> like. In one of his previous postings, Steve suggested the following:
> >>
> >>> Create components in the Kato Jira instance. We have the following
> obvious areas - is this a reasonable split?
> >>> - Test Compliance Kit. Items under this component would cover TCK
> development and issues arrising about execution validity.
> >>> - API specification - items here would cover user story creation, bugs
> in the spec and spec development
> >>> - Reference Implementation (nuf said)
> >>> - Test Harness. The TCK is only one part of the test suite. What we are
> developing needs a complex test setup and execution environment - its big
> enough to need its own component
> >>
> >> I would also suggest one component for each of the demo tools we will
> >> create, although these may be created at a later stage, since the
> >> tools boundaries are still far from being definite.
> >>
> >> What do you think? I would like to call a vote on this list on Friday,
> >> so please post your comments before then.
> >>
> >> Thank you!
> >>
> >>
> >>
> >> Carmine
> >>
> >
>
Re: JIRA components!
Posted by Carmine Cristallo <ca...@gmail.com>.
Robert, Ant,
I created a JIRA issue about the creation of the components for Kato a
few days ago (see https://issues.apache.org/jira/browse/KATO-1 ). Is
there any further step I need to take to have the components created
on JIRA?
Thank you!
Carmine
On Mon, Mar 9, 2009 at 11:03 AM, Carmine Cristallo
<ca...@gmail.com> wrote:
> Hi all!
> Here's the list of the components to be created on Jira.
>
> - TCK (for the Test Compliance Toolkit)
> - API (for the API specification)
> - RI (for the Reference Implementation)
> - HARNESS (for the test harness)
> - NMAT (for the Native Memory Analysis Tool)
> - RTEX (for the RunTime Explorer)
> - PROCEX (for the Process Explorer)
> - RTI (for the RunTime Investigator)
> - JDICONN (for the JDI Connector).
>
> I've created a JIRA task for this item. Ant/Robert... was this the
> right thing to do?
> Thank you!
>
> Carmine
>
>
> Carmine
>
>
> On Tue, Mar 3, 2009 at 3:37 PM, Carmine Cristallo
> <ca...@gmail.com> wrote:
>> Hello!
>> I'm starting to think about what the component structure will look
>> like. In one of his previous postings, Steve suggested the following:
>>
>>> Create components in the Kato Jira instance. We have the following obvious areas - is this a reasonable split?
>>> - Test Compliance Kit. Items under this component would cover TCK development and issues arrising about execution validity.
>>> - API specification - items here would cover user story creation, bugs in the spec and spec development
>>> - Reference Implementation (nuf said)
>>> - Test Harness. The TCK is only one part of the test suite. What we are developing needs a complex test setup and execution environment - its big enough to need its own component
>>
>> I would also suggest one component for each of the demo tools we will
>> create, although these may be created at a later stage, since the
>> tools boundaries are still far from being definite.
>>
>> What do you think? I would like to call a vote on this list on Friday,
>> so please post your comments before then.
>>
>> Thank you!
>>
>>
>>
>> Carmine
>>
>