[RT] Aligning Jira components with our git repos?

[Carsten Ziegeler <cz...@apache.org>]

Hi,

for the most important modules (git repos) we have a separate component 
in jira, like api, engine etc.
But that is not consistent.

I suggest we make an effort to align those, every git repo getting a 
separate component, removing components which are not based on a git repo.

This would make issue handling easier, especially when 
triaging/evaluation issues.

WDYT?

Carsten
-- 
Carsten Ziegeler
Adobe
cziegeler@apache.org

RE: [RT] Aligning Jira components with our git repos?

[Stefan Seifert via dev <de...@sling.apache.org>]

i agree the current list of sling components in JIRA is very outdated and incomplete - and thus mostly not used.

on the other hand, using any single git repo name as component name will completely bloat this list, and probably make it unusable.

ideally, we come up with a component list with each "related group of repos", e.g. one for all models-related repos, caconfig related repos etc. but this also comes with a downside - that list needs to be hand-curated, and maybe the its not obvious for everyone which repo belongs to which component.

so, also considering that it can be automated, a component for each git repo might be a suitable compromise.

stefan

> -----Original Message-----
> From: Carsten Ziegeler <cz...@apache.org>
> Sent: Tuesday, September 29, 2026 1:51 PM
> To: dev@sling.apache.org
> Subject: [RT] Aligning Jira components with our git repos?
> 
> Hi,
> 
> for the most important modules (git repos) we have a separate component
> in jira, like api, engine etc.
> But that is not consistent.
> 
> I suggest we make an effort to align those, every git repo getting a
> separate component, removing components which are not based on a git repo.
> 
> This would make issue handling easier, especially when
> triaging/evaluation issues.
> 
> WDYT?
> 
> Carsten
> --
> Carsten Ziegeler
> Adobe
> cziegeler@apache.org

Re: [RT] Aligning Jira components with our git repos?

[Robert Munteanu <ro...@apache.org>]

On Wed, 2026-09-30 at 07:34 +0200, Carsten Ziegeler wrote:
> Some use the version field, some the components field, some do not
> care, 
> some use both.
> 
> Nothing is ideal - we discussed this yesterday at the Sling Community
> Roundtable at adaptTo and there are some interesting alternative 
> proposals, so stay tuned for a new discussion around that topic
> coming 
> up soon.

I am also in the camp of using 'Affects Version' and 'Fix Version' pin
a Jira issue to a specific component.

I think the component/fix version model works if we have a Sling
'Product' with individual releases and multiple sub-components, like
Jackrabbit does. Managing/requiring components on top of fix versions
seems redundant and even opens up the possibility to have mismatches
between versions and components :-)

If we decide to go down this route we can probably script the component
creation; we don't create git repositories all that often so keeping
the list up-to-date will not be too much effort.

Thanks,
Robert

Re: [RT] Aligning Jira components with our git repos?

[Carsten Ziegeler <cz...@apache.org>]

Some use the version field, some the components field, some do not care, 
some use both.

Nothing is ideal - we discussed this yesterday at the Sling Community 
Roundtable at adaptTo and there are some interesting alternative 
proposals, so stay tuned for a new discussion around that topic coming 
up soon.

Regards
Carsten

On 9/29/2026 3:17 PM, Jörg Hoh via dev wrote:
> I wonder if anyone of us is really using the Jira components.
> 
> I personally mostly rely on the "affected version" field to understand
> which codebase needs to be looked at. Do we have automation/processes which
> would benefit from such an effort?
> 
> Jörg
> 
> Am Di., 29. Sept. 2026 um 13:51 Uhr schrieb Carsten Ziegeler <
> cziegeler@apache.org>:
> 
>> Hi,
>>
>> for the most important modules (git repos) we have a separate component
>> in jira, like api, engine etc.
>> But that is not consistent.
>>
>> I suggest we make an effort to align those, every git repo getting a
>> separate component, removing components which are not based on a git repo.
>>
>> This would make issue handling easier, especially when
>> triaging/evaluation issues.
>>
>> WDYT?
>>
>> Carsten
>> --
>> Carsten Ziegeler
>> Adobe
>> cziegeler@apache.org
>>
>>
> 

-- 
Carsten Ziegeler
Adobe
cziegeler@apache.org

Re: [RT] Aligning Jira components with our git repos?

[Jörg Hoh via dev <de...@sling.apache.org>]

I wonder if anyone of us is really using the Jira components.

I personally mostly rely on the "affected version" field to understand
which codebase needs to be looked at. Do we have automation/processes which
would benefit from such an effort?

Jörg

Am Di., 29. Sept. 2026 um 13:51 Uhr schrieb Carsten Ziegeler <
cziegeler@apache.org>:

> Hi,
>
> for the most important modules (git repos) we have a separate component
> in jira, like api, engine etc.
> But that is not consistent.
>
> I suggest we make an effort to align those, every git repo getting a
> separate component, removing components which are not based on a git repo.
>
> This would make issue handling easier, especially when
> triaging/evaluation issues.
>
> WDYT?
>
> Carsten
> --
> Carsten Ziegeler
> Adobe
> cziegeler@apache.org
>
>

-- 
https://cqdump.joerghoh.de