Changes to Wildfly model that affects HAL

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Changes to Wildfly model that affects HAL

Claudio Miranda
Hi, I would like to propose to add a label "affects-hal" to
WFLY/WFCORE issues that may affect HAL, for example if the resulting
change may add/change/remove resources/operations or dependent
resources, this way once the PR is open, we may test the changes
before it is merged or work on a HAL feature branch.

I have had manually looking (and following) for PR that contains those
changes, but it is more of a guessing work.

An alternative to add the label, would be to add the "Web Console"
component to the issue, but this would not work as there should be two
issues one for WFLY/WFCORE and one for HAL.

I would like to hear your opinions on this topic to help us track
those incoming changes.

Thanks
--
  Claudio Miranda

[hidden email]
http://www.claudius.com.br
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Changes to Wildfly model that affects HAL

Tom Jenkinson
Perhaps it would be simplest to ask that people who make changes that affect the console raise a HAL enhancement request directly in the HAL issue tracker? Would that be possible?


On 3 September 2018 at 15:58, Claudio Miranda <[hidden email]> wrote:
Hi, I would like to propose to add a label "affects-hal" to
WFLY/WFCORE issues that may affect HAL, for example if the resulting
change may add/change/remove resources/operations or dependent
resources, this way once the PR is open, we may test the changes
before it is merged or work on a HAL feature branch.

I have had manually looking (and following) for PR that contains those
changes, but it is more of a guessing work.

An alternative to add the label, would be to add the "Web Console"
component to the issue, but this would not work as there should be two
issues one for WFLY/WFCORE and one for HAL.

I would like to hear your opinions on this topic to help us track
those incoming changes.

Thanks
--
  Claudio Miranda

[hidden email]
http://www.claudius.com.br
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Changes to Wildfly model that affects HAL

Claudio Miranda
On Tue, Sep 4, 2018 at 5:31 AM, Tom Jenkinson <[hidden email]> wrote:
> Perhaps it would be simplest to ask that people who make changes that affect
> the console raise a HAL enhancement request directly in the HAL issue
> tracker? Would that be possible?

This would be the preferable option. I didn't ask it at first as that
would require a bit more work of the developer, but I prefer this
option.

Thanks Tom
--
  Claudio Miranda

[hidden email]
http://www.claudius.com.br
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: Changes to Wildfly model that affects HAL

Harald Pehl
I really like your idea Claudio. Having such a label would make our work
a lot easier. At the same time this would be the least time-consuming
option for the reporter of the issue.

Having such a label, we could setup filters and create the related HAL
issues on our own.

> On 4. Sep 2018, at 14:20, Claudio Miranda <[hidden email]> wrote:
>
> On Tue, Sep 4, 2018 at 5:31 AM, Tom Jenkinson <[hidden email]> wrote:
>> Perhaps it would be simplest to ask that people who make changes that affect
>> the console raise a HAL enhancement request directly in the HAL issue
>> tracker? Would that be possible?
>
> This would be the preferable option. I didn't ask it at first as that
> would require a bit more work of the developer, but I prefer this
> option.
>
> Thanks Tom
> --
>  Claudio Miranda
>
> [hidden email]
> http://www.claudius.com.br
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev