You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Suresh Marru <sm...@apache.org> on 2019/03/21 05:23:57 UTC

Removing Stale Branches 

Hi All,

There are quite a few branches in airavata main repo which seems to be definitely not relevant anymore. If we are absolutely sure about them, can we remove them? 

  origin/AIRAVATA-2500 - This one is merged into master, remove? 
  origin/AIRAVATA-2517-keycloak-mysql-connections - remove?
  origin/AIRAVATA-2620 - remove? 
  origin/BuildRTWithoutModel - Keep for now
  origin/airavata-0.15-release-branch - remove?
  origin/airavata-2938-change-db-initialization-in-registry-server-to-use-registry-refactoring-code - remove?
  origin/airavata-docker - keep 
  origin/airavata-gov-registry - keep 
  origin/archive - keep 
  origin/auroraMesosIntegration - keep 
  origin/cluster-monitoring - keep 
  origin/data-manager - keep 
  origin/data-model-pre-1.0-discussion - keep
  origin/deprecated-gfac-modules - keep 
  origin/develop - keep
  origin/file-management.- keep
  origin/gfac-storm - keep
  origin/git-app-catalog - keep
  origin/group-based-auth - remove since it is merged?
  origin/grouper-integration - keep
  origin/helix-integration - remove since it is merged? 
  origin/hotfix-AIRAVATA-2096 - remove?
  origin/jupyter-integration - keep
  origin/lahiru/AIRAVATA-2017 - remove?
  origin/lahiru/AIRAVATA-2065 - remove?
  origin/lahiru/AIRAVATA-2107 - remove?
  origin/lahiru/airavata-docker - keep
  origin/master - keep
  origin/master-staging-merge - keep 
  origin/mongo-registry - keep 
  origin/new-workflow-design - keep 
  origin/nextcloud - keep 
  origin/orchestratorTaskBreakdown - keep
  origin/queue-gfac - remove?
  origin/queue-gfac-rabbitmq - remove?
  origin/registry-refactoring - remove since it is merged?
  origin/revert-203-develop - remove
  origin/shameera/build-fix - remove?
  origin/staging - keep
  origin/staging-temp - remove?
  origin/thrift-0.10.0-upgrade - remove?
  origin/user-profile - remove since it is merged?
  origin/workflow-support - keep for now

Thoughts?
Suresh

Re: Removing Stale Branches

Posted by DImuthu Upeksha <di...@gmail.com>.
+1

On Thu, Mar 21, 2019 at 1:24 AM Suresh Marru <sm...@apache.org> wrote:

> Hi All,
>
> There are quite a few branches in airavata main repo which seems to be
> definitely not relevant anymore. If we are absolutely sure about them, can
> we remove them?
>
>   origin/AIRAVATA-2500 - This one is merged into master, remove?
>   origin/AIRAVATA-2517-keycloak-mysql-connections - remove?
>   origin/AIRAVATA-2620 - remove?
>   origin/BuildRTWithoutModel - Keep for now
>   origin/airavata-0.15-release-branch - remove?
>
> origin/airavata-2938-change-db-initialization-in-registry-server-to-use-registry-refactoring-code
> - remove?
>   origin/airavata-docker - keep
>   origin/airavata-gov-registry - keep
>   origin/archive - keep
>   origin/auroraMesosIntegration - keep
>   origin/cluster-monitoring - keep
>   origin/data-manager - keep
>   origin/data-model-pre-1.0-discussion - keep
>   origin/deprecated-gfac-modules - keep
>   origin/develop - keep
>   origin/file-management.- keep
>   origin/gfac-storm - keep
>   origin/git-app-catalog - keep
>   origin/group-based-auth - remove since it is merged?
>   origin/grouper-integration - keep
>   origin/helix-integration - remove since it is merged?
>   origin/hotfix-AIRAVATA-2096 - remove?
>   origin/jupyter-integration - keep
>   origin/lahiru/AIRAVATA-2017 - remove?
>   origin/lahiru/AIRAVATA-2065 - remove?
>   origin/lahiru/AIRAVATA-2107 - remove?
>   origin/lahiru/airavata-docker - keep
>   origin/master - keep
>   origin/master-staging-merge - keep
>   origin/mongo-registry - keep
>   origin/new-workflow-design - keep
>   origin/nextcloud - keep
>   origin/orchestratorTaskBreakdown - keep
>   origin/queue-gfac - remove?
>   origin/queue-gfac-rabbitmq - remove?
>   origin/registry-refactoring - remove since it is merged?
>   origin/revert-203-develop - remove
>   origin/shameera/build-fix - remove?
>   origin/staging - keep
>   origin/staging-temp - remove?
>   origin/thrift-0.10.0-upgrade - remove?
>   origin/user-profile - remove since it is merged?
>   origin/workflow-support - keep for now
>
> Thoughts?
> Suresh

Re: Removing Stale Branches

Posted by Suresh Marru <sm...@apache.org>.
Thanks Dimuthu, Marcus for reviewing. I removed the ones which were marked remove below. 

Suresh

