You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Prescott Nasser (JIRA)" <ji...@apache.org> on 2014/11/20 19:18:34 UTC
[jira] [Updated] (INFRA-8664) Improved Git Integration with Apache
for Lucene.Net
[ https://issues.apache.org/jira/browse/INFRA-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prescott Nasser updated INFRA-8664:
-----------------------------------
Summary: Improved Git Integration with Apache for Lucene.Net (was: Improved Git Integration with Apache)
> Improved Git Integration with Apache for Lucene.Net
> ---------------------------------------------------
>
> Key: INFRA-8664
> URL: https://issues.apache.org/jira/browse/INFRA-8664
> Project: Infrastructure
> Issue Type: Wish
> Components: Git
> Reporter: Prescott Nasser
> Priority: Minor
>
> We just found: https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
> We're requesting the following features:
> Apache Infrastructure Team
> « paste.apache.org... | Main | Scaling down the CMS... »
> WEDNESDAY FEB 12, 2014
> Improved integration between Apache and GitHub
> After a few weeks of hard work and mind-boggling debugging, we are pleased to announce tighter and smarter integration between GitHub and the Apache Software Foundation's infrastructure.
> These new features mean a much higher level of replication and retention of what goes on on GitHub, which in turns both help projects maintain control over what goes on within their project, as well as keeping a record of everything that's happening in the development of a project, whether it be on ASF hardware or off-site on GitHub.
> To be more precise, these new features allows for the following:
> - Any Pull Request that gets opened, closed, reopened or commented on now gets recorded on the project's mailing list
> - If a project has a JIRA instance, any PRs or comments on PRs that include a JIRA ticket ID will trigger an update on that specific ticket
> - Replying to a GitHub comment on the dev@ mailing list will trigger a comment being placed on GitHub (yes, it works both ways!)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)