View in #core on Slack
@Matt_Robinson: Who is available for the weekly meeting?
@Viktor: Almost missed it.
@Matt_Robinson: I’m aware that there has been a lot of work going into the experimental v2 repository and also on-going discussion about the Directory. I’m not sure if we have the people here just yet to get an update and discuss any priority issues.
There is an issue for new installs in 1.5.x that has been affecting the upgrade to the latest CP versions in installation solutions like Softaculous. I found an issue in the installation code and have a PR fix in a 1.5.2 milestone and I think the fix has been confirmed to Viktor as working.
https://github.com/ClassicPress/ClassicPress/pull/1219
@Viktor: Yes, Softculous confirmed the issue is fixed.
@Matt_Robinson: Ah, Viktor has commented on the PR to that too. So, is the idea to merge that fix and move with a 1.5.2 release?
@Viktor: I think that’s a good idea, since this causes an issue with new installations.
@Matt_Robinson: Are we making that release sooner or waiting a little longer so users don’t get upgrade fatigue.
@Simone_Fioravanti: For me sooner is better. If someone decides to start a fresh CP site can be blocked at the begin.
@Viktor: Updates remind people we’re alive and working on CP 
@Matt_Robinson: I’m not going to argue with those points 
I’ll set the PR merging now.
@Viktor: Is it possible to have an automated test to test new installation process? In case things like this come up again.
@Matt_Robinson: I can have a look into that - the tests use a different config file to access the database for testing though, so I’m not sure.
Is there anything else for today that needs discussing or should we use the time left to press on with a 1.5.2 release?
@Simone_Fioravanti: For me nothing more
@Viktor: Only thing from me for v2, I have updated main branch with WP-CMS code including tests. Some might need to be removed probably. Since I had to rebase branch, PRs were closed. I created one PR which includes one commit per closed PR.
@Matt_Robinson: I need to update my local clone of the v2 code, been busy with other things this week.
@Viktor: Yes, this week got busier for me than I thought. Hopefully, by next week we’ll have directory wrapped up.
@Matt_Robinson: Okay, I’m going to start the release process locally, are you happy to stick around for some testing and checking?
@Viktor: Yes, I’m around.
@Simone_Fioravanti: Yes.
@Matt_Robinson: I’m testing an updated build script.
Draft release post is here:
https://forums.classicpress.net/t/classicpress-1-5-2-release-notes/4583
GH diff is here:
https://github.com/ClassicPress/ClassicPress/compare/1.5.1+dev...1.5.2+dev
With updated script new releases are showing as ClassyBot now rather than ‘nylen’ 
@Simone_Fioravanti: Diff is clean.
@Matt_Robinson: @Viktor - you’ll need this for media channels
@Viktor: Thanks.
@Matt_Robinson: npm is installed and build is processing.
Release repository diff here:
https://github.com/ClassicPress/ClassicPress-release/compare/1.5.1...1.5.2
Looks right to me
Zip for freash install testing for 1.5.2 now available here:
https://github.com/ClassicPress/ClassicPress-release/archive/1.5.2.zip
@Viktor: Starting up Docker to test.
@Simone_Fioravanti: MAMP fresh install good.
@Matt_Robinson: Localhost install was clean and easier for me as config file output was correct - although spaces are removed as the lines are replaced which annoys me! I can live with it though as v2 will correct that.
@Simone_Fioravanti: educatorecinofilo.dog up with 1.5.2. Just an API error, but guess because 1.5.2 is not already in API.
> spaces are removed
Good, it follows my code style 
@Matt_Robinson: API not updated as yet. Is the Release post change log okay? The change will be dropped into the GH post next.
@Simone_Fioravanti: Yes, just “fix fresh…“. BTW I’ve not contribute to the changes…
@Viktor: Good to go from me. Installation works.
@Matt_Robinson: Didn’t you leave a review on the PR @Simone_Fioravanti
That’s enough of a contribution for me then 
Okay, I think we are done. 1.5.2 is up, release post os published and API should be pushing updates now.
@Simone_Fioravanti: API is pushing updates.
@Matt_Robinson: Thank you both for double checking that process. I think that’s all for now then.
@Viktor - are you going to reach out to Softaculous?
@Viktor: Yes, I will message them.
@Simone_Fioravanti: Thank you 
@Matt_Robinson: https://github.com/ClassicPress/release-builder/pull/8
Updated script now shows releases from ClassyBot too. PR created for that.
@Simone_Fioravanti: Think can be merged.