infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <>
Subject [jira] [Commented] (INFRA-15859) branch-3 should be deleted in the Hadoop git repo
Date Wed, 21 Feb 2018 18:36:00 GMT


Jason Lowe commented on INFRA-15859:

branch-3.0 is tracking 3.0.x releases, so it doesn't make sense to rename it to branch-3.
 trunk is really branch-3 at this point, but I don't think we want to try renaming trunk at
this point.

Putting a pre-push trigger in place that precludes creating a branch-3 makes sense until we
actually need a branch-3 (which is probably not for quite a while).  I'm assuming someone
from infra needs to do that as well.  I'm unclear on how much control we have over the triggers
on our repo.

> branch-3 should be deleted in the Hadoop git repo
> -------------------------------------------------
>                 Key: INFRA-15859
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            Reporter: Jason Lowe
>            Assignee: Chris Thistlethwaite
>            Priority: Major
> Recently a committer accidentally created a "branch-3" branch in the Hadoop repository,  This is causing a lot of confusion since there
is already a "branch-3.0" branch, and some committers are committing their code that should
be on branch-3.0 into branch-3.
> We would like branch-3 to be deleted so the confusion and mis-commits are reduced.  I
am assuming there is a push hook that prevents committers from doing this directly (if not
there probably should be one), hence the INFRA request.

This message was sent by Atlassian JIRA

View raw message