Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Apache Git Repo Github mirror: https://github.com/apache/incubator-gobblin

Website

Status

In ProgressDone

Steps

  1. Open an INFRA JIRA ticket to request a new git repo for site content. 
  2. Make prerequisite changes to current content. (Refer to Olivier's comment on GOBBLIN-2 )
  3. Publish content on new git repo to populate the website. (Move documentation from ReadTheDocs to the website. )

...

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyGOBBLIN-163

Results

Wiki Space: Gobblin Home

Jenkins

Status

In Progress Futuristic 

Note: Changed to 'Futuristic' because Travis has improved under Apache. So, we can take time to move to Jenkins.

Steps

  1. Open an INFRA JIRA ticket to setup and enable Jenkins for code base. 
  2. Explore setting up pre-commit hook such as Yetis.  
  3. Configure Gobblin on Jenkins instance. 

...

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyGOBBLIN-164

Package Rename

StatusIn Progress

Done

Related wiki: Gobblin Package Rename Implications

Steps

  1. 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
  2. The existing configuration will continue to remain the same so that no migration is required for it. 
  3. The class names will have new packages, so users will have to rename them in configs; and custom implementations will have to be updated. 
  4. The state-store will be unreadable with new changes, so we would need a shim for that. 
  5. Two versions must be maintained (previous major version v0.x for gobblin / com.linkedin.gobblin namespace and v1.x for org.apache.gobblin)

...