<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:37:34 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[RELENG-129] ODLParent version not aligned in stable/oxygen</title>
                <link>https://jira.opendaylight.org/browse/RELENG-129</link>
                <project id="10164" key="RELENG">releng</project>
                    <description>&lt;p&gt;I ran a maven build but I see odlparent pulled in in two versions, 3.1.0 and 3.1.1&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;It seems netvirt and it&apos;s dependencies require odlparent 3.1.0 and also yangtools 2.0.5, but this version of yangtools requires odlparent 3.1.1&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Please bump the required odlparent version to 3.1.1 to match what&apos;s required by yangtools&lt;/p&gt;</description>
                <environment></environment>
        <key id="30141">RELENG-129</key>
            <summary>ODLParent version not aligned in stable/oxygen</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="skitt">Stephen Kitt</assignee>
                                    <reporter username="MikeKolesnik">Mike Kolesnik</reporter>
                        <labels>
                    </labels>
                <created>Mon, 18 Jun 2018 08:24:32 +0000</created>
                <updated>Mon, 25 Jun 2018 08:50:40 +0000</updated>
                            <resolved>Mon, 25 Jun 2018 08:50:40 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                                                                <comments>
                            <comment id="63480" author="skitt@redhat.com" created="Tue, 19 Jun 2018 09:59:17 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=mdindoffer&quot; class=&quot;user-hover&quot; rel=&quot;mdindoffer&quot;&gt;mdindoffer&lt;/a&gt; this isn&#8217;t what broke SXP, none of these patches have been merged yet, and the YANG Tools bump didn&#8217;t break SXP. Now to figure out what did... (It&#8217;s very recent, &lt;a href=&quot;https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-oxygen/108/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;yesterday&#8217;s multipatch build&lt;/a&gt; built fine, including SXP.)&lt;/p&gt;</comment>
                            <comment id="63536" author="skitt@redhat.com" created="Wed, 20 Jun 2018 07:45:40 +0000"  >&lt;p&gt;The full multipatch build to validate this series of patches is &lt;a href=&quot;https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-oxygen/110/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-oxygen/110/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="63537" author="wznoinsk" created="Wed, 20 Jun 2018 07:56:13 +0000"  >&lt;p&gt;thanks &lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=skitt&quot; class=&quot;user-hover&quot; rel=&quot;skitt&quot;&gt;skitt&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I see builds #108 and #109 in the ^ job were ran for the same gerrit CR, they both passed, is that enough or we should wait for 110?&lt;/p&gt;</comment>
                            <comment id="63538" author="skitt@redhat.com" created="Wed, 20 Jun 2018 08:18:44 +0000"  >&lt;p&gt;Builds 108 and 109 only built the Fluorine managed projects; for Oxygen we need to build all the autorelease projects, which is what 110 checks.&lt;/p&gt;</comment>
                            <comment id="63589" author="skitt@redhat.com" created="Thu, 21 Jun 2018 07:42:01 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-oxygen/111/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/job/integration-multipatch-test-oxygen/111/&lt;/a&gt; complete successfully so this is good to go.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03fmv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>