[
https://issues.apache.org/jira/browse/WHIMSY-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17849364#comment-17849364
]
Shane Curcuru commented on WHIMSY-415:
--------------------------------------
No - unless you happen to have an "ah-ha, it might be this!" moment, it's not
worth working on now. Partly a reminder to myself to be extra careful creating
next month's agenda, and checking that reminders are only going to needed PMCs.
Thanks!
> /agenda/new fails to mark some reports due when calendar outdated
> -----------------------------------------------------------------
>
> Key: WHIMSY-415
> URL: https://issues.apache.org/jira/browse/WHIMSY-415
> Project: Whimsy
> Issue Type: Bug
> Components: BoardAgenda
> Reporter: Shane Curcuru
> Priority: Minor
>
> On Wednesday 22 May I hit whimsy.a.o/board/agenda/new to create a new agenda,
> but got several errors on the original screen, since the
> committers/board/calendar.txt file didn't have any further dates ready.
> Whimsy did guess at the correct third wednesday of the month, but I didn't
> check the rest of the details.
> I closed the whimsy window without pushing Post. Then I updated calendar.txt
> and waited a day.
> Coming back Thursday to /board/agenda/new, I pressed Post, and it sent out
> the normal reminders (and sent me a report).
> *BUG*
> Reminders went out to Aries and Struts, even though they had submitted
> reports in May. Struts in particular had missed April, so the PMC chair was
> really confused when they thought we hadn't accepted the May report (which we
> did).
> Not sure if this is reproduceable, may have been due to calendar.txt not
> having future dates, or may be because I used /agenda/new, but didn't Post,
> then came back later and did it all over again.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
