Hello, contributors! As many of you might have hea...
# contribute
h
Hello, contributors! As many of you might have heard, we've been moving the backend development of Flyte to a monorepo and today is the official moving day. The following repositories are moving to the monorepo: • datacatalogflyteadminflytecopilotflytepluginsflytepropellerflytestdlib Each one of these components is now a top-level directory in the flyte repo: https://github.com/flyteorg/flyte. We'll be marking each of those repos as read-only by EOD today. Last night we moved all open PRs open in the last 3 months to the monorepo (e.g. https://github.com/flyteorg/flyte/pull/4147/). Notice that some of those PRs will contain merge conflicts as the golang package names will have changed. For example, if your code was importing a package from the logger from "github.com/flyteorg/flytestdlib/logger" now it has to import from "github.com/flyteorg/flyte/flytestdlib/logger". The changes should be mostly mechanical though, I recommend using https://github.com/sirkon/go-imports-rename to rename the Flyte imports (this gist shows how to use it). You can use a simple search-and-replace obviously.
🔥 7
🙏 3
thx 3
flyte 2 2
💯 5
gratitude thank you 3
🎉 7
flyte 6
🙌🏽 1
🚀 3
🤩 3
🙌 5
s
Great news! Any plan to drop a new release? The latest one was in August. I see there are later tags but no release yet. Thanks!
h
@steep-jackal-21573, we are going to release Flyte 1.10 in the next few days, just waiting for a few changes to land. I'm going to announce it here when it happens.
🙏 1