Alfresco Search Services Git Repositories Infrastructure
Alfresco Search Team is using an internal Git Repository for development purposes. This repository is only accesible for Alfresco employees.
https://github.com/alfresco/InsightEngine
Branches, pull requests and commits are happening in this internal repository.
When master branch is updated or a release branch is released, an internal Travis Job is mirroring the changes to the public Community Git Repository.
https://github.com/Alfresco/SearchServices
How to provide Community contributions
Since Community users don't have access to the working Git repository, PRs and issues must be raised in the Community repository. Remember to add also a test for the change you are proposing.
Below a sample process is described.
1. Community member: Create an issue in Search Services Git project
https://github.com/Alfresco/SearchServices/issues/381
2. Community member: Create a Pull Request with the proposed patch in Search Services Git project
https://github.com/Alfresco/SearchServices/pull/382
3. Communit member + Alfresco: Refinement of the PR with Search Services Team
Approval for https://github.com/Alfresco/SearchServices/pull/382 is required
4. Alfresco: Create a JIRA Ticket
https://alfresco.atlassian.net/browse/SEARCH-3022
5. Alfresco: Cherry pick the changes to a new branch in Insight Engine Git project
fix/SEARCH-3022_OptionalSSLProperties
6. Alfresco: Internal review and verification processes
https://github.com/Alfresco/InsightEngine/pull/1238
7. Alfresco: Merge the branch to Insight Engine master branch and mirror the change into Search Services Git repository
https://github.com/Alfresco/InsightEngine/commit/c860b70fc6841bc3b6fe485311de73458d3dfc3e
8. Communit member + Alfresco: Close the Pull Request and the Issue in Search Services Git repository
https://github.com/Alfresco/SearchServices/issues/381
https://github.com/Alfresco/SearchServices/pull/382
Thanks to Michael Chen for his contribution! We're using their work as sample for this post.
2 Comments
