infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-16026) ignite-release repository on github
Date Thu, 15 Feb 2018 01:48:00 GMT

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

Greg Stein resolved INFRA-16026.
--------------------------------
    Resolution: Fixed  (was: Won't Fix)

Sounds great. I'll go ahead and close the issue. I suspect the rest will go just fine, but
we'll keep an eye on it.

And a hat-tip to [~cml] for the underlying TLS negotiation fix.


> ignite-release repository on github
> -----------------------------------
>
>                 Key: INFRA-16026
>                 URL: https://issues.apache.org/jira/browse/INFRA-16026
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>            Reporter: Anton Vinogradov
>            Assignee: Daniel Gruno
>            Priority: Major
>         Attachments: Screen Shot 2018-02-14 at 1.15.22 PM.png
>
>
> Is it possible to create repository "ignite-release" on github? 
> It can be simply forked from my repo 
> https://github.com/anton-vinogradov/apache-ignite-release
> My repo is used now to assembly Apache Ignite at Ignite's TeamCity Release Project:
> https://ci.ignite.apache.org/project.html?projectId=ApacheIgniteReleaseJava8
> and I'd like to allow Ignite's commiters to push changes without asking me to merge.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message