FS#63333 - [plan9port] Choose a new git commit even though there has not been a release?
Attached to Project:
Community Packages
Opened by Neven Sajko (Neven) - Wednesday, 31 July 2019, 19:09 GMT
Last edited by David Runge (dvzrv) - Saturday, 31 August 2019, 14:22 GMT
Opened by Neven Sajko (Neven) - Wednesday, 31 July 2019, 19:09 GMT
Last edited by David Runge (dvzrv) - Saturday, 31 August 2019, 14:22 GMT
|
Details
Maybe make a new Archlinux release, even though upstream
refuses to tag commits? 2017 was a long time ago.
|
This task depends upon
Closed by David Runge (dvzrv)
Saturday, 31 August 2019, 14:22 GMT
Reason for closing: Won't fix
Additional comments about closing: Please use out-of-date flagging.
Saturday, 31 August 2019, 14:22 GMT
Reason for closing: Won't fix
Additional comments about closing: Please use out-of-date flagging.
Comment by
Eli Schwartz (eschwartz) -
Wednesday, 31 July 2019, 19:26 GMT
I sort of feel like this (project with no stable release that
periodically builds from the latest git commits) is a perfectly
reasonable time to flag a package as out of date with the note
"there are lots of new commits in the past several years".