incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Schaefer <joe_schae...@yahoo.com>
Subject Re: Reporting due dates
Date Fri, 02 Aug 2013 21:39:10 GMT
I run the script by hand because it requires a password for the svn checkouts.

If you need it to run a full week prior to the podling reports due date, just ask.
Sent from my iPhone

On Aug 2, 2013, at 5:33 PM, Marvin Humphrey <marvin@rectangular.com> wrote:

> Greets,
> 
> "Marvin" sent out report reminders earlier today.  Here's my proposed timeline
> for preparing our August report:
> 
>    Wed August 7 -- Podling reports due by end of day
>    Tue August 13 -- Mentor signoff due by end of day
>    Tue August 13 -- Shepherd reviews due by end of day
>    Tue August 13 -- Summary due by end of day
>    Wed August 14 -- IPMC Chair submits report (on time!)
>    Wed August 21 -- Board meeting
> 
> Note that this month's schedule differs from the one I laid out for our July
> report, primarily because of a mistake I made last month -- I had thought that
> "Marvin" gave podlings a week and a half to submit their reports rather than
> only five days.  This time I'm proposing that we adhere to Marvin's compressed
> schedule -- so podling reports are due in less than a week.
> 
> In the future, I would like to send out podling reminders one week earlier.
> That way, podlings will get the same amount of time that TLPs get, while still
> allowing the IPMC several days for Mentor signoff and Shepherd review before
> the Chair submits the report -- on time for a change, instead of a couple days
> late as has been the Incubator's bad habit.
> 
> I believe that changing the timing for reminders will require modifications to
> the reminders.pl script (a.k.a. "Marvin"), which is tricky because it looks
> like it's hard to run without actually sending email.
> 
>  https://svn.apache.org/repos/infra/infrastructure/trunk/tools/board_reminders
> 
> What I'm tempted to do is refactor some of the code in reminders.pl into a
> handful of modules which can be run in non-production mode, making it
> possible to write some tests and make changes with greater confidence.
> Although this would be a fair amount of work, it's probably less in the long run
> than making blind, untestable changes to the current monolithic script and
> then cleaning up the huge mess when things go wrong (e.g. because every TLP
> receives a reminder with the wrong date).
> 
> Thoughts?
> 
> Marvin Humphrey
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Mime
View raw message