On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorbur...@redhat.com>
wrote:

> On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorbur...@redhat.com>
> wrote:
>
>> Hello,
>>
>> almost 3 months ago, on https://lists.opendaylight.
>> org/pipermail/controller-dev/2017-September/013889.html, I had started a
>> thread re. the mysterious problems hit in the controller archetype "self
>> test", which occured on Gerrit and Jenkins, and only there (it worked
>> locally even 3 months ago).
>>
>> Today I finally made time to progress on this, and
>> https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up
>> what is going on there, documented for future reference.
>>
>> Is this feasible to get an odlparent 3.0.2 with https://git.opendaylight.
>> org/gerrit/#/c/65940/ for https://git.opendaylight.org/gerrit/#/c/65941/
>> ?
>>
>> Tx,
>> M.
>>
>> PS: I'm hoping to work on https://jira.opendaylight.org/
>> browse/INFRAUTILS-17 in the coming days, which will likely also require
>> a change in odlparent; perhaps this and that could be pooled together into
>> a 3.0.2 - anything else?
>>
>
> https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes
> are what I meant here; if all of this, together with
> https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an
> odlparent 3.0.2, in the hopefully not-too-distant future, that would be
> fabulous.
>

would any fellow controller commiter be willing to merge this
https://git.opendaylight.org/gerrit/#/c/65941/ now?

Tom, or even I volunteer to, then rebase
https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and
then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still
IMHO.


> --
>> Michael Vorburger, Red Hat
>> vorbur...@redhat.com | IRC: vorburger @freenode | ~ = http://vorburger.ch
>>
>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to