pallet-collective | port to frame v2#8193
Conversation
Co-authored-by: Guillaume Thiolliere <gui.thiolliere@gmail.com>
Co-authored-by: Guillaume Thiolliere <gui.thiolliere@gmail.com>
|
so if master merged and a runtime migration either in the pallet or in a polkadot companion at the runtime level and it should be good |
Thanks @thiolliere , will pick up for this week |
|
anyone working on this? |
|
it needs a migration code in polkadot or here. Because the old pallet prefix is different from the pallet name used in polkadot and kusama. |
|
Hello @thiolliere, will pick up run time migration part immediately. |
|
you need to merge master because rust version in CI has changed. But last changes are good to me |
…tive-port-frame-v2 merge to upstream master
…tive-port-frame-v2 Merge upstream master
|
can you merge master ? Once this is done I'll take a second look and it needs another approval maybe @ascjones or somebody else. Then it is good to go. |
…b0/substrate into shamb0-br2-collective-port-frame-v2
|
Hello @thiolliere, merge to upstream master Done 👍 |
|
@shamb0 looks like collective got updated since this was done. Care to update this for latest master? If so, feel free to reopen |
|
yes need master merge, and a second review |
pallet-collective | port to frame v2
related #7882
From https://crates.parity.io/frame_support/attr.pallet.html#checking-upgrade-guidelines
So users of the collective pallet must be careful about the name they used in construct_runtime!. Hence the runtime-migration label, which might not be needed depending on the configuration of the collective pallet.