I can see many issues are migrated but still many more are not. Why are some issues not migrated? Is it just the migration is not yet completed, or for some reason they won’t be migrated?
We mainly migrated issues that were assigned to projects, aka they were actually being “tracked”. Old issues that may got “lost” can still be linked in the old repos. This was also used as chance to clean up the issue tracker.
I see. What should I do for issues that I think are important and should be tracked? Do I just open a new one or ask someone to transfer the existing one?
Sadly we can not transfer issues from an archived repo (not sure why). I mean if there are enough issues, we could probably unarchive and move them over. However, you can also just create a new one and link the old one in the description.
However, you can not expect from someone to see these issues with the same importance as you. You are free to open issues in the repo, but this doesn’t mean that someone starts working on them.
That’s fine. I will open new issues for my old issues.
as most of you have noticed, the Polkadot SDK is created and ready for you to transition. We’ve updated our FAQ giving you a suggestion how to migrate your PRs to the new repo. Please also check out our updated guidelines.
Be aware that the CI is currently having some minor problems, bear with us as we work to fix it as soon as possible.
If you have any questions in relation to the migration, raise it on GH discussions and if you run on any issues (not CI related) or your issue was not migrated to the new repo, please open it on GH issues.
Have a nice rest of the week 
How stable is the new monorepo? I ask here as the linked GH discussions page 404s, as does /discussions alone.
Over the past month, several growing pains have been worked through, which I don’t stand here to dismiss or shouldn’t have been worked through, yet to question if the repository is actually ready for transition.
My biggest personal concern, which is standing, is Import Substrate CI to Monorepo · Issue #1126 · paritytech/polkadot-sdk · GitHub. I’m not clear on if the new repo has had the Substrate CI imported, and is accordingly being properly checked or not.
Then, even if that CI has been imported and the repo is moving forward appropriately (besides misc doc commentary), I’m unsure what the tagging policy is/will be. Prior, substrate had polkadot-v0.x releases which could be relied on as releases. Parity announced a polkadot-1.0 tag for substrate, with it promising a LTS release. To quote,
Polkadot 1.0 also introduces “Long Term Support” (LTS) releases, ensuring critical security fixes for parachains without the need to upgrade to newer versions with breaking changes. The LTS releases will be maintained for 6 months, providing enterprises and users with prioritized stability and a secure parachain codebase.
Unfortunately, this new repository is a massive reorganization which users now must update to for said fixes (despite still being in the 6 month window promised). While I won’t say the new repository breaks the LTS offering, I will say I’m unsure how it translates.
While I can use the new repo’s tags, as they become available, so far there’s a Polkadot release and a global release candidate (no global release). I’m unsure if the Polkadot release effectively has the same meaning as it did on the Substrate repo.
In summary:
- Is the new repository stable, with the CI fully migrated?
- What is the policy for creating tags on it? Should I expect a
substrate-1.1.0tag?
LTS is only around security fixes. So, if there is any major security issue found we would back port it. Currently there is no need and you can just continue to use the old repos. They are archived, but still readable.
The repo is ready. Not sure what you understand as stable.
There will be no substrate tag. Before it was also always around polkadot releases. We will continue to release the Polkadot node and these releases will also release Substrate and Cumulus.
we deactivated the GH discussions since no questions came in during the first weeks of transition