<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Minor patch release date for 11.1.8 in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999784#M5305</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;While I understand your stance on this, take a look at the vendors position. If they say something, then push it out, it could look poorly on them. Also if they say we are going to release it on date x and they dont, it can cause additional tension on them as well as potential legal issues.&lt;/P&gt;
&lt;P&gt;So they do it this way to keep their options for a release date open. There are a lot of vendors that also have adopted this method.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Fri, 27 Dec 2024 18:44:10 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2024-12-27T18:44:10Z</dc:date>
    <item>
      <title>Minor patch release date for 11.1.8</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999777#M5304</link>
      <description>&lt;P&gt;I have run into a situation when we upgraded our environment to 11.1.4-h7, where from the Panorama, I can not modify existing rule sets with my radius authenticated account. This environment is government, so STIGS are used (this should allay any odd questions).&amp;nbsp; The only solution TAC gave was to create a local admin account and use for said modifications.&amp;nbsp; While this is a band-aid, it will be found upon periodic audits.&amp;nbsp; TAC also stated that this is a known issue and is slated to be fixed in patch 11.1.8 (potentially January 18th).&amp;nbsp; Now, I realize it's hard to post "proposed" date of release calendar, but it would at least help when questioned by a review board.&amp;nbsp; Has anyone, come across something similar to a pre-release calendar?&amp;nbsp; I mean if you're using a CI/CD pipeline for these, this would be a very simple thing and it could auto update if engineering needs to slide the window out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-MJ&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 18:30:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999777#M5304</guid>
      <dc:creator>JohnstonM</dc:creator>
      <dc:date>2024-12-27T18:30:59Z</dc:date>
    </item>
    <item>
      <title>Re: Minor patch release date for 11.1.8</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999784#M5305</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;While I understand your stance on this, take a look at the vendors position. If they say something, then push it out, it could look poorly on them. Also if they say we are going to release it on date x and they dont, it can cause additional tension on them as well as potential legal issues.&lt;/P&gt;
&lt;P&gt;So they do it this way to keep their options for a release date open. There are a lot of vendors that also have adopted this method.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 18:44:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999784#M5305</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-12-27T18:44:10Z</dc:date>
    </item>
    <item>
      <title>Re: Minor patch release date for 11.1.8</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999786#M5306</link>
      <description>&lt;P&gt;I completely see that point. Now to counter, if TAC is stating it "verbally", wouldn't something of this sort, cut down on the number of calls for the same issue?&amp;nbsp; I'm only wanting something that could be referenced in a change control review board (they don't like "they said").&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 19:00:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999786#M5306</guid>
      <dc:creator>JohnstonM</dc:creator>
      <dc:date>2024-12-27T19:00:35Z</dc:date>
    </item>
    <item>
      <title>Re: Minor patch release date for 11.1.8</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999787#M5307</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I understand your point. I dont work for the company nor can I speak to their internal processes. I also understand the change board and their stance and wanting something concrete, but not everything can be.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 20:44:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/minor-patch-release-date-for-11-1-8/m-p/999787#M5307</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2024-12-27T20:44:35Z</dc:date>
    </item>
  </channel>
</rss>

