View in #core on Slack
@Matt_Robinson: Is anyone online and feeling eager for a PR review meeting today?
I’m conscious that 1.5.0 is probably ready to release but perhaps that’s best for next week.
I’ve been merging some of the Dependency updates after testing, one more pending but not urgent.
There is just #1201 for consideration if we include that in 1.5.0 - especially while we are figuring out whether we re-fork or try to keep backporting and probably miss out on a lot of efficiency changes made already upstream.
@Simone_Fioravanti: Some background… I’m writing a proof of concept plugin to get updates from the directory (the other path is to use Beda’s one). PR #1201 is to let that header be used. We forced developer to put that in every plugin but it’s not readable.
@Matt_Robinson: It looks like a pretty simple change - I presume it is just parsing the plugin file headers,
@Simone_Fioravanti: Yes… one line to get
@Matt_Robinson: Let’s merge it then, simple change and it get’s 1.5.0 ready in part for the plugin directory - right?
@Simone_Fioravanti: Right. For sure for the plugins part.
@Matt_Robinson: Okay, I’ve merged it. Just running local checks on #1202, what do you think of the changes in the Terser update PR #1184 - on first glance it all looks reasonable changes to me.
@Simone_Fioravanti: Looks clean!
@Matt_Robinson: I thought the same - will merge that ready for 1.5.0 too later, the
rollup update was clean too so that is merging.
Okay, I think that’s probably all for now. Unless anyone has anything else?
@Simone_Fioravanti: Do you plan to release 1.5 after Jan 6, right?
@Matt_Robinson: Maybe a week today, are you comfortable leading a main release after the RC run through and I can be available to assist again or would you prefer I do it?
@Simone_Fioravanti: Those days I’ll be away…
@Matt_Robinson: Okay, so maybe I can / should make the 1.5.0 release next Thursday then instead of the PR session, the next job after that is reviewing the recent poll and deciding on the next path we take and then figuring out how we do what is needed.
Enjoy your time away!
@Simone_Fioravanti: Thank you!
@Matt_Robinson: Okay then, that’s all for today I think, until 2023!