Opened 17 years ago
Closed 16 years ago
#32 closed task (fixed)
email changelogs
Reported by: | VincentMcIntyre | Owned by: | VincentMcIntyre |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | miriad4cabb project | Version: | |
Keywords: | changelog, email | Cc: | |
Estimated Number of Hours: | 8 | Add Hours to Ticket: | 0 |
Billable?: | no | Total Hours: | 9.0 |
Description
We should email out a summary of changes at regular intervals, probably 1 week is ok. This ticket is to remind us to configure this.
Change History (5)
comment:1 Changed 17 years ago by
Keywords: | removed |
---|
comment:2 Changed 17 years ago by
Keywords: | changelog email → changelog, email |
---|
comment:3 Changed 17 years ago by
Billable?: | unset |
---|---|
Estimated Number of Hours: | → 8 |
Status: | new → assigned |
comment:4 Changed 17 years ago by
Component: | Subversion → miriad4cabb project |
---|
comment:5 Changed 16 years ago by
Add Hours to Ticket: | → 9 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Total Hours: | 0.0 → 9.0 |
This got done as follows:
Frpm phoenix:/etc/crontab
we run /local/sbin/svn_log_summary -p /miriad
once a week.
The mail goes to a list of individuals at present, it would be better to use an exploder/majordomo.
Allowing about 6h for writing and debugging the script; 3h reading about the possible options and picking one.
Note: See
TracTickets for help on using
tickets.
estimate time - 8h. Fair bit of reading svn doco needed.