kezhenxu94 edited a comment on pull request #12: URL: https://github.com/apache/skywalking-eyes/pull/12#issuecomment-751441865
> If you set two branches, why need one repo? For me, I am not following the ideas why making the project so complex. I personally don't see any complexity of using a release branch. All things work as before except for the releasing preparation work, which only involves with the release manager. > From my understanding, making two things ready before every release should be fine, as far as this moment. If we reached that days, I prefer to separate the repo. "making two things ready before every release" is fine but not easy, especially when you have more tools in the future, I'm not sure whether I'll create any new tool though. Especially when the tool only contains a small amount of codes (based on the goal of this repo, host infra tools, which are usually small), I don't REALLY want to create and maintain a repo for that. > I haven't seen any project using branch to release partial project. Does any of you have? If the way is not typical and widely in oss, we should not consider this. There are many, the one you are most familiar with is DolphinScheduler. Others like Istio, Kubernetes, etc.. > New repo is not limited in the ASF or SkyWalking. I know that, @fgksgf and @Humbertzhang are willing to maintain another new repo for the E2E, I'm ok to create one. This PR will be closed and the codes should be pushed to the newly-created repo, I'll just reshape this repo to only host license-eye tool. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
