10:00:47 -xmr-pr- timetherewere opened issue #1060: Add "Daemon" entry to Moneropedia 10:00:47 -xmr-pr- > https://repo.getmonero.org/monero-project/monero-site/issues/1060 13:22:37 ErCiccione[m]: Note I updated the site with new hashes for GUI release 0.15.0.4 17:00:47 -xmr-pr- selsta opened pull request #1239: posts: add v0.15.0.4 release post 17:00:47 -xmr-pr- > https://repo.getmonero.org/monero-project/monero-site/-/merge_requests/1239 17:56:11 binaryfate: Do you mean you also updated the server to latest master? 17:59:40 oh nevermind, i see you updated the server too 18:00:38 .merges 18:00:38 -xmr-pr- #1229 #1230 18:01:23 luigi1111 could you merge ^ 1230 is urgent or a menu won't show up 18:04:03 done 18:04:36 Thank! 18:04:39 *s 18:08:44 I'm reviewing selsta's blog post right now, so maybe we can quickly merge it and then update the server with the new changes 18:08:54 oki 18:13:33 selta: since there are no credits in the blog post, what about pointing to the release notes on github? So that people can see the credits there? 18:13:50 i'm thinking of adding a dedicate line like "for credits see release on github" 18:14:08 I just copied the previous blog post 18:14:16 open for changes 18:14:20 or simpy to substitute the link here: https://repo.getmonero.org/monero-project/monero-site/-/merge_requests/1239/diffs#89d70ebb0510cbb84a9a1364877c470db0c6c560_0_24 18:14:41 instead of pointing to the full changelog, we could point to the release notes 18:14:53 i think it's a good idea to have at least one of the two release notes pointing to the other 18:14:54 the problem is that the last release was v0.15.0.2 18:15:07 so the v0.15.0.4 release notes don’t contain all the changes 18:16:22 Ok, could you simply add a link to the github release? maybe under the string i linked to 18:18:28 updated 18:19:34 Thanks :) 18:22:24 .merge+ #1239 18:22:24 Added 18:22:51 .merges 18:22:51 -xmr-pr- #1239 18:22:57 luigi1111 could you quick merge the blog post? ^ 18:26:58 didn't someone get mad when I did that before 18:27:04 or was that ccs 18:28:30 Was definitely the CCS. And it was probably me who got mad :P 18:28:37 btw, if you want to wait a bit fine for me 18:28:55 who is refreshing the website and when might that happen? 18:28:58 but would be cool to have the post out before selsta's reddit post tomorrow 18:28:59 we can get it in before then 18:29:10 Sorry btw ErCiccione[m] I assumed master was ok to deploy so simply merged my changes and did it. I realized afterwards there might have been temporarily broken stuff on master (I don't know what policy there is for the website repo). I'll check with you next time. 18:29:36 depends when binaryfate is available to update the server 18:30:00 I'm available now and for few hours 18:31:14 alright let's give it 1 hour 18:31:16 who is refreshing the website and when might that happen? <-- I did today to update hashes and download for gui 0.15.4. Otherwise I only do when someone asks. 18:31:24 binaryfate: no worries, usually master is always working, but i missed to update a file with one of my MR and one menu wasn't showing up. I PRd it right after but reviews are always a bit slow. Usually it's not a problem, no worries. And soeey about that, was my mistake 18:32:31 *sorry 20:02:37 Getting really annoyed by Gitlab lol, why am I getting emails that my CI pipeline failed when I don’t even have a runner setup. 20:25:17 Gitlab email notifications take half of my inbox 22:11:07 luigi1111: are you around to merge the blog post? otherwise would be better to update the server now, so that the broken menu can be fixed 22:11:29 oops I forgot! 22:13:55 done 22:23:06 great, thanks :) 22:23:25 binaryfate could you update the server?