<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:10:42 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>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-7645] Stop controlling the RPM Release field from Lustre&apos;s build system</title>
                <link>https://jira.whamcloud.com/browse/LU-7645</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;We need to stop trying to control the RPM Release field from instide Lustre&apos;s build system (where &quot;build system&quot; means autogen.sh/configure/autoconf/automake/libtool, not anything to do with lbuild).&lt;/p&gt;

&lt;p&gt;Lustre is open source software, and there are many subreleases created by various organizations that need to be uniquely versioned.  Some of these releases are small and have little distribution, some are major and part of a vendor&apos;s product line.  What they all have in common is that we need some way to tell them apart when they are installed in the wild.&lt;/p&gt;

&lt;p&gt;We have gone through a couple rounds of trying to address this problem. In the most recent round we created the configure --downstream-release option that allows us to specify an additional version string at configure time.  This string is inserted by the current Lustre build and packaging scripts into the RPM Release field.&lt;/p&gt;

&lt;p&gt;I myself was involved in this recent design, so I share the blame for this approach.  But now I&apos;m older, wiser, and balder.  We should not be doing this.&lt;/p&gt;

&lt;p&gt;The RPM Release field is &lt;em&gt;not&lt;/em&gt; the correct place to put versioning information about the source code.  configuration time isn&apos;t really the right time to specify the versioning either, except maybe for one-off build information like a commit number for debug and testing fields.  But even when configuration time is acceptable to add version information, that should go in the Version field, not the Release field.&lt;/p&gt;

&lt;p&gt;It is clear to me now that the Release field needs to be left unmolested by Lustre&apos;s build system.  The Release field is the sole domain of the packager.  Right now the concepts of building and packaging are pretty intertwined in the lustre tree, but we need to work to make a clearer separation.&lt;/p&gt;

&lt;p&gt;The first step is to stop using the Release field.  That is not in Lustre&apos;s domain to use for its versioning purposes.  Lustre&apos;s versioning should only appear in the Version field.&lt;/p&gt;
</description>
                <environment></environment>
        <key id="34028">LU-7645</key>
            <summary>Stop controlling the RPM Release field from Lustre&apos;s build system</summary>
                <type id="7" iconUrl="https://jira.whamcloud.com/images/icons/issuetypes/task_agile.png">Technical task</type>
                            <parent id="20969">LU-3953</parent>
                                    <priority id="3" iconUrl="https://jira.whamcloud.com/images/icons/priorities/major.svg">Major</priority>
                        <status id="6" iconUrl="https://jira.whamcloud.com/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="mdiep">Minh Diep</assignee>
                                    <reporter username="morrone">Christopher Morrone</reporter>
                        <labels>
                            <label>patch</label>
                    </labels>
                <created>Fri, 8 Jan 2016 22:39:12 +0000</created>
                <updated>Wed, 20 Jul 2016 18:21:11 +0000</updated>
                            <resolved>Wed, 20 Jul 2016 18:21:11 +0000</resolved>
                                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                            <comments>
                            <comment id="139981" author="morrone" created="Mon, 25 Jan 2016 22:53:36 +0000"  >&lt;p&gt;There are several patches under &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7699&quot; title=&quot;Overhaul lustre&amp;#39;s versioning&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7699&quot;&gt;&lt;del&gt;LU-7699&lt;/del&gt;&lt;/a&gt; that overhaul lustre&apos;s versioning.  The first patch(&lt;a href=&quot;http://review.whamcloud.com/18107&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/18107&lt;/a&gt;) partly addresses this issue by moving third-party versions (what used to be --downstream-release) and git --describe type information out of the release field and into the version proper.&lt;/p&gt;

&lt;p&gt;Now we just need to stop putting the kernel&apos;s verion string into the release field (&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7643&quot; title=&quot;Remove kernel version string from Lustre release field&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7643&quot;&gt;&lt;del&gt;LU-7643&lt;/del&gt;&lt;/a&gt;).&lt;/p&gt;</comment>
                            <comment id="150927" author="gerrit" created="Wed, 4 May 2016 00:47:21 +0000"  >&lt;p&gt;Christopher J. Morrone (morrone2@llnl.gov) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/19958&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19958&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7645&quot; title=&quot;Stop controlling the RPM Release field from Lustre&amp;#39;s build system&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7645&quot;&gt;&lt;del&gt;LU-7645&lt;/del&gt;&lt;/a&gt; build: Remove unused --with-release configure option&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: 34198af768631badb46e3c0790ffeadc19c6f90b&lt;/p&gt;</comment>
                            <comment id="156396" author="morrone" created="Tue, 21 Jun 2016 21:47:02 +0000"  >&lt;p&gt;With &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-5614&quot; title=&quot;use %kernel_module_package for weak-updates&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-5614&quot;&gt;&lt;del&gt;LU-5614&lt;/del&gt;&lt;/a&gt; close to landing, I rebased this issues&apos; patch. It is ready to go through the normal review process.&lt;/p&gt;</comment>
                            <comment id="159347" author="gerrit" created="Wed, 20 Jul 2016 17:42:42 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/19958/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19958/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7645&quot; title=&quot;Stop controlling the RPM Release field from Lustre&amp;#39;s build system&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7645&quot;&gt;&lt;del&gt;LU-7645&lt;/del&gt;&lt;/a&gt; build: Remove unused --with-release configure option&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: b2ee26bb78ccea8616b3fc94cc1c5fc258831207&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10120">
                    <name>Blocker</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="34026">LU-7643</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="34259">LU-7699</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10490" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>End date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 6 May 2016 22:39:12 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzxxp3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10493" key="com.atlassian.jira.plugin.system.customfieldtypes:datepicker">
                        <customfieldname>Start date</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 8 Jan 2016 22:39:12 +0000</customfieldvalue>

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