Update of bug #64353 (group groff):
Status: Postponed => Need Info
Assigned to: gbranden => deri
_______________________________________________________
Follow-up Comment #8:
[comment #5 comment #5:]
> This is fine, but it should wait until gropdf has been cherry picked from my
> branch to master, when Branden is ready. I hope I won't have to maintain two
> different versions for long, for example, Colin Watson's reproducible build
> patch would not apply against the new gropdf, I had to roll my own.
Hi Deri, I realize your "gropdf-ng" still exists and last I recall there's
"just one more thing" (à la Columbo) that needs to be done with the master
branch before the "gropdf-ng" branch can be deleted (though I don't remember
what it is--maybe it's the _gropdf_ documentation work that I have as 1.24
release goals).
In any case, is that one last thing still gating _this_ ticket?
I'm asking because nowadays we use "Postponed" for things that _could_ be
worked on immediately, but aren't due to scheduling concerns, and bug
dependencies to handle unsatisfied prerequisites. Savannah's come a long way
in the past 2½ years in helping us handle dependencies and expose the
meanings of ticket fields to mere mortal users (not just group
administrators).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64353>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
