snleee opened a new issue #3623: Notes on preparing for Apache release URL: https://github.com/apache/incubator-pinot/issues/3623 Notes on preparing for Apache release === Given that Pinot is now a part of Apache incubator projects, we need to clean up the code base to be Apache compliant. Before we can drill into the detailed process, there are some clean up works that need to be done. 1. Remove dependency of `org.json:json:20080701`. The license for org.json library is not compatible with Apache license. We are using this library extensively for serializing & deserializing json object. Ideally, we should pick one json libarary `e.g. Gson or fastxml` and use the same library for all serialization/deserialization of JSON objects. 2. Change package name from `com.linkedin` to `org.apache`. This will break a lot of internal and external projects that are importing Pinot libraries. We need to plan carefully and do the update. 3. Need to change license header to all files. (Currently, our license header contains copyright of LinkedIn and this has to be removed. Also, license header provided in Apache documentation is slightly different from what we have). It seems that dealing license header becomes easy if we install maven `Apache Rat` plugin. The correct header should be the following: ``` Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ``` 4. Cleaning up branches. - We have directly pushed the working branch to main repository when creating a pr. This have resulted in a lot of branches (over 130 after deleting all branches whose pr is either merged or closed) in the main repository. Moving forward, I think that we should fork the main repo and use local repo for creating a pr to avoid creating too much branches in the main repo. - I would like to keep the main repo clean because we will have to keep branch for each release. (e.g. Gobblin keeps only 14 branches for their main repo https://github.com/apache/incubator-gobblin)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
