| ▲ | Gitea 28.0(blog.gitea.com) |
| 44 points by porridgeraisin an hour ago | 15 comments |
| |
|
| ▲ | wasting_time an hour ago | parent | next [-] |
| For anyone curious why they should choose one over the other: https://forgejo.org/compare-to-gitea/ |
| |
| ▲ | nightpool 30 minutes ago | parent | next [-] | | Unfortunately, seems like this is Forgejo's best suggestion on how to compare the two: https://i.imgur.com/j1665QR.png. Not sure that page helps much if you're not already bought in to a free-software-absolutist mindset | |
| ▲ | DASD an hour ago | parent | prev [-] | | Thanks! Currently going through this decision process myself. | | |
| ▲ | GrayShade an hour ago | parent [-] | | I suggest browsing through the release notes of the last 4-5 versions to see what you like more. | | |
| ▲ | tjoff 33 minutes ago | parent [-] | | I'd argue project values, license and health are way more important. |
|
|
|
|
| ▲ | ThePinion an hour ago | parent | prev | next [-] |
| > This release contains security fixes. To give everyone time to upgrade, details will be added to this post in about a week. Is this something that has been happening for a while or a new trend due to LLM concerns? I understand the reasoning, it just made me do a double take because I haven't really seen that before. |
| |
| ▲ | techknowlogick 6 minutes ago | parent | next [-] | | (bias note: I am a project lead of Gitea) this approach is based on what peertube has been doing, and is being attempted as an alternative approach to what we've been doing previously due to feedback we've been receiving from the community. | |
| ▲ | QuantumNomad_ 37 minutes ago | parent | prev | next [-] | | With Gitea specifically or in general? A lot of different software has silently included security fixes in updates combined with other changes and then later revealed what security fixes were made or stayed quiet about it all together, since long before LLMs could analyze changes. Security researchers and malware authors would reverse engineer software updates of proprietary software, and scrutinise source code changes of open source projects to find secretly shipped security fixes. | |
| ▲ | stackghost 36 minutes ago | parent | prev [-] | | Bizarre policy. Any bad guys unaware of the security implications are analyzing the patch diffs as we speak, so this seems nonsensical to me. | | |
|
|
| ▲ | MitPitt an hour ago | parent | prev | next [-] |
| they skipped 26 major versions, ai is truly amazing |
| |
| ▲ | layer8 an hour ago | parent [-] | | > Gitea drops the historical 1. prefix from its version numbers, so this release is 28.0.0 rather than 1.28.0. |
|
|
| ▲ | godbox 39 minutes ago | parent | prev [-] |
| Holy shit. They went from 1.27.3 to 28.0.0. These guys are hauling ass |
| |
