| 1 |
On Fri, Jan 30, 2015 at 06:22:31PM -0500, Rich Freeman wrote: |
| 2 |
> On Fri, Jan 30, 2015 at 6:06 PM, William Hubbs <williamh@g.o> wrote: |
| 3 |
> > |
| 4 |
> > When should ewarns vs news items be used to inform users about changes? |
| 5 |
> > I'm not asking for a policy, just thoughts about when one or the other |
| 6 |
> > should be used. |
| 7 |
> > |
| 8 |
> |
| 9 |
> IMHO it is almost pointless to issue news this far after the event. |
| 10 |
> Just about anybody impacted will have already broken their systems and |
| 11 |
> fixed them by now. |
| 12 |
|
| 13 |
That's what I would have thought too, but I was specifically asked to |
| 14 |
put together a news item by another qa member; the bug was escalated by |
| 15 |
the reporter, and I didn't have time to do it the day I was asked. |
| 16 |
|
| 17 |
> The big advantage of news is that you can issue it a few days BEFORE |
| 18 |
> releasing the change. |
| 19 |
|
| 20 |
I guess I'm trying to figure out an idea of what kinds of changes should |
| 21 |
be announced beforehand. |
| 22 |
|
| 23 |
According to some, my change should have been anounced beforehand, but I |
| 24 |
guess I thought that users are supposed to read their ewarns and they |
| 25 |
would catch this. |
| 26 |
|
| 27 |
William |
Archives