Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refer the database schema scripts from the latest Git release corresponding to the API Management version #111

Open
chirangaalwis opened this issue Nov 24, 2019 · 2 comments

Comments

@chirangaalwis
Copy link
Member

Description:
As of now (i.e. pivotal-cf/docs-wso2-api-manager@cf39e24), the official documentation of the WSO2 API Management v2.6.0 PCF Tile refers to the 2.6.x Git development branch for the product profile database schema scripts [1].

As the Git release tags of WSO2 installation resources can be regarded most stable rather than the corresponding development branch, I suggest referencing the most latest, Git release tag of the PCF resources corresponding to the product-version in the official documentation [1].

@ThilinaManamgoda, @msmshariq and @VimukthiPerera WDYT?

[1]: Official Documentation

Affected Product Version:
Official documentation of WSO2 API Management v2.6.x PCF Tile

@ThilinaManamgoda
Copy link
Contributor

@chirangaalwis What if we create Github Gist instead since these scripts don't change frequently.

@chirangaalwis
Copy link
Member Author

chirangaalwis commented Nov 25, 2019

@ThilinaManamgoda as per the internal discussion, we will start referring to the master branch's database scripts in the latest product version's resource documentation, as this branch will always refer to the latest resource release for the latest version of the product.

@NishikaDeSilva please note.

In the case of documentation for the older versions of the product, we may have to refer to the latest platform resource release tag for that particular product version. WDYT?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants