Disroot Changelog

Here you can follow changes to the platform. When there is a new update to any of the services on the platform here is where we coordinate the preparartion work and testing. Also here is where we keep the history of changes. The entire process has been made public so that not only disrooters can keep track of changes together with us core team, but also disrooters could participate in testing of new features helping us provide best possible solution to all of us. The repository is strictly dedicated to work, coordination and testing the updates, please do not post unrelated things here. If you have issue, suggestion, feedback you would like to share with us, please use the general purpose board at https://git.disroot.org/Disroot/Disroot-Project

Deployments

We run updates on disroot during a maintenance window on first Tuesday of the month. To be able to reach that deadline, we start preparting a month earlier.

We start the process by creating issues in this repository. The issues cover new software versions release by upstream developers and also significant changes rolled by us (eg. adding new feature in existing service, changing infrastructure related tasks,). In general anything worth mentioning in Changelog or tasks that require downtime and aren't critical in sense of urgency, is scheduled for the maintenance window. The only exeption is with security urgent updates. Those we try to push onto the platform as fast as possible.

Once service is scheduled for update, it goes through a "Deployment process" which we signal with several labels.

1. WIP is the stage of the process where sysadmins do the needed work to prepare the update for production.
2. Staging testing - Once sysadmins are ready with their work, they push the update onto a staging server. Staging server is a little test server we run a sort of disroot copy on. This is where the rest of the team as well as volounteers are testing the updates helping us find issues, bugs as well as test new features. We do our best to get service scheduled for update, two weeks before the maintenance window to give enough time for testers and sysadmins to fix anything found during the testing.
3. Ready for production - Once the testing team gives a green light for update, we prepare it and run updates on production servers for all the disrooters hungry for new stuff. As explained above, this is done first Tuesday of the month.

Below is a simple checklist to follow when testing services for updates:

Checklist

Etherpad

• Check if the service's frontend works
• Open an existing pad (eg. https://pad.morecats.net/p/test)
  • Check if the content of the pad exists
  • Check if you can type
  • Reload pad to see if you changes are still there
  • Check pad's history
• Create new pad and add text; reload the pad
• Check changelog for possible extra features: https://github.com/ether/etherpad-lite/releases (or you can find the link to the release version in the issue created in this repository)
• Note any possible feature highlight inside git issue on Changelog repo

Forgejo

• Check if the service's frontend works
• Log in using private mode
• Change themes
• Check if you can see issues, repos, milestones etc
• Comment on git issue (eg. in Changelog repo)
• Create git repo
• Check for possible extra feature highlight https://forgejo.org/news/ https://codeberg.org/forgejo/forgejo/src/branch/forgejo/RELEASE-NOTES.mode (or you can find the link to the release version in the issue created in this repository)

Webmail

• Check if the service's frontend works
• Login to webmail using your disroot credentials
• Check if emails load
• Send/Receive emails
• Check if your contacts are there
• Check for possible extra features worth mentioning: https://github.com/roundcube/roundcubemail/releases https://roundcube.net (or you can find the link to the release version in the issue created in this repository)

PrivateBin

• Check if the service's frontend works
• Upload paste
• Read paste
• Set to delete on first read
• Add comments
• Read comments
• Check for possible extra features worth mentioning:
  • https://github.com/PrivateBin/PrivateBin/releases
  • https://privatebin.info/category/news.html

(or you can find the link to the release version in the issue created in this repository)

Lufi

• Check if the service's frontend works
• Check if previously uploaded files (if not expired) loads
• Upload new file with exp data
• Upload new file with password
• Upload new file burned on first download
• Check if file deletes on first download
• Check for possible features worth mentioning: https://framagit.org/fiat-tux/hat-softwares/lufi/-/releases (or you can find the link to the release version in the issue created in this repository)

SearXNG

• Check if the service's frontend works
• Check if queries return results for text and image
• Check if dashboard loads links to services correctly
• Check for new features worth mentioning: (missing)

Cryptpad

• Check if the service's frontend works
• Create a pad like text, speadsheet, presentation, etc.
• Check if you can log in
• Check if you can view old existing pads and edit them
• Check if you can create a team (if you haven't)
• Check if you can access documents in a team
• Check if you can read and post commments
• Check for new features worth mentioning: https://github.com/cryptpad/cryptpad/releases (or you can find the link to the release version in the issue created in this repository)

Akkoma

• Check if the service's frontend works
• Check if you can log in
• Check if you can read posts of others
• Check if you can post
• Check if federation works (if you can see your post from other instances and the otherway around) << This is still WIP so don't test
• Check for possible features worth highlighting: https://meta.akkoma.dev/c/releases/7 (or you can find the link to the release version in the issue created in this repository)

LibreTranslate

• Check if the service's frontend works
• Make some translations
• Check for possible new features worth highlighting: https://github.com/LibreTranslate/LibreTranslate/releases (or you can find the link to the release version in the issue created in this repository)

Lemmy

• Check if the service's frontend works
• Check if you can read existing posts
• Check if you can submit to community
• Check if you can read posts from a community
• Check if you can unsubscribe from community
• Check if you can create a post:
• Link to a page
• Just text/image
• Check if you can post a comment under a thread
• Check if federation works (if you can see your post from other instances and the otherway around) << This is still WIP so don't test
• Check for possible new features worth highlighting: https://join-lemmy.org/news (or you can find the link to the release version in the issue created in this repository)

Movim

• Check if the service's frontend works
• Check if you can login to movim
• Check if roster is loaded and client joins all rooms
• Check if you can read and post into a room but also in 1on1 chats
• Check if OMEMO works for both MUC and 1on1
• Check if you can upload files
• Check if you can open uploaded files
• Check if avatars display correctly
• Check for possible new features worth highlighting: (grrrr cannot paste link to community page)

Get involved

If you would like to participate in the testing process, please feel free to reach out to us. The more people to test and give feedback the better. If you have suggestions on how to improve the check list or the process, feel free to suggest them by doing a pull request.