Skip to content

Commit 17c7a4e

Browse files
committed
update Tanzu Network links
1 parent 35397da commit 17c7a4e

4 files changed

+8
-8
lines changed

brokered.html.md.erb

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ service tile for <%= vars.platform_name %>.
99
You can achieve the first real improvement in your <%= vars.platform_name %> user experience by creating a [Service Broker](service-brokers.html) for your service.
1010

1111
A brokered service runs external to <%= vars.platform_name %>, but it has a tile
12-
on [VMware Tanzu Network](http://network.pivotal.io). You install, configure, and upgrade the tile through the
12+
on [VMware Tanzu Network](https://network.tanzu.vmware.com). You install, configure, and upgrade the tile through the
1313
Tanzu Operations Manager Installation Dashboard.
1414

1515
The service broker eliminates the need for you to know the URLs and

dev-workflow.html.md.erb

+1-1
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ how tiles are structured.
2626

2727
* [Tile documentation](./tile-documentation.html) explains how to document your tile as part of [<%= vars.platform_name %> documentation](http://docs.pivotal.io).
2828

29-
* [Publish and update](./publish.html) explains how to publish your tile on [VMware Tanzu Network](http://network.pivotal.io) (VMware Tanzu Network) and package upgrade information into your new versions.
29+
* [Publish and update](./publish.html) explains how to publish your tile on [VMware Tanzu Network](https://network.tanzu.vmware.com) (VMware Tanzu Network) and package upgrade information into your new versions.
3030

3131
* [Reference](./reference.html) provides language references for tile elements such as the Service Broker API and the Properties list for tile configuration.
3232

publish.html.md.erb

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ You can publish and update your service tile for <%= vars.platform_name %>.
88
## <a id="publish"></a> Publish your service tile
99

1010
The [Partner software product release cycle](./releases.html) explains how <%= vars.company_name %> works with partners to release VMware Tanzu products,
11-
from the private alpha and closed beta phases, to general availability and publication on [VMware Tanzu Network](http://network.pivotal.io).
11+
from the private alpha and closed beta phases, to general availability and publication on [VMware Tanzu Network](https://network.tanzu.vmware.com).
1212

1313
After you package your product's BOSH releases, stemcell, metadata, and other tile components into a single zipped download file, post it to VMware Tanzu Network in one of two ways:
1414

releases.html.md.erb

+5-5
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ A product must remain in Closed Beta while:
2121
- Users can experience major issues.
2222
- Users must to delete and reinstall tiles rather than upgrading them.
2323

24-
Developers make products in Closed Beta available to specific groups or individual customers on [VMware Tanzu Network](http://network.pivotal.io).
24+
Developers make products in Closed Beta available to specific groups or individual customers on [VMware Tanzu Network](https://network.tanzu.vmware.com).
2525

2626
### Requirements
2727
To enter Closed Beta, a product must meet the following requirements:
@@ -45,7 +45,7 @@ Aa Closed Beta product must include a streamlined method for users to provide fe
4545
### Steps to release
4646
To create a new Closed Beta release for your product:
4747

48-
1. Log in to [VMware Tanzu Network](http://network.pivotal.io).
48+
1. Log in to [VMware Tanzu Network](https://network.tanzu.vmware.com).
4949

5050
1. Create a new release for your product and populate all of the required text boxes.
5151

@@ -67,7 +67,7 @@ Your product is a good candidate for the **Public Beta** stage if:
6767
- The product does not contain the full set of features intended for the final release.
6868
- You feel comfortable supporting this tile for customers.
6969

70-
Products in Public Beta are available on [VMware Tanzu network](http://network.pivotal.io) to any user with a free VMware Tanzu Network account.
70+
Products in Public Beta are available on [VMware Tanzu Network](https://network.tanzu.vmware.com) to any user with a free VMware Tanzu Network account.
7171

7272
### Requirements
7373
Products in Public Beta must meet the following requirements:
@@ -90,7 +90,7 @@ For more information about the security policy, see [<%= vars.platform_name %> S
9090

9191
### Steps to release
9292

93-
1. Log in to [VMware Tanzu Network](http://network.pivotal.io).
93+
1. Log in to [VMware Tanzu Network](https://network.tanzu.vmware.com).
9494

9595
1. Create a new release for your product and populate all of the required text boxes.
9696

@@ -130,7 +130,7 @@ Products must meet the following requirements for **General Availability**:
130130
* Product installation does not require an Internet connection, after initial product download.
131131

132132
### Steps to release
133-
1. Log in to [VMware Tanzu network](http://network.pivotal.io).
133+
1. Log in to [VMware Tanzu Network](https://network.tanzu.vmware.com).
134134

135135
1. Create a new release for your product and populate all of the required text boxes.
136136
1. Email your <%= vars.company_name %> contact to request product validation and General Availability release. Provide basic instructions on how to validate the new feature set. <%= vars.company_name %> validates the upgrade scenario and data persistence.

0 commit comments

Comments
 (0)