(03-20-2020, 01:59 AM)tigerw Wrote: [ -> ]RIP
So how is everyone doing?
Pretty good! I currently have a week off due to a certain epidemic, which resulted in some Cuberite contributions (yay) from my side. Hopefully everyone here is well.
A week off, lucky you. I gotta work from home, which, considering my baby boy's growing teeth, is a nightmare. Not to mention the poor internet connection, luckily at least that improved when I asked my neighbors to share their connection. That was a fun evening - trying to make a 15-year-old wifi AP in the attic connect to another network. Took me several hours, and just when I was about to give it up, it suddenly started working. Well, I've got a new AP incoming, hopefully on Saturday, so the connection speed might improve. Unless I find out it is incompatible with the antenna on the roof. Hrrrrmmmm, life....
I finally found some time to at least go through some of the PRs and comment on them. My knowledge of Cuberite is rusting away, the memory isn't what it used to be

Now I have to look up everything before typing an answer.
I see that the windows build are old. How are the builds generated, can I offer my personal PC for that?
The builds from the buildserver are no longer used, the homepage links to Appveyor builds, which are fresh.
Perhaps we should remove the windows builds from the Jenkins? , what do you think?
(03-22-2020, 05:50 PM)Seadragon91 Wrote: [ -> ]I see that the windows build are old. How are the builds generated, can I offer my personal PC for that?
Use the Appveyor builds linked on the homepage, the buildserver ones were discontinued when we moved away from xoft's server.
(03-22-2020, 07:39 PM)xoft Wrote: [ -> ]The builds from the buildserver are no longer used, the homepage links to Appveyor builds, which are fresh.
Perhaps we should remove the windows builds from the Jenkins? , what do you think?
Maybe not completely remove them (can still be useful for debugging), but place a notification on the build server page?
Alternatively move them into some archived section, so that old links no longer work. Bearbin decides though, they probably take up a bit of space.
The space isn't particularly a concern for me at the moment, the buildserver has plenty of it. I haven't archived the builds for precisely the reason that the old links _will_ still work; but I realise now that breaking them is probably a good thing if it means people switch to the new working builds.
I think the best thing to do would be for me to set up another server just to serve 307s, that way we can change the location of the builds without having to worry about updating it in all the places. Once I do that I'll move the old windows builds to a new URL so people hopefully get up to date.