You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by "Dave Fisher (JIRA)" <ji...@apache.org> on 2019/04/10 02:57:00 UTC

[jira] [Commented] (WHIMSY-118) Add releases cross-check between board reports and DOAP files

    [ https://issues.apache.org/jira/browse/WHIMSY-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814001#comment-16814001 ] 

Dave Fisher commented on WHIMSY-118:
------------------------------------

All releases are supposed to be available on dist.apache.org.

For the incubator clutch we read all the releases via:
https://svn.apache.org/repos/asf/incubator/public/trunk/clutch2.py


> Add releases cross-check between board reports and DOAP files
> -------------------------------------------------------------
>
>                 Key: WHIMSY-118
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-118
>             Project: Whimsy
>          Issue Type: New Feature
>            Reporter: Shane Curcuru
>            Priority: Minor
>
> PMC efforts to keep DOAP files (which generate a number of useful webpages) updated vary widely in quality and timeliness.
> One simple way to see which PMCs are updating DOAPs is to crosscheck board reports of release activity with that PMC's DOAP file(s).  Projects that use the reporter.a.o tool make this easy in board reports:
> {{## Releases: 
>    
>  - Last release was 2.4.2 on Wed Apr 15 2015 }}
> Highlighting board reported releases that aren't found in DOAP files would be useful at some point in the process - probably not during the meeting, but perhaps after the meeting in an automated, targeted email that points out the new releases not yet marked in DOAPs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)