I think we don't have any tech block for the repo split. If more people think it is reasonable, we can do that. And, we have to keep the version continuous when the repo splits.
Sheng Wu 吴晟 Twitter, wusheng1108 kezhenxu94@apache <kezhenx...@apache.org> 于2021年8月24日周二 上午9:53写道： > > Hi, I’m big +1 to split the repo into two, > the reason for me is to make it more clear and reasonable to maintain, > also, for new contributors they usually don't understand why Java agent > is different with other languages' agents and they usually mix the backend > with Java agent because they are in the same repo. > > As for the CI waiting time, if splitting the repo can reduce the time, > splitting the CI tasks into backend and agent, and only run the tasks > when their corresponding codes are changed, can also reduce the time. > > > > On Aug 23, 2021, at 17:56, Sheng Wu <wush...@apache.org> wrote: > > > > Hi > > > > In case not everyone noticed, the main CI-IT task time of our main > > repo is closing in one hour. > > Our e2e tasks and plugin tests are still efficient, but CI-IT will be > > a time blocker for us shortly. > > > > In my mind, the only option would be to split the java agent from the > > main repo codebase and create a skywalking-java repo instead. This is > > still not urgent, but the trend is very clear. > > When we reach that point, we will not have any so-called main-repo > > anymore. Everything would be a component, and replaceable. > > > > There is no action planned to be taken, but I hope everyone could know > > this day will come eventually. If the time is over 60 mins, we may > > have no option, but to do it. > > > > Sheng Wu 吴晟 > > Twitter, wusheng1108 > > ————————— > Zhenxu Ke (柯振旭) > GitHub @kezhenxu94 >
