This has been requested repeatedly, trying to convey the urgency a bit clearer:
With todays increasing mix of different device classes in production for all kinds of media, the lack of this feature has reached a breaking point.
The time and work required to synch up footage manually and/or use a work-around with Resolve/outsidePremierePro pushes you to use other NLEs to work efficiently and cost effective. Converting LTC inside premiere pro should be a given, footage ingest is at beginning, at the base of all projects!
And I do say this as someone who really likes premiere Pro.
Thank you, development team!

In the new export window you now have to manually turn "on" the captions tab, which you would think means the captions would be exported with the video, but no, you also have to click on the tab, then de-select the default "none" option and select burned in or side-car. This is really aggravating especially when you have to export dozens of videos with captions a day. It would make way more sense to have the default option be burned-in, not "none". If you want no captions, you can just click the captions tab to off, so the none option is redundant, and most people who have captions in their timeline will want them burned in, or side car.

Premiere has an issue where if you import a subclip into a sequence with a different frame rate than the source, the subclip will desync & include frames that were not present in the original subclip.

This might seem like a minor nuisance, but if you're using scene edit detection to break down footage into their constituent shots for repurposing (think of the subclips like a painter's palette), this desync can cause the first frame to be from the previous shot.

Now, I did find a solution to this problem (which I will link below), but it requires certain work arounds that I feel shouldn't be necessary. Especially because it's not unlikely for a project to include different footage sources with varying frame rates, depending on the project, so that only increases the amount of work needed to conform everything to a single, unified standard.

This might have been unsolvable for a lot of Premiere's history, but with the scene edit detection AI already detecting where the edits are in the clip, I imagine it shouldn't be too difficult to set up something similar with the subclips; a similar AI could detect changes in frame rate & adjust the clips to stay within their boundaries set up at the creation of the subclip, streamlining the process immensely.

This would also make the program more accessible to editors with AD\HD (like myself), where having to keep track of so many different variables can often downright sabotage any productive workflow that may have otherwise been achieved, so it would be a victory overall if something like this was implemented.

I won't act like I know how much work this would ultimately take to implement, but I do firmly believe that the foundations are already in place, so achieving such a feature (theoretically) shouldn't be a herculean task.

https://community.adobe.com/t5/premiere-pro-discussions/scene-edit-detection-subclips-bug/td-p/13090729

The new colour management is an interesting beta feature but having it on by default means all older projects open up looking crazy, having the 709 transform under the user applied LUTs. Also you can't override the input colour space if it isn't detected from the camera file.

The interpret footage colour settings also don't appear to follow the project across workstations, I'll open a project someone has sent me and its all enabled again.

There really needs to be a global way to turn it on and off, being forced to do it manually for all the rushes is a pain **********.

Currently, Premiere just appends Copy 01, Copy 02 etc to a duplicated sequence name.

As a result, this process requires users to maually "uptick" a new name / version number each time they duplicate. This means unnecessary key strokes and precision clicks for what should be a single keyboard shortcut: cmd + d (mac)

Premiere should be able to detect common naming conventions "v01, v02, v03...", "R1, R2, R3" etc. and automatically uptick and rename duplicated sequences accordingly.

Furthermore, it would be great to customize exactly how to name a sequence too. Think: placeholder variables for sequence dimensions (9x16, 4x5 etc), client name, project name, date, etc. For example, a custom convention of:

{clientName}{projectName}{sequenceDimensions}_v{newVersionNumber}

...might yield a duplicated seauence of:

AdobeNewProductVideo9x16_v5

Changing the seqeunce settings later to 1920x1080 (16x9) would then dynamically change the name of the sequence to:

AdobeNewProductVideo16x9_v5