> On Mar 22, 2019, at 9:20 AM, Christie, Marcus Aaron <ma...@iu.edu> wrote:
> 
> +1
> 
> I don't see any that you've marked with remove that need to be kept.
> 
>> On Mar 21, 2019, at 1:23 AM, Suresh Marru <sm...@apache.org> wrote:
>> 
>> Hi All,
>> 
>> There are quite a few branches in airavata main repo which seems to be definitely not relevant anymore. If we are absolutely sure about them, can we remove them? 
>> 
>> origin/AIRAVATA-2500 - This one is merged into master, remove? 
>> origin/AIRAVATA-2517-keycloak-mysql-connections - remove?
>> origin/AIRAVATA-2620 - remove? 
>> origin/BuildRTWithoutModel - Keep for now
>> origin/airavata-0.15-release-branch - remove?
>> origin/airavata-2938-change-db-initialization-in-registry-server-to-use-registry-refactoring-code - remove?
>> origin/airavata-docker - keep 
>> origin/airavata-gov-registry - keep 
>> origin/archive - keep 
>> origin/auroraMesosIntegration - keep 
>> origin/cluster-monitoring - keep 
>> origin/data-manager - keep 
>> origin/data-model-pre-1.0-discussion - keep
>> origin/deprecated-gfac-modules - keep 
>> origin/develop - keep
>> origin/file-management.- keep
>> origin/gfac-storm - keep
>> origin/git-app-catalog - keep
>> origin/group-based-auth - remove since it is merged?
>> origin/grouper-integration - keep
>> origin/helix-integration - remove since it is merged? 
>> origin/hotfix-AIRAVATA-2096 - remove?
>> origin/jupyter-integration - keep
>> origin/lahiru/AIRAVATA-2017 - remove?
>> origin/lahiru/AIRAVATA-2065 - remove?
>> origin/lahiru/AIRAVATA-2107 - remove?
>> origin/lahiru/airavata-docker - keep
>> origin/master - keep
>> origin/master-staging-merge - keep 
>> origin/mongo-registry - keep 
>> origin/new-workflow-design - keep 
>> origin/nextcloud - keep 
>> origin/orchestratorTaskBreakdown - keep
>> origin/queue-gfac - remove?
>> origin/queue-gfac-rabbitmq - remove?
>> origin/registry-refactoring - remove since it is merged?
>> origin/revert-203-develop - remove
>> origin/shameera/build-fix - remove?
>> origin/staging - keep
>> origin/staging-temp - remove?
>> origin/thrift-0.10.0-upgrade - remove?
>> origin/user-profile - remove since it is merged?
>> origin/workflow-support - keep for now
>> 
>> Thoughts?
>> Suresh
>

Re: Removing Stale Branches

Posted by "Christie, Marcus Aaron" <ma...@iu.edu>.
+1

I don't see any that you've marked with remove that need to be kept.

> On Mar 21, 2019, at 1:23 AM, Suresh Marru <sm...@apache.org> wrote:
> 
> Hi All,
> 
> There are quite a few branches in airavata main repo which seems to be definitely not relevant anymore. If we are absolutely sure about them, can we remove them? 
> 
>  origin/AIRAVATA-2500 - This one is merged into master, remove? 
>  origin/AIRAVATA-2517-keycloak-mysql-connections - remove?
>  origin/AIRAVATA-2620 - remove? 
>  origin/BuildRTWithoutModel - Keep for now
>  origin/airavata-0.15-release-branch - remove?
>  origin/airavata-2938-change-db-initialization-in-registry-server-to-use-registry-refactoring-code - remove?
>  origin/airavata-docker - keep 
>  origin/airavata-gov-registry - keep 
>  origin/archive - keep 
>  origin/auroraMesosIntegration - keep 
>  origin/cluster-monitoring - keep 
>  origin/data-manager - keep 
>  origin/data-model-pre-1.0-discussion - keep
>  origin/deprecated-gfac-modules - keep 
>  origin/develop - keep
>  origin/file-management.- keep
>  origin/gfac-storm - keep
>  origin/git-app-catalog - keep
>  origin/group-based-auth - remove since it is merged?
>  origin/grouper-integration - keep
>  origin/helix-integration - remove since it is merged? 
>  origin/hotfix-AIRAVATA-2096 - remove?
>  origin/jupyter-integration - keep
>  origin/lahiru/AIRAVATA-2017 - remove?
>  origin/lahiru/AIRAVATA-2065 - remove?
>  origin/lahiru/AIRAVATA-2107 - remove?
>  origin/lahiru/airavata-docker - keep
>  origin/master - keep
>  origin/master-staging-merge - keep 
>  origin/mongo-registry - keep 
>  origin/new-workflow-design - keep 
>  origin/nextcloud - keep 
>  origin/orchestratorTaskBreakdown - keep
>  origin/queue-gfac - remove?
>  origin/queue-gfac-rabbitmq - remove?
>  origin/registry-refactoring - remove since it is merged?
>  origin/revert-203-develop - remove
>  origin/shameera/build-fix - remove?
>  origin/staging - keep
>  origin/staging-temp - remove?
>  origin/thrift-0.10.0-upgrade - remove?
>  origin/user-profile - remove since it is merged?
>  origin/workflow-support - keep for now
> 
> Thoughts?
> Suresh