IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 26 January 2022 (all times are UTC)
| 06:25 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving) | |
| 06:47 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 11:58 | parlos has joined IRC (parlos!~pal@146.247.147.166) | |
| 12:23 | lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-251.static.oncabo.net.br) | |
| 13:15 | woernie has left IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
| 13:16 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
| 13:32 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
| 13:32 | woernie has joined IRC (woernie!~werner@p5b296cc2.dip0.t-ipconnect.de) | |
| 14:21 | parlos has left IRC (parlos!~pal@146.247.147.166, Quit: Konversation terminated!) | |
| 17:05 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 17:35 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e) | |
| 19:00 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 19:00 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 19:07 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 19:07 | Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas) | |
| 21:19 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 21:59 | <kvaps[m]> <alkisg> "Hi kvaps , github releases..." <- No, they don't. The tar.gz files with sources will be generated from tags automatically.
| |
| 21:59 | Additionally you can upload some binaries, but it does not required at all
| |
| 22:00 | <alkisg> kvaps: the tar.gz files are already uploaded due to tags
| |
| 22:00 | And I don't have any binaries to upload
| |
| 22:00 | So what am I supposed to do in releases?
| |
| 22:05 | <kvaps[m]> alkisg: Just go into https://github.com/ltsp/ltsp/tags choose the tag you want
| |
| 22:05 | - Click three dots on the right side and choose: "Create release"
| |
| 22:05 | - Fill name of the release (I usually use the same name as tag)
| |
| 22:05 | - Then you can fill the changelog (markdown is also supported)
| |
| 22:05 | - Click "Publish release" button
| |
| 22:05 | - Job is done 🙂
| |
| 22:05 | <alkisg> kvaps: but why would I do that, what purpose does it serve?
| |
| 22:06 | I can understand releases for projects that ship binary files, but for ltsp which doesn't ship any, why would I go though that trouble, how does it help our users?
| |
| 22:07 | <kvaps[m]> Ah there is also cool feature "Auto-generate release notes" which will fill in information accoring to the merged Pull Requests
| |
| 22:08 | <alkisg> The release notes are the same as in debian/changelog, i.e. a summary of the most significant things; there's no duplicated work for that part, it's just a copy/paste
| |
| 22:08 | <kvaps[m]> > I can understand releases for projects that ship binary files, but for ltsp which doesn't ship any, why would I go though that trouble, how does it help our users?
| |
| 22:08 | Because releases are supposed to be in releases, you don't have to hold specific issue for announcing the new releases. This is useful because you can subscribe only on releases and get notifications when you make new release.
| |
| 22:09 | * kvaps[m] uploaded an image: (34KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/lspMSOBqVNAbZKtcrxicCSWp/%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5.png > | |
| 22:11 | <alkisg> Got it. Thanks, if I remember correctly it'll also allow me to create releases for past tags; I'll do them all in the summer when I'll have some free time
| |
| 22:12 | * kvaps[m] uploaded an image: (12KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/DscdeocElBiUvrfSnIKNGRKk/%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B5.png > | |
| 22:12 | <kvaps[m]> Also you can easley get infromation about the latest version of project and simple access changelog from the main page of the project
| |
| 22:13 | > Got it. Thanks, if I remember correctly it'll also allow me to create releases for past tags; I'll do them all in the summer when I'll have some free time
| |
| 22:13 | Not sure but I think that older releases will shown on top if you'll cut them after the newer ones
| |
| 22:13 | <alkisg> I think so too, that's why I'll start from the oldest ones ;)
| |
| 22:14 | I tried it a few years back but at that point there was no "notify for releases" option; from what google says, it was added in 2019
| |
| 22:14 | So I deleted the releases and created the #1 issue....
| |
| 22:14 | <kvaps[m]> This is actually done to support few branches of development
| |
| 22:14 | Got it :)
| |
| 22:14 | Good luck with that!
| |
| 22:15 | <alkisg> Thanks for the hint! :)
| |