<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:52:59 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>[YANGTOOLS-355] Milestone: Introduce support for YANG v 1.1 (RFC7950)</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-355</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;YANGTools parser should be able to parse and express information defined in YANG models from &lt;a href=&quot;https://tools.ietf.org/html/draft-ietf-netmod-rfc6020bis-01&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/draft-ietf-netmod-rfc6020bis-01&lt;/a&gt;&lt;/p&gt;


&lt;p&gt;Compatibility with parsing of YANG version 1 needs to be preserved.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="22775">YANGTOOLS-355</key>
            <summary>Milestone: Introduce support for YANG v 1.1 (RFC7950)</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <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="pkajsa">Peter Kajsa</assignee>
                                    <reporter username="tony.tkacik@gmail.com">Tony Tkacik</reporter>
                        <labels>
                    </labels>
                <created>Tue, 4 Nov 2014 13:42:55 +0000</created>
                <updated>Sun, 10 Apr 2022 18:35:23 +0000</updated>
                            <resolved>Wed, 1 Mar 2017 09:42:31 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>9</watches>
                                                                                                                <comments>
                            <comment id="43144" author="martin.ciglan" created="Tue, 20 Jan 2015 11:02:35 +0000"  >&lt;p&gt;in very first draft phase&lt;/p&gt;</comment>
                            <comment id="43145" author="rovarga" created="Wed, 18 Mar 2015 12:39:57 +0000"  >&lt;p&gt;Beryllium feature.&lt;/p&gt;</comment>
                            <comment id="43146" author="tony.tkacik@gmail.com" created="Wed, 30 Mar 2016 08:45:32 +0000"  >&lt;p&gt;Further analysis of changes showed that full support will be probably slanted for Carbon, since it does not only affect YANG Tools, but also MD-SAL, NETCONF and RESTCONF.&lt;/p&gt;</comment>
                            <comment id="43147" author="rgoulding" created="Wed, 30 Mar 2016 22:57:42 +0000"  >&lt;p&gt;Thanks for the synopsis on the scope of this change.  Do we have any ideas on how yangtools will handle YANG models with version 1.1 in Boron?  Will the parser reject such models?&lt;/p&gt;</comment>
                            <comment id="43148" author="verthezpw" created="Mon, 3 Oct 2016 11:47:16 +0000"  >&lt;p&gt;May I ask what the plan now is for support of YANG 1.1?   It is now officially planned to be included in Carbon?&lt;/p&gt;

&lt;p&gt;Note that YANG 1.1 is now a Proposed Standard (&lt;a href=&quot;https://tools.ietf.org/html/rfc7950&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://tools.ietf.org/html/rfc7950&lt;/a&gt;), so probably the title of this ticket should be updated.&lt;/p&gt;

&lt;p&gt;We are feeling the heat of this, as more and more IETF YANG modules are YANG 1.1, so I would really like to know the plan.  I understand the date for Carbon is May next year, which we can live with, although we would probably try to use intermediate milestones of the yang tools when available.   But we would have a big problem if this would not be in Carbon: in that case, we will probably have to look for alternatives.&lt;/p&gt;</comment>
                            <comment id="67854" author="JIRAUSER12905" created="Thu, 13 Feb 2020 18:16:25 +0000"  >&lt;p&gt;I&apos;m using version &lt;font color=&quot;#000000&quot;&gt;0.7.4-Lithium-SR4 of &lt;/font&gt;&lt;font color=&quot;#000000&quot;&gt;yang-maven-plugin&lt;/font&gt; &lt;font color=&quot;#000000&quot;&gt;which complains as follows when asked to process a YANG input with &quot;yang-version 1.1;&quot;&lt;/font&gt;&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Unable to parse yang files from /Users/me/my-project/yang: Yang validation failed for fileorg.opendaylight.yangtools.yang.parser.util.YangValidationException: (In (sub)module:my-module-config-v1) Unsupported yang version:1.1, supported version:1 -&amp;gt; [Help 1]&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;&lt;font color=&quot;#000000&quot;&gt;I see that many issues tagged &lt;span class=&quot;error&quot;&gt;&amp;#91;Yang 1.1&amp;#93;&lt;/span&gt; are resolved. Do I need to set a special command option, use a generator class other than&lt;/font&gt;&lt;br/&gt;
&lt;font color=&quot;#000000&quot;&gt;org.opendaylight.yangtools.maven.sal.api.gen.plugin.CodeGeneratorImpl&lt;/font&gt; or ? Please advise, thanks.&lt;/p&gt;</comment>
                            <comment id="67862" author="rovarga" created="Fri, 14 Feb 2020 11:13:19 +0000"  >&lt;p&gt;Lithium SR4 predates RFC7950 by ~6 months, so there is just no way that release could have supported it. Upgrade to a supported version (Neon+) and you&apos;ll be fine.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="23084">YANGTOOLS-664</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23085">YANGTOOLS-665</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23086">YANGTOOLS-666</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23087">YANGTOOLS-667</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23088">YANGTOOLS-668</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23089">YANGTOOLS-669</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23090">YANGTOOLS-670</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23091">YANGTOOLS-671</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23092">YANGTOOLS-672</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23093">YANGTOOLS-673</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23096">YANGTOOLS-676</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23099">YANGTOOLS-679</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23100">YANGTOOLS-680</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23101">YANGTOOLS-681</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23102">YANGTOOLS-682</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23103">YANGTOOLS-683</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23104">YANGTOOLS-684</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23105">YANGTOOLS-685</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23107">YANGTOOLS-687</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23118">YANGTOOLS-698</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23119">YANGTOOLS-699</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="23150">YANGTOOLS-730</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2305</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=2305]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10308"><![CDATA[New Feature]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10348"><![CDATA[Carbon-M5]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i026pr:</customfieldvalue>

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