Does 2.1.2 need be installed on top of 2.1.1?

[ThomasColson]

If I were slipstreaming service packs into an admin install, can I put 2.1.2 on top of 2.1 and it will roll up 2.1.1, or do I need to slipstream 2.1.1 first (which would be a pain....)?

[XanderBakker]

Hate to tell you, but it was shared on the internal website. I guess this info was missing in the messaging that went out. Should be done better next time so that clients don't have to guess what they should do. 

[JoshuaBixby]

At least I wasn't missing the obvious.  Hopefully someone from the Pro communications team checks this thread and updates the external documentation.  Thanks.

[Todd_Metzler]

"I think ESRI is under the mistaken impression that all users are going to have the admin rights necessary to hit that update button, when the opposite is the reality."  Agree!  Besides, in the enterprise world users don't really get to choose application patching.  The team responsible for the app sets the schedule after 1st testing the patch in a controlled environment to ensure nothing else gets broken in the enterprise as a result of patch application.

Now I'd like to know:  How can I disable the check for updates at startup in pro 2.1.2 (yes I patched Pro serial fasion 2.1.1 then 2.1.2) for my remote app consumers so the end user isn't tempted to try to do something they can't on our application server.

[brianbond]

For anyone that wants to know how to disable the check for updates at startup in ArcGIS Pro. 

Todd Metzler wrote:

Now I'd like to know:  How can I disable the check for updates at startup in pro 2.1.2 (yes I patched Pro serial fasion 2.1.1 then 2.1.2) for my remote app consumers so the end user isn't tempted to try to do something they can't on our application server.

Here is an ESRI Technical article that I found and I have applied. 

FAQ: Is it possible to block update notifications in ArcGIS Pro, so that end-users are unable to ins... 

[TimOrmsby]

Hi, yes, Pro documentation team has seen this thread. Thanks for reporting the confusion.

[nigelwillits]

If the Pro documentation team had seen it by Mar 1, 2018, why have they not updated the release notes page by Apr 26? I have just spent 15 minutes finding and reading this thread. Can I send an invoice for my time?!?!

[RobertGarrity]

Hello, everyone. I'm sorry for the delay on this. As documentation lead for ArcMap and ArcGIS Pro, my goal is to provide the information you need to use these products effectively in your work. I realize that on the surface changing web help content is a simple html edit, but underneath there is more to it, such as translating to six languages, so we typically follow scheduled updates. In this case, we need to make an exception and update the content immediately.

The ArcGIS Desktop Documentation Team has a topic that covers cumulative releases in the queue, ready to be released with the next web help update. So, for now, the team is making a critical update to the "Release notes for ArcGIS Pro 2.1"--it will be covered in the intro paragraphs of the page. There are some dependencies to posting that, but I am working to get that information on the website as soon as possible.

UPDATE: The paragraph has been added to the Release Notes topic. At 2.2, a new topic will be added, and it will cover how Pro adheres to semantic versioning and that you can expect patches to be cumulative. The Release Notes topics will link to the new one.

[JoshuaBixby]

Robert Garrity‌, thanks for chiming in and sharing some information on production documentation updates.  You mentioned, "we typically follow scheduled updates," can you elaborate a bit more?  Even if the dates/schedules fluctuate, do you aim for semi-annually, matching up with product releases, or something else?

[RobertGarrity]

Hi, Joshua. You're welcome! And, yes, I can elaborate a bit more.

At a minimum, we update the Pro web help with each major, minor, and patch release. Extensive content updates occur with major and minor releases to incorporate new functionality. To give you an idea of the extent, there are about 650 new topics or topic versions for ArcGIS Pro 2.2 so far. We'll probably have between 800 to 1,000 topics/topic versions by the time 2.2 releases.

The web help updates that coincide with Pro's patch (i.e., "bug-fix") releases are much lighter because there isn't new functionality to describe. However, we take that opportunity to release content enhancements that are ready at that time but not specific to the next release. At 2.1, we revamped the licensing documentation section to make it more comprehensive and clear. We identified more improvements to make to that section after the release and published them when 2.1.1 went live. We also fix severe documentation problems during patch releases, such as adding a step that was missing in a tutorial, preventing people from completing a new workflow.

Although we try to keep the focus of Software Development on the next release as much as possible, when we have a critical doc problem to fix, like the one in this thread, we redirect resources to address it. This falls under critical doc updates.

Pro has two major or minor releases per year, about two to four patches per year, and we make about 10-20 critical doc updates, so that's between 14 and 26 total doc updates per year.

The people who work on Pro also work on ArcMap, but ArcMap is usually limited to two significant releases--equivalent to Pro's major and minor releases--and has 10-15 critical doc updates per year.

[DanPatterson_Retired]

Robert, kudos to the team that has worked on the 'Pro help documentation.  I find it the best incarnation so far. 

Do us and yourselves a favor and highlight the ArcGIS Blog a bit more... buried in the 'Community' link on the landing page is a bit modest.  It is full of pertinent information directly and indirectly related to the help documentation itself.