All, The YuniKorn repositories have been renamed in GitHub as part of the graduation process. From this point until we complete the migration tasks, please do not submit any non-migration related PRs or approve any PRs. A follow-up email will sent to this list once these tasks have been completed.
Thanks, Craig > On Mar 24, 2022, at 4:25 PM, Weiwei Yang <[email protected]> wrote: > > Hi Wilfred > > Thank you for the detailed write up, this is very helpful. > I have created the INFRA ticket as discussed: > https://issues.apache.org/jira/browse/INFRA-23028. > Once the infra team renames our repos, Craig will make the changes > accordingly to get everything back up and working. > It may be disruptive for 1 day or 2, we will keep that posted on the > mailing list. > > Thanks > > On Wed, Mar 23, 2022 at 11:47 PM Wilfred Spiegelenburg <[email protected]> > wrote: > >> Hi, >> >> As part of the top level graduation we are removing the incubator >> references from our code and documentation. >> One of the steps is moving or renaming the code repositories. The >> normal impact of that change is that the remote set in a cloned >> repository _should_ be updated *). For our project this rename has a >> flow on effect to our code base because of the way Go handles >> dependencies. >> >> This email is just to explain the process of the code change. Multiple >> steps have to be executed, steps will be announced when needed. >> >> Renaming the repositories will require us to change the imports >> throughout our code base. This is a multi step process. The steps >> involve: >> * update the scheduler interface (SI) code to change the module and >> import statements, >> commit the changes. >> * update the core repository code to change the module and import >> statements, >> changes must include the SI pseudo ref, and commit the change >> * update the k8shim repository code to change the module and import >> statements, >> changes must including the core & SI pseudo refs and commit the change >> >> After the changes all tests in each of the repositories should pass. >> We must do this for the master branch. After the change in master we >> can prepare for branching 1.0.0 not before. >> >> Depending on whether we still want, or need, to release from an older >> branch further changes might be required. The changes might be the >> same as for the master, we might get away with less. The proposal is >> to not change anything for the older branches until we have a real >> need to release an older branch. >> At the moment that seems unlikely, however we cannot dismiss that. >> >> The first step in the process is to request the rename from Apache >> Infra for which Weiwei volunteered. >> Import changes will follow after the renaming of all repositories is >> ready. Craig has stepped up to perform that change. >> More details can be found in the community sync up notes [1]. A list >> of further tasks for which help is needed is also part of the notes. >> >> Wilfred >> >> [1] >> https://docs.google.com/document/d/165gzC7uhcKc5XDWiMYSRKBiPQBy2tDtXADUPuhGlUa0/edit#heading=h.4ojjr45cn3ra >> *) github will redirect the old repository name incubator-yunikorn-* >> to the new name yunikorn-* for most actions which means you might not >> notice but it can get confusing >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
