[wildfly-dev] WildFly Core component upgrade coordination

[Darran Lofthouse]

Maybe something with labels, if a PR is labelled a blocker no releases 
are performed until it is in?

On 08/10/14 13:40, Kabir Khan wrote:
> I think I prefer the 'human interaction' one best. What if the automatic one does the release, just as someone is attempting to merge a bunch of PRs which should be in the release? Although that might be a corner case :-P
> On 8 Oct 2014, at 13:24, Tomaž Cerar <tomaz.cerar at gmail.com> wrote:
>
>> I had some discussions with Jason on how we could automate
>> time boxed releases by just having a button in CI that would perform it.
>> So we at least have a bit of human interaction.
>>
>> We could also have it done automatically by CI every week on schedule that shouldn't be a big deal to do.
>> If we do that we should have "indexed" build versions like 1.0.0.Beta1-01, 1.0.0.Beta1-02 etc...
>>
>> --
>> tomaz
>>
>> On Wed, Oct 8, 2014 at 12:31 PM, Darran Lofthouse <darran.lofthouse at jboss.com> wrote:
>> I don't know if it needs to be a short timebox say weekly or better if
>> on-demand e.g. if an engineer is working on an issue in both core and
>> wildfly they request a core release and upgrade to continue their work.
>>
>> At the same time I think we do need the Jiras as David suggests to track
>> what we actually needs, unfortunately this does create some additional
>> maintenance as these need updating after each release.
>>
>> On 08/10/14 07:21, Heiko Braun wrote:
>>> Does it help to put Core on a time boxed schedule?
>>>
>>> On 07 Oct 2014, at 22:07, Stuart Douglas <stuart.w.douglas at gmail.com
>>> <mailto:stuart.w.douglas at gmail.com>> wrote:
>>>
>>>> I don't really think that we need this level of process around a Wildfly
>>>> Core release. I think that we should just be doing these releases fairly
>>>> frequently, and if some work misses the release then there is always
>>>> another release coming up in the near future.
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>