The "Report a bug" link actually goes to the https://freedos.org/bugs/ page on the website. And that page says:
*>Bug tracker on GitLab* *>We discussed on the email list that we're trying to move bug tracking to GitLab. Please report bugs on this tracker: ..* (With a big blue button to "Report a bug" plus a link to "or report by email") And: *>Old tracker on SourceForge* *>Our old bug tracker is still on SourceForge. Please report new bugs on GitLab, but you can find the old bugs here: ..* (With just a link to "Old bug tracker") That's because long ago, we decided on the list to move to the GitLab bug tracker. So the intention is for folks to use GitLab to report bugs. And the link to the SF bug tracker is to provide visibility to the old bugs. Perhaps it would be best to remove the link to the SourceForge tracker from this page on our website, so people can't accidentally use the old tracker to report new bugs? The SF bug tracker would still exist, and we can still respond to bugs on the SF bug tracker, we just wouldn't link to it. That said, it's likely that some folks have the old SF bug tracker bookmarked so we should probably still add a "freedos14" category there anyway. And then we could recategorize old bugs for FreeDOS 1.4 that way too, which is a good way to tidy the bug list. On Thu, Jan 2, 2025, 4:29 AM Wilhelm Spiegl <wilhelm.spi...@mail.com> wrote: > Hi Jim, > I just noticed your announcement at freedos.org and saw that bugs can > still be reported via sourceforge. > Could you please add a group freedos14 at sourceforge bugtracker: > > https://sourceforge.net/p/freedos/bugs/ > > This would make it easier to find 1.4 related bugs in the future. > > Thx. > > Willi > > -- > Gesendet mit der mail.com Mail App > > > Am 01.01.25, 18:01 schrieb Jim Hall via Freedos-devel < > freedos-devel@lists.sourceforge.net>: >> >> This is EXCELLENT news! I installed it and things seem to work well so >> far (as expected, since this is an updated monthly test release, and I >> test every monthly test release). >> >> I've posted a news item about it on the FreeDOS website. I also >> updated the "Download" page with a big yellow box so interested folks >> can see the new FreeDOS 1.4 RC1. >> https://www.freedos.org/download/ >> >> >> >> On Wed, Jan 1, 2025 at 6:04 AM Jerome Shidel via Freedos-devel >> <freedos-devel@lists.sourceforge.net> wrote: >> > >> > The FreeDOS 1.4-RC1 Release Build (aka T2501) is now available at: >> > >> > >> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/test/ >> > >> > Please note, that as a “Release Candidate” the RBE does a couple >> > minor things a little different. Primarily, it does not swap out the >> > color theme for the FreeDOS installer. So unlike an Interim Test Build, >> > you will not see a black background in the main installer. Instead >> > you will see the blue background used on a release. >> > >> > Also, the RBE builds from the media using the “candidate” and/or >> > “master” project branches. Therefore any project or package updates >> > that are pushed to GitLab under an “unstable” branch will not >> > cause changes to the RC or eventual Final release of version 1.4. >> > >> > Furthermore, the online update repository for FreeDOS 1.4 (RC1 and >> > later) is now “officially” active. It has the latest version of the >> > packages from the RC1 build. It also contains the majority of packages >> > which are “download only” (for example, ClamAV) and not provided on >> > any of the Release Media. Also, the “unstable” download repository >> > has been purged and loaded with the packages for 1.4-RC1. >> > >> > >> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.4/pkg-html/index.html >> > >> > Following is a list of changes since FreeDOS 1.3. As I have mentioned >> > before, the RBE does some filtering on this list. I also preformed >> > some manual filtering to remove most general housekeeping, CI/CD and >> > NLS related commit messages. As a reminder, packages that are not >> > maintained on the GitLab Archive usually only get a “updated to >> > x.y.z” message when they are brought up to date. That could be a >> > simple update or one that contains many changes. For those, you need >> > to check inside the package for a changelog or check upstream. >> > >> > :-) >> >> [..] >> >> >> _______________________________________________ >> Freedos-devel mailing list >> Freedos-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freedos-devel >> >
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
