infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Navina Ramesh (JIRA)" <>
Subject [jira] [Commented] (INFRA-14660) How to create a related sub-repo for the project?
Date Thu, 20 Jul 2017 18:27:00 GMT


Navina Ramesh commented on INFRA-14660:


> How to create a related sub-repo for the project?
> -------------------------------------------------
>                 Key: INFRA-14660
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Github
>            Reporter: Navina Ramesh
> Hi Infra team,
> Apache Samza wants to create a separate sub-repo for maintaining its pluggable components.
Is it possible to do so? 
> This will help us in the following manner:
> 1. The main repository/project remains free from rarely used dependencies. This simplifies
source-code management for the committers. For example, most users may directly depend on
the core artifacts and not use the pluggable modules.
> 2. De-couples the samza project release cycle from the components' release cycle. A lot
of our users may want to upgrade a components' version, for example, azure-api , elastic-search
libraries etc. These are directly used by the pluggable components, and not the main project.
Today, a request to upgrade a dependency version means that we have to re-publish or re-release
the entire project artifact. This is very heavy-weight and slows down our release cadence
of components.
> Please let us know if it is possible to create project-related sub-repos. Happy to follow-up
with any questions you may have. 
> Thanks!
> Navina
> Apache Samza, PMC

This message was sent by Atlassian JIRA

View raw message