[wildfly-dev] WildFly Core component upgrade coordination

[David M. Lloyd]

There are a few things we can do just in JIRA alone, like setting 
priority to "Blocker", and setting a dependency to the core upgrade 
issue, and then commenting on the core upgrade issue.  Or you could do 
it in the PR with a comment (or a tag maybe?).

On 10/15/2014 04:04 AM, Darran Lofthouse wrote:
> I think this takes us back to one point to double check.
>
> Obviously any engineer can raise a component upgrade Jira in the
> WildFly-Core project, sometimes there is no immediate rush but other
> times until the update is there they are blocked from continuing their
> work in WildFly - what is the best way to indicate the latter?
>
> On 13/10/14 11:33, Darran Lofthouse wrote:
>> On 10/10/14 23:37, Stuart Douglas wrote:
>>> I meant in the general case, not this week in particular :-)
>>
>> +1 I think from a predictability perspective for the majority of
>> engineers this means that it is the start of the week that they see
>> Wildfly with an updated core which overall is what we are trying to meet.
>>
>>> Stuart
>>>
>>> David M. Lloyd wrote:
>>>> We just did a release Tuesday, so why don't we start next week instead?
>>>>
>>>> On 10/10/2014 04:28 PM, Stuart Douglas wrote:
>>>>> If no one else gets to I can do it first thing Monday (Sunday for
>>>>> everyone else).
>>>>>
>>>>> Stuart
>>>>>
>>>>> Jason Greene wrote:
>>>>>> I don’t think Stuart officially volunteered? Don’t forget that our
>>>>>> Friday is his Saturday, and his Friday is our Thursday.
>>>>>>
>>>>>> Brain volunteered though. I was planning on doing it, but if he (or
>>>>>> anyone else is up for thats great), he (or anyone else) can continue
>>>>>> to charge me beer debt :)
>>>>>>
>>>>>> On Oct 10, 2014, at 8:38 AM, David M. Lloyd<david.lloyd at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> OK so it seems like we have a sort of consensus here. To summarize:
>>>>>>>
>>>>>>> • WildFly Core releases will happen at some nonspecific time on each
>>>>>>> Friday (but only if there have actually been changes that warrant a
>>>>>>> release, of course, i.e. there's something that would block somebody's
>>>>>>> progress in some area)
>>>>>>> • Release will be done by Stuart or another core team member as
>>>>>>> appropriate/needed
>>>>>>> • Merge team will make a best effort to merge everything that is marked
>>>>>>> ready-for-merge by Thursday end-of-day
>>>>>>> • People submitting changes should have no reasonable expectation that
>>>>>>> last minute changes will be merged unless they are trivial
>>>>>>> • All WildFly Core update JIRAs will be parented to this JIRA:
>>>>>>> https://issues.jboss.org/browse/WFLY-3956
>>>>>>> • Since the last release was this past Tuesday, we'll start this no
>>>>>>> sooner than next week
>>>>>>>
>>>>>>> I think that's about it. I'm sure you all will correct me if I missed
>>>>>>> something. :)
>>>>>>> --
>>>>>>> - DML
>>>>>>> _______________________________________________
>>>>>>> wildfly-dev mailing list
>>>>>>> wildfly-dev at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>>>
>>>>>> --
>>>>>> Jason T. Greene
>>>>>> WildFly Lead / JBoss EAP Platform Architect
>>>>>> JBoss, a division of Red Hat
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> wildfly-dev mailing list
>>>>>> wildfly-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

-- 
- DML