Jump to content

Changes in the House of Development


Recommended Posts

Since a few weeks ago, some changes have been made to the development process of the server. They're listed below, in no particular order:

  • Updates are now scheduled for every first weekend of the month.

    This is a convenience thing, which allows for easier tracking of when an update's scheduled and more consistency. It does cut, on average, a week from the current cycle length. But this should be a non-issue.

    This is in effective starting with the August update. Which means that the time between the July update (today, 22JUL) and the August update (05AUG) is only 2 weeks long. But we decided that this is better than skipping the August update and having a thus bigger September update.
  • Contributors can now review pull requests.

    As it says on the tin. Contributor reviews can now count towards the review limit. Though this is with the caveat that we don't necessarily trust them. So a new contributor's review, or a review from a contributor who's obviously not as skilled as required for the task, may still merit two developers look over a PR. But in general, we hope that this results in more eyes on code changes, resulting in less bugs and errors.
  • Two reviews per pull request now required.

    In line with the above, we would like to increase the number of eyes on code that's being merged. As such, all PRs targeting development must optimally pass 2 peer reviews. With contributor reviews counting as described above. Clear exceptions made for high priority PRs, obviously, and for PRs bypassing development. For the latter case, 2 reviews are required for a merge before 24 hours, and 1 for merge after 24 hours.
  • The Projects subforum.

    This subforum has been created to better facilitate developers and contributors gathering feedback on active projects. The main difference between this subforum and the suggestions subforum is that the projects subforum describe actually in-development (and hopefully soon-to-release) projects. And as such, the feedback should be oriented towards the final idea which was chosen for implementation, which at times may differ from the original idea pitched in the suggestions subforum. Hopefully yhis will garner feedback that's more on topic once an idea has been selected for implementation. As opposed to suggestion topics, which may still discuss various different implementation methods long past a dev has picked the subject up.
  • Regular community votes!

    This isn't exactly new anymore, but I figured I'd mention this anyways. We've started running community feedback votes on certain development issues over the past month or two. You hopefully have seen and voted on a few of them. The idea is to break out of simply having largely the same group of people offer feedback on the forums and on Discord, and to see what the greater playerbase thinks on certain topics. Though it should be noted that this feedback is not ever binding, it will be taken into consideration when addressing issues around votes.

 


So. That should be it for now. If anyone has any questions about any of this, or wishes for elaboration, feel free to post down below.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...