infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <>
Subject [jira] [Resolved] (INFRA-17048) Split Ambari repos on apache: ambari, ambari-infra, ambari-metrics, ambari-logsearch
Date Fri, 21 Sep 2018 19:52:00 GMT


Greg Stein resolved INFRA-17048.
    Resolution: Invalid

This is not an Infrastructure task.

Create your new repositories with:

Then perform the appropriate version control actions. Only the Apache Ambari team can review
that it was done properly, according to your desires.

There are no special actions that require Infra attention on this matter. Should you run into
something, then let us know.

(personal commentary: release workflow does not require multiple repositories, and I don't
understand why you think that would be necessary; you're only making things more complicated
by switching to multiple repositories)

> Split Ambari repos on apache: ambari, ambari-infra, ambari-metrics, ambari-logsearch
> ------------------------------------------------------------------------------------
>                 Key: INFRA-17048
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Git, GitBox, Github
>            Reporter: Jayush Luniya
>            Priority: Critical
> The Apache Ambari community voted to break down the ambari git repo into multiple repos
in order to decouple the build and release cycles of ambari (i.e. ambari core), ambari-infra,
ambari-metrics and ambari-logsearch. We want to split the ambari-infra, ambari-metrics and
ambari-logsearch sub-folders in ambari git repo into its individual git repos. 
> VOTE thread:
> Can we follow the guidelines below to ensure that the commit history is maintained after
the split.
> Steps on github: (do that with ambari-infra, ambari-metrics, ambari-logsearch)
> (it is important to keep the commit history, also it's enough to have a master branch
for every repo at start, i can figure it out how to extend the release process with these

This message was sent by Atlassian JIRA

View raw message