You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: brokered.html.md.erb
+1-1
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ service tile for <%= vars.platform_name %>.
9
9
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.
10
10
11
11
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
13
13
Tanzu Operations Manager Installation Dashboard.
14
14
15
15
The service broker eliminates the need for you to know the URLs and
Copy file name to clipboardexpand all lines: dev-workflow.html.md.erb
+1-1
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ how tiles are structured.
26
26
27
27
* [Tile documentation](./tile-documentation.html) explains how to document your tile as part of [<%=vars.platform_name%> documentation](http://docs.pivotal.io).
28
28
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.
30
30
31
31
* [Reference](./reference.html) provides language references for tile elements such as the Service Broker API and the Properties list for tile configuration.
Copy file name to clipboardexpand all lines: publish.html.md.erb
+1-1
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ You can publish and update your service tile for <%= vars.platform_name %>.
8
8
## <aid="publish"></a> Publish your service tile
9
9
10
10
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).
12
12
13
13
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:
Copy file name to clipboardexpand all lines: releases.html.md.erb
+5-5
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ A product must remain in Closed Beta while:
21
21
- Users can experience major issues.
22
22
- Users must to delete and reinstall tiles rather than upgrading them.
23
23
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).
25
25
26
26
### Requirements
27
27
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
45
45
### Steps to release
46
46
To create a new Closed Beta release for your product:
47
47
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).
49
49
50
50
1. Create a new release for your product and populate all of the required text boxes.
51
51
@@ -67,7 +67,7 @@ Your product is a good candidate for the **Public Beta** stage if:
67
67
- The product does not contain the full set of features intended for the final release.
68
68
- You feel comfortable supporting this tile for customers.
69
69
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.
71
71
72
72
### Requirements
73
73
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
90
90
91
91
### Steps to release
92
92
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).
94
94
95
95
1. Create a new release for your product and populate all of the required text boxes.
96
96
@@ -130,7 +130,7 @@ Products must meet the following requirements for **General Availability**:
130
130
* Product installation does not require an Internet connection, after initial product download.
131
131
132
132
### 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).
134
134
135
135
1. Create a new release for your product and populate all of the required text boxes.
136
136
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