infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-15676) GitBox for kafka and kafka-site
Date Sat, 23 Dec 2017 08:52:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ismael Juma updated INFRA-15676:
--------------------------------
    Status: Waiting for Infra  (was: Waiting for user)

[~pono], that sounds great. Unfortunately it doesn't seem to have worked. I just closed a
PR without merging it and the diff was posted as a comment:

https://issues.apache.org/jira/browse/KAFKA-6141?focusedCommentId=16302283&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16302283

> GitBox for kafka and kafka-site
> -------------------------------
>
>                 Key: INFRA-15676
>                 URL: https://issues.apache.org/jira/browse/INFRA-15676
>             Project: Infrastructure
>          Issue Type: GitBox Request
>          Components: GitBox
>            Reporter: Ismael Juma
>            Assignee: Daniel Takamori
>
> The Apache Kafka project would like to enable GitBox for the kafka and kafka-site Git
repositories.
> The successful vote can be found in the following mailing list thread:
> https://lists.apache.org/thread.html/3ef19c439e978993d1e40f0f30cc0126e79761b7b8910400fb7f18bb@%3Cdev.kafka.apache.org%3E
> Is it correct that for changes that require Admin access (like setting protected branches
and configuring the allowed merge options), we would still need Infra help?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message