You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of having to decide when to retire fantasy consoles that aren't actively developed, we could just add a column with the year of the last update. That way, working consoles could stay listed while also giving readers a bit of a clue which ones are actively developed/supported.
What do you all think? I started working on this but realized I should probably ask before I go to the trouble of looking them all up. I've been going by Github activity (for open source projects) or release notes/history (for closed source projects).
The text was updated successfully, but these errors were encountered:
So we want to convey something hopefully useful to the user, but we don't have an automated way to track actual releases from the projects.
My thoughts are to tackle this two ways:
Have status+date indicators: Something along the lines of "Project Status" and "Status Last Updated"
Project status could have life-cycle indicators like: Alpha | Beta | Stable | Mature | Maintenance | Archived or somesuch.
And statuses could have sub-indicators like :(Stalled) | (Active) | (Usable)
Have a quick link on each project that opens a "Create Issue" dialog with a Status Update template, making it easy for users to report status changes for a project.
Instead of having to decide when to retire fantasy consoles that aren't actively developed, we could just add a column with the year of the last update. That way, working consoles could stay listed while also giving readers a bit of a clue which ones are actively developed/supported.
What do you all think? I started working on this but realized I should probably ask before I go to the trouble of looking them all up. I've been going by Github activity (for open source projects) or release notes/history (for closed source projects).
The text was updated successfully, but these errors were encountered: