Moving current scrap API docs to the top to avoid confusion

[Matiiss]

There is this notice that "everything below is deprecated" so it sort of made sense to move the working stuff to above that, I don't think that would cause confusion now (but I am not entirely sure what to do with .. ## pygame.scrap ## at the end of the docs, should it just stay at the end anyway? (I don't think we are using that feature anyway)).

Regarding the experimental notice, is that still relevant?

[MyreMylar]

LGTM 👍

I mean we could probably actually consider removing the old scrap stuff for 2.4.0 based on the 'two major versions since deprecation' guideline. However, since we've been galloping up major versions quite fast at the minute and this was a fairly large feature set I'd be happy to leave it another version at present. We also haven't officially codified a policy yet on the Wiki.

CPython's policy deprecation-to-removal cycle is two years - which for them also equals two major versions. Numpy uses a 1 year deprecation-to-removal cycle and two major releases (which for them are once every 6 months).

This modules was deprecated 7 months ago in March so there is a little ways to go yet on either rule.

[Starbuck5]

Good idea!

[Starbuck5]

I say keep the experimental notice for now.

I mean we could probably actually consider removing the old scrap stuff for 2.4.0 based on the 'two major versions since deprecation' guideline. However, since we've been galloping up major versions quite fast at the minute and this was a fairly large feature set I'd be happy to leave it another version at present. We also haven't officially codified a policy yet on the Wiki.

We don't have the market share to make large breaking changes. People can switch over to use pygame-ce with no problem because we have made very few backwards-incompatible changes.