Skip to content

Relying on Alien4Cloud 2.2.0-SM9 builtin types #38

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Relying on Alien4Cloud 2.2.0-SM9 builtin types #38

wants to merge 1 commit into from

Conversation

laurentganne
Copy link
Contributor

Updated dependency on Alien4Cloud components, from 2.2.0-SM6 to 2.2.0-SM9

@loicalbertin
Copy link
Member

I think we should rely on 2.2.0-SNAPSHOT and tag this branch as 2.2.0-SM9. WDYT?

@laurentganne
Copy link
Contributor Author

I think we should rely on 2.2.0-SNAPSHOT and tag this branch as 2.2.0-SM9. WDYT?

It may have only an interest for internal developers, as only milestones versions of Alien4Cloud are built for customers.
The interest of relying on a milestone version of Alien4Cloud is that customers can use the develop version of the forge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@loicalbertin loicalbertin Awaiting requested review from loicalbertin

@stefbenoist stefbenoist Awaiting requested review from stefbenoist

@adidanes adidanes Awaiting requested review from adidanes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@laurentganne @loicalbertin