Draft proposal: JEP 2.0
jonathan.gibbons at oracle.com
Thu Apr 17 00:19:00 UTC 2014
On 04/15/2014 02:09 PM, Jon Masamitsu wrote:
>> The JEP owner is expected to update the Alert Status on a weekly
>> basis once a JEP is Funded and active development work is under way.
>> If the Alert Status is Yellow or Red then the owner must use the
>> Alert Reason field to explain what is required to return the Status
>> to Green. This way everyone working on the release or otherwise
>> interested in the JEP can easily understand its current state.
> This sounds a lot like the status I have to report to my managers.
> Except that
> I talk to my manager about how things are going. This I have to
> compose and
> publish. Sorry but it's something that I'll easily forget to do.
I think the point is that this will supersede some of the ad-hoc
infrastructure we currently use to track project progress, so this is
not something that you'll forget to do: it is simply a formalized
replacement of what you do today. It is just an "enum"
(green/yellow/red) and a text field. I doubt that folk are expecting you
to write an essay each week for the Alert Reason field.
The good news is that by having the alert status in a system like JIRA,
we can do intelligent queries about work in progress to create useful
summary reports, rather than working with miscellaneous ad-hoc
infrastructure (i.e. wiki pages, uugh!)
More information about the discuss