pivotal-cf / pcf-release-notes

A repo for release notes

pcf-release-notes

This repository stores the content that publishes to the PCF versioned release notes. Versioned release notes for Pivotal Platform v2.7, Pivotal Platform v2.8, and Ops Manager and Tanzu Application Service v2.9 and later have been moved to their respective product repositories:

• docs-ops-manager
• docs-pas
• docs-pcf-windows

All release notes are stored in version-specific branches. Do not use the main branch for release note content.

Branch Information

Branch	Use
main	Do not use.

Create Release Notes

When you create release notes, create them in the branch of this repository that corresponds to the product version number you are updating. Release notes for versioned products publish from the branch of the same name. For example, we publish the PCF 2.5 release notes using the content of the 2.5 branch of this repository.

Publish or Update Release Notes

Change and additions to the content in an existing branch of this repository automatically trigger the cf-release-notes Concourse pipeline run by the VMware Tanzu Documention team: https://concourse.run.pivotal.io/teams/cf-docs/pipelines/cf-release-notes

This pipeline automatically publishes release notes to a staging environment. Once published to a staging environment, someone should review the results to verify the content and formatting. After verification, someone must manually trigger publishing to a production site.

Contact the VMware Tanzu Documentation team to publish your release notes to a production site, either through Slack (#tanzu-docs in the VMware or Pivotal organization) or by email ([email protected]).

If you have access permission to the cf-release-notes Concourse pipeline, you can publish your release notes to a production site without contacting the VMware Tanzu Documentation team. In general, we only recommend this for small changes.

If you have access permission to the cf-release-notes Concourse pipeline, follow the steps below to update release notes on a production site:

1. Update, commit, and changes to a branch of this repository.

2. Verify that your updates publish to the appropriate staging site correctly. You may need to refresh the site in your browser to see the changes.

   • PCF 1.10 staging site
   • PCF 1.11 staging site
   • PCF 1.12 staging site
   • PCF 2.0 staging site
   • PCF 2.1 staging site
   • PCF 2.2 staging site
   • PCF 2.3 staging site
   • PCF 2.4 staging site
   • PCF 2.5 staging site
   • PCF 2.6 staging site

   I think these staging sites are wrong. Try https://docs-pcf-staging.sc2-04-pcf1-apps.oc.vmware.com/pivotalcf/2-6/pcf-release-notes/index.html instead.

3. Open the appropriate tab in Concourse, click the production box, then click the + button in the top right to start a production build.

   • PCF 1.10
   • PCF 1.11
   • PCF 1.12
   • PCF 2.0
   • PCF 2.1
   • PCF 2.2
   • PCF 2.3
   • PCF 2.4
   • PCF 2.5
   • PCF 2.6

   Look on concourse: https://runway-ci.eng.vmware.com/teams/mapbu-docs/pipelines/cf-release-notes

pcf-release-notes's Issues

1.10.25 Release note web link results in 404

This section of the 1.10.25 Release Note produces a 404 Not Found Error

• Bumps cf-autoscaling-release to v84.5 Release
  Notes.

2.8.5 release notes appear to be missing from pivnet

Hi there, just a heads up, despite the merge here a few days ago, it appears 2.8.5 release notes are not visible on pivnet (https://docs.pivotal.io/platform/2-8/release-notes/runtime-rn.html)

just giving a heads up 👍 thanks

Opsmgr 2.9.5 release notes not published on tanzu docs (/thanks for having this be in git)

This isn't a complaint or anything, I just want to share why I love having these release notes in the open:

Just a heads up, as of writing this issue (6/17/20 at ~12:40pm central), the release notes for opsmgr 2.9.5 are not published on the tanzu/pivotal.io docs site (the current highest it goes is 2.9.4), but the product has been available for download for a few days.

This isn't a huge deal, I imagine things are just moving through update pipelines, but because the docs are OSS I can just look at the opsmgr 2.9.5 release notes PR listed here. And I can keep an eye on any release-candidate updates every so often just to be more prepared about what changes might be coming down the pike before the official release.

I want to thank you all for the work you all do to keep the doc professional, clean, updated, and able to contribute (whether that's a good thing is highly debatable, I know >_>).

That's all. Just posting this because I think it's an excellent validation of why having the doc be version controlled and open is really valuable. Maybe you all as maintainers hate it 😉 , but I want you to know that as a consumer of these products you all have really helped me out

thanks 👍 we can close this whenever, no worries

screencaps of pivnet/tanzu:

NSX-T tile install

Current content for nsx-t portion has:

Install the NSX-T tile.

You must install the NSX-T tile after you install the Ops Manager Director tile.
You must install the NSX-T tile before you install the PAS tile.

It should be:

Install the NSX-T tile.

You must install the NSX-T tile after you install the Ops Manager Director tile.
You must install the NSX-T tile (import and config but not hit Apply Changes) before you install the PAS tile.
``

3445 is up to version .16 and this page stops at .7

https://docs.pivotal.io/pivotalcf/1-12/pcf-release-notes/stemcell-rn.html

Where are the release notes for version .8 through .16?

1.7 Tile author release notes don't mention change from instance_definitions to instance_definition

Is this the only place to look for changes to tile metadata structure when moving to v1.7 metadata?

http://docs.pivotal.io/pivotalcf/1-7/pcf-release-notes/opsmanager-rn.html#tile-authors

It should mention the change from instance_definitions (array) to instance_definition (object)

https://github.com/pivotal-cf/docs-partners/commit/98071fc58ae7b09dc2ac18c9ae81364dbb9af856#diff-53afaab04f3f877756a66316f1e373ebR379

Missing required details

Hi there,

As a user of this document I can't figure out whether some issues listed here are fixed in a later version, and if yes, in which version. E.g. this issue: Inviting New Users or Adding Space Roles in Apps Manager Fails

Such details are there in many other listed issues which is very helpful to know which minor versions are only impacted by it. Please add such missing details for its proper understanding.

Bug not listed in know Issue section

This bug is not listed in know issues section https://www.pivotaltracker.com/n/projects/555129/stories/157602876.

Linkf for 2.4 Zero Downtime App Deployment gets 404

The ZeroDowntim App Beta Feature link is not found
https://docs.pivotal.io/pivotalcf/2-4/devguide/deploy-apps/zero-downtime.html

PCF 2.6 Release notes links to PCF 2.7 Stemcell release notes

The Stemcell Release Notes link on this page: https://docs.pivotal.io/pivotalcf/2-6/pcf-release-notes/ sends me to a 2.7 stemcell release notes page which requires a login to view. Seems like it should actually point to https://docs.pivotal.io/pivotalcf/2-6/stemcells/index.html

pcf-release-notes/index.html.md.erb

Line 34 in bee89a2

* [Stemcell Release Notes](https://docs.pivotal.io/pivotalcf/2-7/stemcells/index.html)

Escaping of * not working for 1.12.9 table

Escaping of * not working for 1.12.9 table
https://github.com/pivotal-cf/pcf-release-notes/blob/1.12/runtime-rn.html.md.erb#L63

It is working for lower versions (e.g. https://github.com/pivotal-cf/pcf-release-notes/blob/1.12/runtime-rn.html.md.erb#L313)

Please configure GITBOT

@pivotal-cf : Pivotal uses GITBOT to synchronize Github issues and pull requests with Pivotal Tracker.
Please add your new repo to the GITBOT config-prouction.yml in the Gitbot configuration repo
If there are any questions, please reach out to [email protected]

"In-container CF helper assets are transferred into app containers securely" Feature improvement isn't included in v2.7 release notes

In reviewing the current v2.7 release notes I don't see a call out for the security enhancement described in Aha! card ERT-560.

This feature improvement was a x-functional effort between capi and diego teams. The 2.7.0-beta.1 build includes both capi-release v1.84.0 and diego-release v2.34.0 which collectively enable the enhancement.

Remove 2012R2 reference in PASW release notes

PASW 2012R2 is an offering that's approaching EOL. Let's not draw visibility to it and just remove the note.

https://github.com/pivotal-cf/pcf-release-notes/blob/2.1/windows-rn.html.md.erb
https://github.com/pivotal-cf/pcf-release-notes/blob/2.2/windows-rn.html.md.erb

Link to Microsoft Azure Availability Zones Available points to staging doc

In paragraph https://docs.pivotal.io/pivotalcf/2-5/pcf-release-notes/breaking-changes.html#azure-azs, the last line states:

For more information about Azure AZs, see Microsoft Azure Availability Zones Available (link).

The last link actually points to https://docs-pcf-staging.cfapps.io which requires a login/pwd.

Missing Release Note

The ops-manager release notes are missing version 1.11

Error in release notes (Default SSH Access)

Disable Default SSH Access for New Applications

Previously, application SSH access was previously enabled globally as a feature in Cloud Foundry ...

No need to use previously twice

Missing released stemcells in 3421 line

pcf-release-notes/stemcell-rn.html.md.erb

The release notes are missing any data for 3421.24 and 3421.26.

Also, the sequence of version numbers is erratic.

Stemcell in version table for ERT 1.12.13 does not exist

I've raised PR #74 to fix this based on the externally-visible information I have access to.

2.4.4 Release Notes mess up formatting of 2.3.3 release notes

PDF download link returns verison 2.3 vs 2.6

Navigate to this link:
https://docs.pivotal.io/pivotalcf/2-6/pcf-release-notes/index.html
Verify the 2.6 version on the pull down.
click on the PDF link
I was expecting 2.6, not 2.3.

Opened the downloaded PDF just in case this was a naming issue and not a content issue.,
The 2.3 file has version 2.3 published 24 Sept 2018 on the title page.

Release Notes version drop-down links are broken

Issues:

• Links for 1.10 through 1.6 are broken.
• Appears to be broken due to using http instead of https