<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 01:35:01 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-3567] kernel update [SLES11 SP3]</title>
                <link>https://jira.whamcloud.com/browse/LU-3567</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;looking at &lt;a href=&quot;https://www.suse.com/products/server/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://www.suse.com/products/server/&lt;/a&gt; it&apos;s apparent that SuSE has now publicly announced SLES11 SP3.&lt;/p&gt;

&lt;p&gt;Need to carefully schedule the cutover from one version to another.  Maybe we need to stage using SP3 instead of SP2 somewhere before using it everywhere?&lt;/p&gt;

&lt;p&gt;Need to make decisions about sticking to the policy of supporting only one version of any distro.  It&apos;s possible to have base and ldiskfs patches for both SP2 and SP3, but it would be easier to drop support for SP2 and support only SP3.&lt;/p&gt;</description>
                <environment></environment>
        <key id="19710">LU-3567</key>
            <summary>kernel update [SLES11 SP3]</summary>
                <type id="6" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11315&amp;avatarType=issuetype">Story</type>
                                            <priority id="2" iconUrl="https://jira.whamcloud.com/images/icons/priorities/critical.svg">Critical</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/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="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="bogl">Bob Glossman</assignee>
                                    <reporter username="bogl">Bob Glossman</reporter>
                        <labels>
                    </labels>
                <created>Mon, 8 Jul 2013 18:03:30 +0000</created>
                <updated>Fri, 27 Sep 2013 16:23:34 +0000</updated>
                            <resolved>Fri, 20 Sep 2013 20:44:33 +0000</resolved>
                                                    <fixVersion>Lustre 2.5.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>7</watches>
                                                                            <comments>
                            <comment id="62547" author="simmonsja" created="Thu, 18 Jul 2013 15:44:37 +0000"  >&lt;p&gt;Since no Lustre maintenance branches support SLES11SP2 which requires a new installation anyways it would be IMO best to move to SLES11 SP3. &lt;/p&gt;</comment>
                            <comment id="62551" author="spitzcor" created="Thu, 18 Jul 2013 15:55:09 +0000"  >&lt;p&gt;That would be acceptable if SLES 11 SP2 won&apos;t be supported at all with 2.5.  However, I would suggest that 2.5 would support both SP2 &amp;amp; SP3.  But it is more problematic since b2_5 might have long legs due to being dubbed the next maintenance branch.  Maybe it would be acceptable to drop SP2 support in a later 2.5 release after everyone has been given an appropriate amount of time to upgrade to SP3?  Did we already take up client OS support with the CDWG?  Even if so, perhaps we should take another look at it.  It should be possible to support both side by side.&lt;/p&gt;</comment>
                            <comment id="65984" author="bogl" created="Fri, 6 Sep 2013 21:44:48 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/7580&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/7580&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="66417" author="bogl" created="Wed, 11 Sep 2013 21:11:52 +0000"  >&lt;p&gt;Just in case it&apos;s not obvious from looking at the submitted patches, we chose to continue supporting building for SP2 as well as building for SP3.&lt;/p&gt;</comment>
                            <comment id="67164" author="pjones" created="Fri, 20 Sep 2013 20:44:33 +0000"  >&lt;p&gt;Landed for 2.5.0&lt;/p&gt;</comment>
                            <comment id="67826" author="spitzcor" created="Fri, 27 Sep 2013 16:23:34 +0000"  >&lt;p&gt;Bob, yup! Thanks!&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </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_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzvuqv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>8978</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>