镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

🎉🎉🎉 dotnet/runtime welcomes you 🎉🎉🎉 #253

Closed

Description

@ViktorHofer

We welcome all our beloved community members from CoreCLR, CoreFx and Core-Setup as well as colleagues and partner teams. As announced, we migrated all the commits reachable from HEAD in the master branches in CoreFx, CoreCLR and Core-Setup. While doing that we trimmed out unreachable files and rewrote commits to point to the original repositories by appending a message to every commit.

Repo stats

Commits: 60,221
Objects: 1187850, 218.45 MiB
Deltas: 877978
Files: 50668

Workflow changes

CoreFx --> src\libraries
Core-Setup --> src\installer
CoreClr --> src\coreclr

We recommend that you use the helper scripts in the repository root which are available per partition (e.g. libraries.cmd/sh). Additionally make sure that the Software Requirements are met (e.g. long path support on Windows).

TODO

  1. Mono isn't migrated yet. We expect this to be finished early next year.
  2. Live builds across partitions (e.g. coreclr <--> libraries) isn't working yet both locally and in CI. This is our top-most priority and while changing our infrastructure to enable live builds, we need to make sure that we don't regress the product or test coverage.
  3. No nightly builds available to test out until live builds are working.
  4. Issues aren't migrated yet. ETA early December.
  5. Docs are consolidated but require significant updates to accommodate the new paths and workflow changes.

cc @danmosemsft @MeiChin-Tsai @jaredpar @stephentoub @marek-safar @jkotas @dotnet/runtime-infrastructure

Activity

  1. added this to the 5.0 milestone on Nov 25, 2019
  2. pinned this issue on Nov 25, 2019
  3. removed
    untriagedNew issue has not been triaged by the area owner
    on Nov 25, 2019
  4. danmoseley commented on Nov 25, 2019

    @danmoseley
    Contributor

    Hooray and thank you for everyone that worked so tirelessly the last few weeks to get to this point!

  5. PureKrome commented on Nov 26, 2019

    @PureKrome
    Contributor

  6. hez2010 commented on Nov 26, 2019

    @hez2010
    Contributor

    What about CoreRT? Can we expect that there will be a full AOT compiler in the future?

  7. Gnbrkm41 commented on Nov 26, 2019

    @Gnbrkm41
    Contributor

    @hez2010, From dotnet/announcements#119:

    Yes. We plan to retire/archive the corert repo. Some of the technology in the corert repo will be migrated to the master branch of dotnet/platform, where it will be productized as part of .NET. Other portions of the corert repo will be migrated to feature branches of dotnet/platform, where the experimentation can continue. In this way, we will use feature branches to continue experimenting with the corert technology, while making it easier to share portions with its shipping counterpart and also graduate functionality into master if/when it’s ready.

  8. alrz commented on Nov 26, 2019

    @alrz
    Member

    CoreFx --> src\libraries I don't understand the purpose of this renaming. Why not just corefx?

  9. huoyaoyuan commented on Nov 26, 2019

    @huoyaoyuan
    Member

    Don't forget to update pinned repositories of the organization.

  10. shaggygi commented on Nov 26, 2019

    @shaggygi
    Contributor

    @huoyaoyuan

    Don't forget to update pinned repositories of the organization.

    Referencing #255

  11. PRIMETSS commented on Nov 26, 2019

    @PRIMETSS
    Contributor

    Nice work Guys & Gals!! Must have been MAMMOTH effort to merge all this!
    I think CoreFx --> src\libraries rename is fine. Helps differentiate prev corefx from the rest, as from someone only used to corefx, there is a lot more to get head around folder structure wise when trying to navigate it all. Nothing negative though!

    Is there a directory tree doc outlining a brief description of whats what. I know that's not easy, but wondering if its been automated some how in docs? As after initial build the artifacts folder is quite daunting....

  12. deinok commented on Nov 26, 2019

    @deinok

    Is there a way to generate the .tar like that contains the runtime itself?
    I'm looking how to integrate the runtime and sdk in projects like buildroot and yocto.

  13. ViktorHofer commented on Nov 27, 2019

    @ViktorHofer
    MemberAuthor

    Is there a way to generate the .tar like that contains the runtime itself?

    Not yet as we haven't enabled live builds. We are working on it.

  14. ViktorHofer commented on Nov 27, 2019

    @ViktorHofer
    MemberAuthor

    Is there a directory tree doc outlining a brief description of whats what. I know that's not easy, but wondering if its been automated some how in docs? As after initial build the artifacts folder is quite daunting....

    Not yet as we haven't finalized the structure. We plan to move a few things around and Mono will join soon.

  15. ViktorHofer commented on Nov 27, 2019

    @ViktorHofer
    MemberAuthor

    CoreFx --> src\libraries I don't understand the purpose of this renaming. Why not just corefx?

    We don't use the term corefx anymore. Also internally our team was renamed to ".NET Libraries".

  16. unpinned this issue on Dec 4, 2019
  17. ghost locked as resolved and limited conversation to collaborators on Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions