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

Change npm package scope to @hyperledger-labs #28

Closed
petermetz opened this issue Nov 6, 2019 · 0 comments · Fixed by #38
Closed

Change npm package scope to @hyperledger-labs #28

petermetz opened this issue Nov 6, 2019 · 0 comments · Fixed by #38
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request good-first-issue Good for newcomers
Milestone

Comments

@petermetz
Copy link
Contributor

Received the recommendation on Rocket chat that we should publish under the labs scope when we are in the labs stage.
I raised the issue of migration effort and the answer was that it is acceptable to publish under multiple different names to save early adopters the headache.

Target new package scope:
@hyperledger-labs/blockchain-integration-framework

Once we graduate we can publish the same package under all these aliases in parallel if need be:
@hyperledger-labs/blockchain-integration-framework
@hyperledger/blockchain-integration-framework
and potentially of course whatever the final project name will end up being
@hyperledger/$FINAL_PROJECT_NAME

@petermetz petermetz added documentation Improvements or additions to documentation enhancement New feature or request good-first-issue Good for newcomers labels Nov 6, 2019
@petermetz petermetz added this to the v0.1.0 milestone Nov 6, 2019
@petermetz petermetz self-assigned this Nov 6, 2019
@petermetz petermetz removed this from the v0.1.0 milestone Nov 6, 2019
@jonathan-m-hamilton jonathan-m-hamilton added this to the v0.1.0 milestone Nov 13, 2019
blefevre pushed a commit to blefevre/blockchain-integration-framework that referenced this issue Feb 4, 2020
Fixes hyperledger-cacti#28
We'll be allowed to use the @hyperledger scope once the project
graduates from the labs.
At that point we can publish the same package contents under multiple package
scopes for each new release to spare early adopters the migration
effort.

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request good-first-issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants