6:21 p.m.
If you are assigned a JIRA for WildFly that requires a change to WildFly
Core (either a direct fix or a component upgrade), there (obviously)
needs to be a WildFly Core release and upgrade into WildFly proper
before the change can be completed. But because we're all asynchronous
here, coordination is something of a problem.
So, to organize things a bit, I've opened
https://issues.jboss.org/browse/WFLY-3945 for upgrading WildFly Core to
1.0.0.Alpha9.
If you have a WFCORE task or component upgrade that you think should be
finished before the upgrade happens, add the corresponding JIRA as a
dependency to that issue. If a WFLY task is blocked waiting for the
WFCORE upgrade, add that task as a dependent (in other words, add
WFLY-3945 as a dependency to that task; you can do it either way though).
If the list gets too large, we'll have a discussion about splitting the
work between Alpha9 and Alpha10 (or whatever is next).
Keeping the work organized around this issue will remove some of the
confusion around what needs updating and when, and why.
--
- DML
10:07 p.m.
I think that a big problem with this approach is that there is always
going to be another task that should be done and another reason to hold
the core release by just a few more days.
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.
I think that a JIRA that tracks what is waiting on the next WF core
release is a good idea, as it lets us see what is blocked waiting on the
next release, however I don't think we should be holding up a core
release based on work in the pipeline.
Stuart
David M. Lloyd wrote:
If you are assigned a JIRA for WildFly that requires a change to
WildFly
Core (either a direct fix or a component upgrade), there (obviously)
needs to be a WildFly Core release and upgrade into WildFly proper
before the change can be completed. But because we're all asynchronous
here, coordination is something of a problem.
So, to organize things a bit, I've opened
https://issues.jboss.org/browse/WFLY-3945 for upgrading WildFly Core to
1.0.0.Alpha9.
If you have a WFCORE task or component upgrade that you think should be
finished before the upgrade happens, add the corresponding JIRA as a
dependency to that issue. If a WFLY task is blocked waiting for the
WFCORE upgrade, add that task as a dependent (in other words, add
WFLY-3945 as a dependency to that task; you can do it either way though).
If the list gets too large, we'll have a discussion about splitting the
work between Alpha9 and Alpha10 (or whatever is next).
Keeping the work organized around this issue will remove some of the
confusion around what needs updating and when, and why.
11:24 p.m.
Yeah that wasn't really my intent, it's more of an advisory thing. The
point is to have the data in the issue so that it's always clear what's
going on around the release. The dependencies can always be updated to
a later release if a core release needs to be done before 100% of its
prerequisites are done. On the other hand, if you (or whomever) sees
that there's something that is almost ready, you might decide to
coordinate with that person. The important thing is to have the
information handy.
On 10/07/2014 03:07 PM, Stuart Douglas wrote:
I think that a big problem with this approach is that there is
always
going to be another task that should be done and another reason to hold
the core release by just a few more days.
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.
I think that a JIRA that tracks what is waiting on the next WF core
release is a good idea, as it lets us see what is blocked waiting on the
next release, however I don't think we should be holding up a core
release based on work in the pipeline.
Stuart
David M. Lloyd wrote:
> If you are assigned a JIRA for WildFly that requires a change to WildFly
> Core (either a direct fix or a component upgrade), there (obviously)
> needs to be a WildFly Core release and upgrade into WildFly proper
> before the change can be completed. But because we're all asynchronous
> here, coordination is something of a problem.
>
> So, to organize things a bit, I've opened
> https://issues.jboss.org/browse/WFLY-3945 for upgrading WildFly Core to
> 1.0.0.Alpha9.
>
> If you have a WFCORE task or component upgrade that you think should be
> finished before the upgrade happens, add the corresponding JIRA as a
> dependency to that issue. If a WFLY task is blocked waiting for the
> WFCORE upgrade, add that task as a dependent (in other words, add
> WFLY-3945 as a dependency to that task; you can do it either way though).
>
> If the list gets too large, we'll have a discussion about splitting the
> work between Alpha9 and Alpha10 (or whatever is next).
>
> Keeping the work organized around this issue will remove some of the
> confusion around what needs updating and when, and why.
--
- DML
8:21 a.m.
Does it help to put Core on a time boxed schedule?
On 07 Oct 2014, at 22:07, Stuart Douglas <stuart.w.douglas(a)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.
12:31 p.m.
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(a)gmail.com
<mailto:stuart.w.douglas@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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:24 p.m.
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(a)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(a)gmail.com
> <mailto:stuart.w.douglas@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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:38 p.m.
How about a timestamp instead of an index, at a glance you can see how
old the current core actually is.
On 08/10/14 13:24, Tomaž Cerar 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(a)jboss.com <mailto:darran.lofthouse@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(a)gmail.com
<mailto:stuart.w.douglas@gmail.com>
> <mailto:stuart.w.douglas@gmail.com
<mailto:stuart.w.douglas@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(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:40 p.m.
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(a)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(a)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(a)gmail.com
> <mailto:stuart.w.douglas@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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:41 p.m.
Also, it makes it easier to e.g. synchronise for the rare cases when incompatible changes
are made to core requiring wildfly fixes.
On 8 Oct 2014, at 13:40, Kabir Khan <kabir.khan(a)jboss.com> 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(a)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(a)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(a)gmail.com
>> <mailto:stuart.w.douglas@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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:43 p.m.
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(a)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(a)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(a)gmail.com
>> <mailto:stuart.w.douglas@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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
4:57 p.m.
Just telling people "hey I'm releasing core in a day or two" is already
10x better than the current status quo.
On 10/08/2014 07:40 AM, 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(a)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(a)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(a)gmail.com
>> <mailto:stuart.w.douglas@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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
- DML
5 p.m.
that still doesnt solve the problem on "when" next release is.
as people that need to do work across both repos need to know this info.
Current state is just too unknown and annoyng if you need to do something
in core and then also in full to make it work.
not to even add to the mix that your PR *needs* to break something in full,
at least until your PR for full is also merged.
On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd <david.lloyd(a)redhat.com>
wrote:
Just telling people "hey I'm releasing core in a day or
two" is already
10x better than the current status quo.
On 10/08/2014 07:40 AM, 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(a)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(a)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(a)gmail.com
>>> <mailto:stuart.w.douglas@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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
- DML
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
5:01 p.m.
I'll take whatever I can get. :-)
On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
that still doesnt solve the problem on "when" next release
is.
as people that need to do work across both repos need to know this info.
Current state is just too unknown and annoyng if you need to do
something in core and then also in full to make it work.
not to even add to the mix that your PR *needs* to break something in
full, at least until your PR for full is also merged.
On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd <david.lloyd(a)redhat.com
<mailto:david.lloyd@redhat.com>> wrote:
Just telling people "hey I'm releasing core in a day or two" is
already
10x better than the current status quo.
On 10/08/2014 07:40 AM, 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(a)gmail.com
<mailto:tomaz.cerar@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(a)jboss.com <mailto:darran.lofthouse@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(a)gmail.com
<mailto:stuart.w.douglas@gmail.com>
>>> <mailto:stuart.w.douglas@gmail.com
<mailto:stuart.w.douglas@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(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>>wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>> _______________________________________________
>> wildfly-dev mailing list
>>wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
>wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
- DML
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
- DML
10:26 p.m.
I think the best way to deal with this is just a time boxed release, say
every Friday afternoon. That way there is no surprises, and if a PR is
not ready then it can go into next weeks release.
I don't think automation is a good idea, there are to many things that
can go wrong.
Stuart
David M. Lloyd wrote:
I'll take whatever I can get. :-)
On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
> that still doesnt solve the problem on "when" next release is.
>
> as people that need to do work across both repos need to know this info.
> Current state is just too unknown and annoyng if you need to do
> something in core and then also in full to make it work.
> not to even add to the mix that your PR *needs* to break something in
> full, at least until your PR for full is also merged.
>
>
>
> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
> <mailto:david.lloyd@redhat.com>> wrote:
>
> Just telling people "hey I'm releasing core in a day or two" is
already
> 10x better than the current status quo.
>
> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
> >>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >>>
> >> _______________________________________________
> >> wildfly-dev mailing list
> >>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >>
> >> _______________________________________________
> >> wildfly-dev mailing list
> >>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >
> >
> > _______________________________________________
> > wildfly-dev mailing list
> >wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
> >
>
> --
> - DML
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
10:44 p.m.
I agree, the amount of effort required getting automation working
*correctly* is going to exceed the amount of work it would save. Doing
releases by hand is easy enough.
On 10/08/2014 03:26 PM, Stuart Douglas wrote:
I think the best way to deal with this is just a time boxed release,
say
every Friday afternoon. That way there is no surprises, and if a PR is
not ready then it can go into next weeks release.
I don't think automation is a good idea, there are to many things that
can go wrong.
Stuart
David M. Lloyd wrote:
> I'll take whatever I can get. :-)
>
> On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
>> that still doesnt solve the problem on "when" next release is.
>>
>> as people that need to do work across both repos need to know this info.
>> Current state is just too unknown and annoyng if you need to do
>> something in core and then also in full to make it work.
>> not to even add to the mix that your PR *needs* to break something in
>> full, at least until your PR for full is also merged.
>>
>>
>>
>> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
>> <mailto:david.lloyd@redhat.com>> wrote:
>>
>> Just telling people "hey I'm releasing core in a day or two"
is
>> already
>> 10x better than the current status quo.
>>
>> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
>> >>>
>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >>>
>> >> _______________________________________________
>> >> wildfly-dev mailing list
>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >>
>> >> _______________________________________________
>> >> wildfly-dev mailing list
>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >
>> >
>> > _______________________________________________
>> > wildfly-dev mailing list
>> >wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >
>>
>> --
>> - DML
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>
--
- DML
11:24 p.m.
On Wed, Oct 8, 2014 at 10:44 PM, David M. Lloyd <david.lloyd(a)redhat.com>
wrote:
I agree, the amount of effort required getting automation working
*correctly* is going to exceed the amount of work it would save.
not really agreeing on this one, as long as maven release plugin works (and
it does) this is matter of invoking 3 maven operations.
which can be done by anyone with necessary permissions.
If release for whatever reason cannot be done that simple, that is another
problem that needs to be addressed.
2:55 p.m.
Could we make an agreement that all PRs submitted by say Thursday
afternoon that are ready to be merged are merged before the tag is created.
Not saying that Friday's PRs can't be merged just trying to engineers
some predictability when they are working on issues that affect both repos.
Regards,
Darran Lofthouse.
On 08/10/14 21:26, Stuart Douglas wrote:
I think the best way to deal with this is just a time boxed release,
say
every Friday afternoon. That way there is no surprises, and if a PR is
not ready then it can go into next weeks release.
I don't think automation is a good idea, there are to many things that
can go wrong.
Stuart
David M. Lloyd wrote:
> I'll take whatever I can get. :-)
>
> On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
>> that still doesnt solve the problem on "when" next release is.
>>
>> as people that need to do work across both repos need to know this info.
>> Current state is just too unknown and annoyng if you need to do
>> something in core and then also in full to make it work.
>> not to even add to the mix that your PR *needs* to break something in
>> full, at least until your PR for full is also merged.
>>
>>
>>
>> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
>> <mailto:david.lloyd@redhat.com>> wrote:
>>
>> Just telling people "hey I'm releasing core in a day or two"
is already
>> 10x better than the current status quo.
>>
>> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
>> >>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >>>
>> >> _______________________________________________
>> >> wildfly-dev mailing list
>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >>
>> >> _______________________________________________
>> >> wildfly-dev mailing list
>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >
>> >
>> > _______________________________________________
>> > wildfly-dev mailing list
>> >wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> >
>>
>> --
>> - DML
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
3:25 p.m.
On 10/9/14, 7:55 AM, Darran Lofthouse wrote:
Could we make an agreement that all PRs submitted by say Thursday
afternoon that are ready to be merged are merged before the tag is created.
Given the "ready to be merged" bit, sure, fine with me.
I'm not willing to commit to people to get things reviewed and tested on
a weekly deadline, but if things are already reviewed and tested I have
no problem promising to merge them.
I'm just one of the players here, unless I'm nominated as the person who
does the weekly release, in which case my promise matters more. But I
volunteer to do the release if Jason wants that.
Not saying that Friday's PRs can't be merged just trying to
engineers
some predictability when they are working on issues that affect both repos.
Regards,
Darran Lofthouse.
On 08/10/14 21:26, Stuart Douglas wrote:
> I think the best way to deal with this is just a time boxed release, say
> every Friday afternoon. That way there is no surprises, and if a PR is
> not ready then it can go into next weeks release.
>
> I don't think automation is a good idea, there are to many things that
> can go wrong.
>
> Stuart
>
> David M. Lloyd wrote:
>> I'll take whatever I can get. :-)
>>
>> On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
>>> that still doesnt solve the problem on "when" next release is.
>>>
>>> as people that need to do work across both repos need to know this info.
>>> Current state is just too unknown and annoyng if you need to do
>>> something in core and then also in full to make it work.
>>> not to even add to the mix that your PR *needs* to break something in
>>> full, at least until your PR for full is also merged.
>>>
>>>
>>>
>>> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
>>> <mailto:david.lloyd@redhat.com>> wrote:
>>>
>>> Just telling people "hey I'm releasing core in a day or
two" is already
>>> 10x better than the current status quo.
>>>
>>> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
>>> >>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >>>
>>> >> _______________________________________________
>>> >> wildfly-dev mailing list
>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >>
>>> >> _______________________________________________
>>> >> wildfly-dev mailing list
>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > wildfly-dev mailing list
>>>
>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >
>>>
>>> --
>>> - DML
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>>
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
4:23 p.m.
On 10/09/2014 08:25 AM, Brian Stansberry wrote:
On 10/9/14, 7:55 AM, Darran Lofthouse wrote:
> Could we make an agreement that all PRs submitted by say Thursday
> afternoon that are ready to be merged are merged before the tag is created.
>
Given the "ready to be merged" bit, sure, fine with me.
I'm not willing to commit to people to get things reviewed and tested on
a weekly deadline, but if things are already reviewed and tested I have
no problem promising to merge them.
I'm just one of the players here, unless I'm nominated as the person who
does the weekly release, in which case my promise matters more. But I
volunteer to do the release if Jason wants that.
I agree 100% and I also volunteer to be on the weekly release roster
(more people means less likely to miss a release).
> Not saying that Friday's PRs can't be merged just trying
to engineers
> some predictability when they are working on issues that affect both repos.
>
> Regards,
> Darran Lofthouse.
>
>
> On 08/10/14 21:26, Stuart Douglas wrote:
>> I think the best way to deal with this is just a time boxed release, say
>> every Friday afternoon. That way there is no surprises, and if a PR is
>> not ready then it can go into next weeks release.
>>
>> I don't think automation is a good idea, there are to many things that
>> can go wrong.
>>
>> Stuart
>>
>> David M. Lloyd wrote:
>>> I'll take whatever I can get. :-)
>>>
>>> On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
>>>> that still doesnt solve the problem on "when" next release is.
>>>>
>>>> as people that need to do work across both repos need to know this info.
>>>> Current state is just too unknown and annoyng if you need to do
>>>> something in core and then also in full to make it work.
>>>> not to even add to the mix that your PR *needs* to break something in
>>>> full, at least until your PR for full is also merged.
>>>>
>>>>
>>>>
>>>> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
>>>> <mailto:david.lloyd@redhat.com>> wrote:
>>>>
>>>> Just telling people "hey I'm releasing core in a day or
two" is already
>>>> 10x better than the current status quo.
>>>>
>>>> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
>>>> >>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>>
>>>> >> _______________________________________________
>>>> >> wildfly-dev mailing list
>>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>
>>>> >> _______________________________________________
>>>> >> wildfly-dev mailing list
>>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > wildfly-dev mailing list
>>>>
>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >
>>>>
>>>> --
>>>> - DML
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>>
wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>>>
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
- DML
4:42 p.m.
On 09/10/14 14:25, Brian Stansberry wrote:
On 10/9/14, 7:55 AM, Darran Lofthouse wrote:
> Could we make an agreement that all PRs submitted by say Thursday
> afternoon that are ready to be merged are merged before the tag is created.
>
Given the "ready to be merged" bit, sure, fine with me.
+1 Essentially if an engineer has jumped through all of the hoops to get
their PR to the point it is acceptable to merge, e.g. test pass, follow
up commits following a PR review etc... and this is all complete by the
end of Thursday there should be a very high chance their PR will make it
into that weeks release.
Of course overall there is a risk of merge conflicts but we can never
completely eliminate that.
I'm not willing to commit to people to get things reviewed and
tested on
a weekly deadline, but if things are already reviewed and tested I have
no problem promising to merge them.
I'm just one of the players here, unless I'm nominated as the person who
does the weekly release, in which case my promise matters more. But I
volunteer to do the release if Jason wants that.
> Not saying that Friday's PRs can't be merged just trying to engineers
> some predictability when they are working on issues that affect both repos.
>
> Regards,
> Darran Lofthouse.
>
>
> On 08/10/14 21:26, Stuart Douglas wrote:
>> I think the best way to deal with this is just a time boxed release, say
>> every Friday afternoon. That way there is no surprises, and if a PR is
>> not ready then it can go into next weeks release.
>>
>> I don't think automation is a good idea, there are to many things that
>> can go wrong.
>>
>> Stuart
>>
>> David M. Lloyd wrote:
>>> I'll take whatever I can get. :-)
>>>
>>> On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
>>>> that still doesnt solve the problem on "when" next release is.
>>>>
>>>> as people that need to do work across both repos need to know this info.
>>>> Current state is just too unknown and annoyng if you need to do
>>>> something in core and then also in full to make it work.
>>>> not to even add to the mix that your PR *needs* to break something in
>>>> full, at least until your PR for full is also merged.
>>>>
>>>>
>>>>
>>>> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
>>>> <mailto:david.lloyd@redhat.com>> wrote:
>>>>
>>>> Just telling people "hey I'm releasing core in a day or
two" is already
>>>> 10x better than the current status quo.
>>>>
>>>> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
>>>> >>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>>
>>>> >> _______________________________________________
>>>> >> wildfly-dev mailing list
>>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>
>>>> >> _______________________________________________
>>>> >> wildfly-dev mailing list
>>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > wildfly-dev mailing list
>>>>
>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >
>>>>
>>>> --
>>>> - DML
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>>
wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>>>
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
2:47 a.m.
With the various time zones we should define "Thursday afternoon".
On 10/09/2014 05:55 AM, Darran Lofthouse wrote:
Could we make an agreement that all PRs submitted by say Thursday
afternoon that are ready to be merged are merged before the tag is created.
Not saying that Friday's PRs can't be merged just trying to engineers
some predictability when they are working on issues that affect both repos.
Regards,
Darran Lofthouse.
On 08/10/14 21:26, Stuart Douglas wrote:
> I think the best way to deal with this is just a time boxed release, say
> every Friday afternoon. That way there is no surprises, and if a PR is
> not ready then it can go into next weeks release.
>
> I don't think automation is a good idea, there are to many things that
> can go wrong.
>
> Stuart
>
> David M. Lloyd wrote:
>> I'll take whatever I can get. :-)
>>
>> On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
>>> that still doesnt solve the problem on "when" next release is.
>>>
>>> as people that need to do work across both repos need to know this info.
>>> Current state is just too unknown and annoyng if you need to do
>>> something in core and then also in full to make it work.
>>> not to even add to the mix that your PR *needs* to break something in
>>> full, at least until your PR for full is also merged.
>>>
>>>
>>>
>>> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
>>> <mailto:david.lloyd@redhat.com>> wrote:
>>>
>>> Just telling people "hey I'm releasing core in a day or
two" is already
>>> 10x better than the current status quo.
>>>
>>> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
>>> >>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >>>
>>> >> _______________________________________________
>>> >> wildfly-dev mailing list
>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >>
>>> >> _______________________________________________
>>> >> wildfly-dev mailing list
>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >
>>> >
>>> > _______________________________________________
>>> > wildfly-dev mailing list
>>>
>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>> >
>>>
>>> --
>>> - DML
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
James R. Perkins
JBoss by Red Hat
10:29 a.m.
Timezones was the reason I suggested the day before the tagging,
everyones Thursday afternoon should have concluded before we reach the
Friday afternoon that tagging is occurring in. Apart from a bit of
overlap from the US to Australia even the Friday mornings have minimal
overlap regardless of which timezone tagging will occur in.
But really it should translate to the engineer that knows they are
tagging during their afternoon should ensure the PR queue is cleared of
all acceptable PRs in the queue that were ready to be merged when they
start their day before they tag.
Having said all of that in general engineers should be trying to avoid
expecting a last minute PR in, clean test runs need to have happened and
a review should have already happened - if a review has not already
happened it is probably unfair to expect that of the tagger unless the
PR is really trivial.
Regards,
Darran Lofthouse.
On 10/10/14 01:47, James R. Perkins wrote:
With the various time zones we should define "Thursday
afternoon".
On 10/09/2014 05:55 AM, Darran Lofthouse wrote:
> Could we make an agreement that all PRs submitted by say Thursday
> afternoon that are ready to be merged are merged before the tag is created.
>
> Not saying that Friday's PRs can't be merged just trying to engineers
> some predictability when they are working on issues that affect both repos.
>
> Regards,
> Darran Lofthouse.
>
>
> On 08/10/14 21:26, Stuart Douglas wrote:
>> I think the best way to deal with this is just a time boxed release, say
>> every Friday afternoon. That way there is no surprises, and if a PR is
>> not ready then it can go into next weeks release.
>>
>> I don't think automation is a good idea, there are to many things that
>> can go wrong.
>>
>> Stuart
>>
>> David M. Lloyd wrote:
>>> I'll take whatever I can get. :-)
>>>
>>> On 10/08/2014 10:00 AM, Tomaž Cerar wrote:
>>>> that still doesnt solve the problem on "when" next release is.
>>>>
>>>> as people that need to do work across both repos need to know this info.
>>>> Current state is just too unknown and annoyng if you need to do
>>>> something in core and then also in full to make it work.
>>>> not to even add to the mix that your PR *needs* to break something in
>>>> full, at least until your PR for full is also merged.
>>>>
>>>>
>>>>
>>>> On Wed, Oct 8, 2014 at 4:57 PM, David M. Lloyd<david.lloyd(a)redhat.com
>>>> <mailto:david.lloyd@redhat.com>> wrote:
>>>>
>>>> Just telling people "hey I'm releasing core in a day or
two" is already
>>>> 10x better than the current status quo.
>>>>
>>>> On 10/08/2014 07:40 AM, 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@gmail.com<mailto:tomaz.cerar@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@jboss.com<mailto:darran.lofthouse@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@gmail.com<mailto:stuart.w.douglas@gmail.com>
>>>> >>>
<mailto:stuart.w.douglas@gmail.com<mailto:stuart.w.douglas@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@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>>
>>>> >> _______________________________________________
>>>> >> wildfly-dev mailing list
>>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >>
>>>> >> _______________________________________________
>>>> >> wildfly-dev mailing list
>>>>
>>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >>https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > wildfly-dev mailing list
>>>>
>wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> >https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>> >
>>>>
>>>> --
>>>> - DML
>>>> _______________________________________________
>>>> wildfly-dev mailing list
>>>>
wildfly-dev@lists.jboss.org<mailto:wildfly-dev@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
3:38 p.m.
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
3:54 p.m.
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(a)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(a)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
4:06 p.m.
See? Corrections! :-)
At least three volunteers so far, so I think we're solid either way.
On 10/10/2014 08:54 AM, 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(a)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(a)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
--
- DML
5:09 p.m.
I can also help
On 10 Oct 2014, at 15:06, David M. Lloyd <david.lloyd(a)redhat.com> wrote:
See? Corrections! :-)
At least three volunteers so far, so I think we're solid either way.
On 10/10/2014 08:54 AM, 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(a)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(a)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
>
--
- DML
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
1:31 a.m.
I've got the latest afternoon so I don't mind helping out either :)
On 10/10/2014 08:09 AM, Kabir Khan wrote:
I can also help
On 10 Oct 2014, at 15:06, David M. Lloyd <david.lloyd(a)redhat.com> wrote:
> See? Corrections! :-)
>
> At least three volunteers so far, so I think we're solid either way.
>
> On 10/10/2014 08:54 AM, 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(a)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(a)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
>>
> --
> - DML
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
James R. Perkins
JBoss by Red Hat
11:28 p.m.
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(a)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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
12:12 a.m.
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(a)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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
- DML
12:37 a.m.
I meant in the general case, not this week in particular :-)
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(a)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(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
12:33 p.m.
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(a)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(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:49 p.m.
<div name="BB10" id="BB10_response_div" dir="auto"
contenteditable="true"
style="width:100%;background:"#ffffff"; font-size:
initial;font-family:"Calibri","Slate
Pro","sans-serif";color:#1f497d;"><br
style="display:initial"></div>
<div name="BB10" id="response_div_spacer" dir="auto"
contenteditable="true"
style="width:100%;background:"#ffffff"; font-size:
initial;font-family:"Calibri","Slate
Pro","sans-serif";color:#1f497d;"><br
style="display:initial"></div>
<div id="_signaturePlaceholder" name="BB10" dir="auto"
contenteditable="true"
style="font-size:
initial;font-family:"Calibri","Slate
Pro","sans-serif";color:#1f497d;"></div>
<table id="_bb10TempSeparator"
width="100%" style="background-color:white; border-spacing:0px;"
contenteditable="false">
<tr><td></td><td id="_separatorInternal" rowspan=2
style="text-align:center">
<span id="_bb10TempSeparatorText"
style="background-color:white;
color:#0073BC;font-size:smaller;font-family:"Slate
Pro""> Original Message </span>
</td></tr>
<tr> <td colspan=2><div style="border:none;border-top:solid #0073BC
1.0pt;">
</td></tr></table>
<table width="100%"
style="background-color:white;border-spacing:0px;"> <tr><td
id="_persistentHeaderContainer" colspan=2>
<div id="_persistentHeader" style="font-size:
smaller;font-family:"Tahoma","BB Alpha
Sans","Slate Pro","sans-serif";">
<div id=From ><b>From: </b>Darran Lofthouse</div><div id=Sent
><b>Sent: </b>Monday, October 13, 2014 5:33 AM</div><div id=To
><b>To: </b>Stuart Douglas; David M. Lloyd</div><div id=Cc
><b>Cc: </b>wildfly-dev(a)lists.jboss.org</div><div id=Subject
><b>Subject: </b>Re: [wildfly-dev] WildFly Core component upgrade
coordination</div></div></td></tr></table><div
id="_persistentHeaderEnd" style="border:none;border-top:solid #babcd1
1pt;"></div><br><div name="BB10" dir="auto"
id="_originalContent">On 10/10/14 23:37, Stuart Douglas
wrote:<br/>> I meant in the general case, not this week in particular
:-)<br/><br/>+1 I think from a predictability perspective for the majority of
<br/>engineers this means that it is the start of the week that they see
<br/>Wildfly with an updated core which overall is what we are trying to
meet.<br/><br/>> Stuart<br/>><br/>> David M.
Lloyd wrote:<br/>>> We just did a release Tuesday, so why
don't we start next week
instead?<br/>>><br/>>> On 10/10/2014 04:28 PM,
Stuart Douglas wrote:<br/>>>> If no one else gets to I can do
it first thing Monday (Sunday for<br/>>>> everyone
else).<br/>>>><br/>>>>
Stuart<br/>>>><br/>>>> Jason Greene
wrote:<br/>>>>> I don’t think Stuart officially
volunteered? Don’t forget that our<br/>>>>> Friday is
his Saturday, and his Friday is our
Thursday.<br/>>>>><br/>>>>>
Brain volunteered though. I was planning on doing it, but if he
(or<br/>>>>> anyone else is up for thats great), he (or
anyone else) can continue<br/>>>>> to charge me beer
debt
:)<br/>>>>><br/>>>>>
On Oct 10, 2014, at 8:38 AM, David M.
Lloyd&lt;david.lloyd(a)redhat.com&gt;<br/>&gt;&gt;&gt;&gt;
wrote:<br/>>>>><br/>>>>>>
OK so it seems like we have a sort of consensus here. To
summarize:<br/>>>>>><br/>>>>>>
• WildFly Core releases will happen at some nonspecific time on
each<br/>>>>>> Friday (but only if there have
actually been changes that warrant a<br/>>>>>>
release, of course, i.e. there's something that would block
somebody's<br/>>>>>> progress in some
area)<br/>>>>>> • Release will be done by Stuart
or another core team member as<br/>>>>>>
appropriate/needed<br/>>>>>> • Merge team will
make a best effort to merge everything that is
marked<br/>>>>>> ready-for-merge by Thursday
end-of-day<br/>>>>>> • People submitting changes
should have no reasonable expectation
that<br/>>>>>> last minute changes will be merged
unless they are trivial<br/>>>>>> • All WildFly
Core update JIRAs will be parented to this
JIRA:<br/>>>>>>
https://issues.jboss.org/browse/WFLY-3956<br/>>>&...
• Since the last release was this past Tuesday, we'll start this
no<br/>>>>>> sooner than next
week<br/>>>>>><br/>>>>>>
I think that's about it. I'm sure you all will correct me if I
missed<br/>>>>>> something.
:)<br/>>>>>>
--<br/>>>>>> -
DML<br/>>>>>>
_______________________________________________<br/>>>>>>
wildfly-dev mailing list<br/>>>>>>
wildfly-dev(a)lists.jboss.org<br/>&gt;&gt;&gt;&gt;&gt;
https://lists.jboss.org/mailman/listinfo/wildfly-dev<br/>>&a...
--<br/>>>>> Jason T.
Greene<br/>>>>> WildFly Lead / JBoss EAP Platform
Architect<br/>>>>> JBoss, a division of Red
Hat<br/>>>>><br/>>>>><br/>>>>>
_______________________________________________<br/>>>>>
wildfly-dev mailing list<br/>>>>>
wildfly-dev(a)lists.jboss.org<br/>&gt;&gt;&gt;&gt;
https://lists.jboss.org/mailman/listinfo/wildfly-dev<br/>>&a...
_______________________________________________<br/>> wildfly-dev mailing
list<br/>> wildfly-dev(a)lists.jboss.org<br/>&gt;
https://lists.jboss.org/mailman/listinfo/wildfly-dev<br/>>&l...
mailing
list<br/>wildfly-dev@lists.jboss.org<br/>https://lists.jboss.org/mailman/listinfo/wildfly-dev
11:04 a.m.
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(a)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(a)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(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:49 p.m.
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(a)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(a)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(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
- DML
2:51 p.m.
Labels. I meant labels.
On 10/15/2014 07:49 AM, David M. Lloyd wrote:
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(a)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(a)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(a)lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>>
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
--
- DML
2:49 p.m.
Sent from my BlackBerry 10 smartphone.
Original Message
From: Stuart Douglas
Sent: Friday, October 10, 2014 4:28 PM
To: Jason Greene
Cc: wildfly-dev(a)lists.jboss.org
Subject: Re: [wildfly-dev] WildFly Core component upgrade coordination
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(a)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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:53 p.m.
I think your BlackBerry 10 smartphone is not having a good day, I see no
content in this message from you and another message is a blob of HTML ;-)
On 13/10/14 13:49, jose.e.chavez(a)gmail.com wrote:
Sent from my BlackBerry 10 smartphone.
Original Message
From: Stuart Douglas
Sent: Friday, October 10, 2014 4:28 PM
To: Jason Greene
Cc: wildfly-dev(a)lists.jboss.org
Subject: Re: [wildfly-dev] WildFly Core component upgrade coordination
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(a)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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
5:39 p.m.
This is the broken html content:
:)
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(a)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(a)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(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2014-10-13 9:53 GMT-03:00 Darran Lofthouse <darran.lofthouse(a)jboss.com>:
I think your BlackBerry 10 smartphone is not having a good day, I see
no
content in this message from you and another message is a blob of HTML ;-)
On 13/10/14 13:49, jose.e.chavez(a)gmail.com wrote:
>
>
> Sent from my BlackBerry 10 smartphone.
> Original Message
> From: Stuart Douglas
> Sent: Friday, October 10, 2014 4:28 PM
> To: Jason Greene
> Cc: wildfly-dev(a)lists.jboss.org
> Subject: Re: [wildfly-dev] WildFly Core component upgrade coordination
>
> 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(a)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(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
__________________________
Eduardo Sant'Ana da Silva
2014-10-13 9:53 GMT-03:00 Darran Lofthouse <darran.lofthouse(a)jboss.com>:
I think your BlackBerry 10 smartphone is not having a good day, I see
no
content in this message from you and another message is a blob of HTML ;-)
On 13/10/14 13:49, jose.e.chavez(a)gmail.com wrote:
>
>
> Sent from my BlackBerry 10 smartphone.
> Original Message
> From: Stuart Douglas
> Sent: Friday, October 10, 2014 4:28 PM
> To: Jason Greene
> Cc: wildfly-dev(a)lists.jboss.org
> Subject: Re: [wildfly-dev] WildFly Core component upgrade coordination
>
> 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(a)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(a)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(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI
3481
days inactive
3489
days old
37 comments
11 participants
participants (11)
-
Brian Stansberry -
Darran Lofthouse -
David M. Lloyd -
Eduardo Sant´Ana da Silva -
Heiko Braun -
James R. Perkins -
Jason Greene -
jose.e.chavez＠gmail.com -
Kabir Khan -
Stuart Douglas -
Tomaž Cerar