Todd, I may be the only one with tickets of this particular issue. Let me know how you want the metadata to be set. . .
There are sometimes doc tickets that cause changes to the wiki or web, but not to the CONDOR_SRC/ git repo. When I finish one of these tickets, I mark them as resolved, but there isn't an associated fixed version field, as they don't go into a release. If you desperately need a fixed version field for these tickets, then can we invent an appropriate string that will be well-known value? Thanks. Karen On 08/04/2014 11:30 AM, Todd Tannenbaum wrote:
Hi HTCondor developers - Folks have gotten a bit sloppy with the meta-fields in htcondor-wiki tickets. Please view the three below URLs - if any tickets assigned or created by you show up on the lists below, please fix the meta data. This info is important - we report it to NSF, we use version fields to be certain our version history is complete upon release, etc. I'd like these cleaned up today, it takes 5 seconds per ticket. Ask me if you have any questions. Thanks! Todd 1. The set of all code tickets that have been resolved but do not have a fixed version set. Could click on a commit and hit the [Branches] button to help jog your memory re when the fix happened. https://htcondor-wiki.cs.wisc.edu/index.cgi/rptview?rn=51 2. The set of all tickets with invalid/malformed version fields. https://htcondor-wiki.cs.wisc.edu/index.cgi/rptview?rn=34 3. Tickets with a "todo" type field are actions will not involve commits to the htcondor repository, such as changes to the web site. If they do require commits they should be ticket type defect or an enhance. https://htcondor-wiki.cs.wisc.edu/index.cgi/rptview?rn=60
_______________________________________________ HTCondor-devel mailing list [email protected] https://lists.cs.wisc.edu/mailman/listinfo/htcondor-devel
