infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-19015) Limit the length and segment count of Git repo names?
Date Wed, 11 Sep 2019 22:30:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-19015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928052#comment-16928052
] 

Chris Lambertus edited comment on INFRA-19015 at 9/11/19 10:29 PM:
-------------------------------------------------------------------

We weren’t thrilled with that particular naming scheme either, but as long as the project
name is the first in the pattern, Infra doesn’t really care what projects name their repos,
and see no reason to artificially limit it unless there is an explicit problem. You’re welcome
to discuss Sling’s naming with Sling.



was (Author: cml):
We weren’t thrilled with that particular naming scheme either, but as long as the project
name is the first in the pattern, Infra doesn’t really care what projects we name their
repos, and see no reason to artificially limit it unless there is an explicit problem. You’re
welcome to discuss Sling’s naming with Sling.


> Limit the length and segment count of Git repo names?
> -----------------------------------------------------
>
>                 Key: INFRA-19015
>                 URL: https://issues.apache.org/jira/browse/INFRA-19015
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Selfserve
>            Reporter: Sebb
>            Priority: Major
>
> Perhaps the repo name should be validated for length and segment count.
> e.g. sling-org-apache-sling-bnd-plugin-headers-parameters-remove.git
> seems excessively long. At the very least the org-apache-sling part is not needed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message