Platform updates: Recent pushes

In recent weeks, we’ve pushed out a number of new releases, featuring fixes and feature enhancements. Here’s several of these changes.

[#2242] – Adds a “release technician” role to projects, so that you can have non-admins make file releases. To access this feature, go to Admin → Tools, and select ‘Release Technicians’.

This feature was available in Classic projects, but prior to this change, only project admins on new/upgraded projects were able to upload to the file release area. This gives a way to have better defined division of tasks on your project.

[#4936] – Adds resolution to ticket status. In SourceForge classic, the status and the resolution (ie, “Closed”, and “WontFix”) were tracked as two separate fields. In the new SourceForge tracker, there’s just one status. This fix ensures that the two old fields are migrated into the new field and no information is lost.

[#5260] – On migration, close milestones that contain all closed tickets. In SourceForge classic, milestones didn’t have an open/closed status, but they do in the new version. So, when trackers are migrated, we now mark milestones as closed if all of the tickets in them are closed. This avoids resurrecting past milestones on migration.

If you want to see what’s scheduled for upcoming releases, follow the next milestone, and don’t forge to vote for tickets that you’d like to see prioritized, or make new feature requests in the Feature Requests ticket queue.

Tags: , , ,

Comments are closed.