Table of Contents |
---|
Code
Status
In ProgressDone
Steps
- Create a new Apache Git repo (our champion i.e Olivier should be able to help with that since he has necessary permissions). This will come with a Apache Git repo's Github mirror.
- Open an INFRA JIRA ticket to start the migration (as described in next step).
- Transfer ownership of the linkedin/gobblin repository to an Apache INFRA person. See this page for details on what gets kept and lost. The Apache INFRA will seed the Apache Git repo with linkedin/gobblin repository content and re-designate the linkedin/gobblin repository as Apache Git repo mirror.
- Update documentation.
...
Apache Git Repo Github mirror: https://github.com/apache/incubator-gobblin
Website
Status
In ProgressDone
Steps
- Open an INFRA JIRA ticket to request a new git repo for site content.
- Make prerequisite changes to current content. (Refer to Olivier's comment on GOBBLIN-2 )
- Publish content on new git repo to populate the website. (Move documentation from ReadTheDocs to the website. )
Jiras
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
Website: https://gobblin.apache.org/
Mailing lists
Status
In ProgressDone
Steps
- Post notification to Google groups pointing to new mailing lists.
- Lock down Google groups.
...
Closed Issues: https://github.com/linkedin/gobblin/issues?q=is%3Aissue+is%3Aclosed+label%3A%22Moved+to+Apache+Jira%22
Pull Requests
Status
TODODone
Steps
- Update PR instructions to put JIRA issue numbers in PR titles.
- Add Github label to identify PRs without JIRA issues in title.
- Ensure that tooling in Jenkins is enabled for auto-closing issues based on PR title.
...
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Wiki
Status
In ProgressDone
Steps
- Open an INFRA JIRA ticket to create a wiki space.
- Create relevant wiki pages. Move documentation from ReadTheDocs to the website.
- Define how content is distributed between wiki and the website going forward.
...
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Results
Wiki Space: Gobblin Home
Jenkins
StatusTODO
In Progress Futuristic
Note: Changed to 'Futuristic' because Travis has improved under Apache. So, we can take time to move to Jenkins.
Steps
- Open an INFRA JIRA ticket to setup and enable Jenkins for code base.
- Explore setting up pre-commit hook such as Yetis.
- Configure Gobblin on Jenkins instance.
...
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Package Rename
Status
Done
Related wiki: Gobblin Package Rename Implications
Steps
- Rename packages and schema namespaces from gobblin and com.linkedin.gobblin to org.apache.gobblin
The entities to take care of:- Java packages
- Avro schema and namespaces
- RESTLi schema and namespaces
- META-INF services
- SQL references
- Reflection
- Alias Resolution
- Pull and config files
- Config store hierarchy
- Default config references
- Fully qualified names
- Hardcoded class and package names
- Powermock / mockito change in exclusion / inclusion params
- Build changes to operate on different package structure
- Typed references / imports / extension of classes and implementation of interfaces
- Shell / launcher scripts
- Documentation / Javadocs
- The existing configuration will continue to remain the same so that no migration is required for it.
- The class names will have new packages, so users will have to rename them in configs; and custom implementations will have to be updated.
- The state-store will be unreadable with new changes, so we would need a shim for that.
- Two versions must be maintained (previous major version v0.x for gobblin / com.linkedin.gobblin namespace and v1.x for org.apache.gobblin)
Jiras
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
Notes
Email to send out on Google Groups announcing the migration
...