PRDoc crate semver

[Morganamilo]

So we can properly version bump with the next release we need to know what kind of changes were made to these crates. Can authors of the following PRs update the PRdoc to specify patch, minor or major. See example here:

polkadot-sdk/prdoc/pr_2119.prdoc

Line 10 in 9d052b7

crates:

@eskimor @dharjeezy @ordian @k-gunjan @muraca @PraetorP @s0me0ne-unkn0wn @JuaniRios @asiniscalchi @ermalkaleci @bkchr

• Fix algorithmic complexity of on-demand scheduler with regards to number of cores. #3190
• Try State Hook for Beefy #3246
• collator protocol changes for elastic scaling (validator side) #3302: Update pr_3302.prdoc #3985
• Pallet AURA: remove pallet::getter macro and write the corresponding code #3350
• removed pallet::getter usage from cumulus pallets #3471
• XCM Fee Payment Runtime API #3607
• Eliminate experimental feature #3654
• Add HRMP notification handlers to the xcm-executor #3696
• [parachain-template] runtime API Implementations into mod apis #3817
• process enqueued messages on idle #3844
• pallet-scheduler: Unrequest call on failed lookup #3849
• pallet-referenda: Detect incorrect pre-image length #3850

[asiniscalchi]

#3817 was tagged as R0-silent so I imagine PRdoc was not needed here

[bkchr]

#3817 was tagged as R0-silent so I imagine PRdoc was not needed here

I mean it is not very important to appear in the release notes. However, the sp-api-macro change is actually something that requires a minor bump. Maybe you could create a pr and make the prdoc only about this change with a minor bump for this crate?

[ggwpez]

We dont yet have CI checks that assert that the Prdoc bumps are correct.
So we cannot confidently use this to version it - yet. But it would still be good to have the tools in place to do so.

[bkchr]

So, @ggwpez we don't yet need to have the correct bumps in the prdoc yet? Any idea when CI etc tooling will be ready?

[ggwpez]

So, ggwpez we don't yet need to have the correct bumps in the prdoc yet?

Yea, looks like we were not ready for it yet. Reverted here #3987

Any idea when CI etc tooling will be ready?

No. I think @Morganamilo is working on an extension for the parity-publish to detect breaking changes though.

[asiniscalchi]

#3817 was tagged as R0-silent so I imagine PRdoc was not needed here

I mean it is not very important to appear in the release notes. However, the sp-api-macro change is actually something that requires a minor bump. Maybe you could create a pr and make the prdoc only about this change with a minor bump for this crate?

Hope it fits : #3995

[s0me0ne-unkn0wn]

Maybe create a single co-authored PR instead of a bunch of one-liners?

[ggwpez]

We dont need it for this Release, its causing too much noise now to ping dozens of ppl. Sorry about this.