+1

So, if I understand correctly, this is done already, and was pushed to (whether that was a good idea or not) to Fedora 36 stable too, already?

Yes, it got pushed to Fedora 36.
Intention of this Change proposal was to make sure users are communicated correctly about new features and changes, as there are some visible changes.

It also turned out that some packages which depend on Emacs need to be updated.
This is first time I have created a change proposal, so I'm not sure what happens in this case.

Yes, it got pushed to Fedora 36.
Intention of this Change proposal was to make sure users are communicated correctly about new features and changes, as there are some visible changes.

Well, you targeted your Change proposal at Fedora 37, so that kind of sets up the expectation that it's a big enough change not to get pushed as an update to stable branches.

It also turned out that some packages which depend on Emacs need to be updated.

That sounds like, this would have indeed been a big enough change to warrant being exclusive to Fedora 37.

This is first time I have created a change proposal, so I'm not sure what happens in this case.

Well, the update is already stable on F36, so there's nothing we can do other than to give you a metaphorical "slap on the wrist" :wink:

However, I'd appreciate it if you could help with fixing the problems that were caused by updating emacs to v28 both prematurely (before this Change proposal was approved) and on a stable branch, apparently without considering the possible ramifications.

FWIW, since this Change proposal is now basically moot, have my +1 vote ...

Well, the update is already stable on F36, so there's nothing we can do other than to give you a metaphorical "slap on the wrist" 😉

Understood. This was something out of my hands as well (I don't have access to push updates), we could have coordinated this better for sure.

I will check the packages having issues and try to fix whichever I'm able to over weekend.

Owners, do not implement this work until the FESCo vote has explicitly ended.

This is exactly why we have this process...

Given the fallout, I'm inclined to recommend that emacs bump epoch and downgrade back to the previous version in F36. As for F37... +1, assuming @bhavin192 can smooth out the wrinkles.

After a week, the vote is +2,0,-0 (with a caveat on one of the +1s). Waiting for additional votes/discussion.

I don't think the breakage is that bad for F37 anyway.
Yes it breaks a few old elisp packages - but delaying 28 isn't going to get those fixed any quicker. (For example make-obsolete was already deprecated in emacs 23! We can't support back-compatibility to old unmaintained libraries forever. This first Emacs 28 version was released 4 months ago: April 4.)

I have been using Emacs 28 in my Fedora 36 for some months now (from Bhavin's copr repo and now the update) without any problems and the native elisp jit compilation speed-up is really significant.

It is probably a good idea to add @defolos to the Change.

Based on @petersen's assessment: +1 from me.
I too have been using emacs 28 (and now 29) from copr and I don't think it makes sense to delay the update. I don't even think it makes sense to try to revert the update in F36 at this point.

After 2+ weeks, the vote is +4,0,-0, hence this is APPROVED.

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4UCHC2R6JZQHHR3UT7H7XS4LPZ3K3JQ7/