Launch Publishing Workflow: Developing within a release cycle ?

Avatar

Avatar
Validate 1
Level 2
Alandy_Iceboats
Level 2

Likes

11 likes

Total Posts

23 posts

Correct reply

2 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 1
Level 2
Alandy_Iceboats
Level 2

Likes

11 likes

Total Posts

23 posts

Correct reply

2 solutions
Top badges earned
Validate 1
Give Back
Boost 5
Boost 3
Boost 10
View profile
Alandy_Iceboats
Level 2

17-10-2019

While Launch allows for the publication of libraries continuously, some of us must adhere to strict release windows

In our scheme, only one person has the ability to publish to production and that can only be done during particular hours on a particular day (every two weeks)

My question is, how can I not be blocked from development while QA and UAT are in progress?

For example. When I complete my dev work within the sprint and submit to Staging (where QA/UAT happens), I want to create a new library in Development to start on my next round of work

However, if the library is rejected and sent back to Development, only ONE library can exist within that environment

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back
Level 2
AnalyticsAlice
Level 2

Likes

10 likes

Total Posts

10 posts

Correct reply

7 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Give Back
Level 2
AnalyticsAlice
Level 2

Likes

10 likes

Total Posts

10 posts

Correct reply

7 solutions
Top badges earned
Give Back
Boost 5
Boost 3
Boost 10
Boost 1
View profile
AnalyticsAlice
Level 2

25-10-2019

Alandy_Iceboats​  Multiple libraries can exist in Dev status but they cannot share the same embed codes, so in this case you'd need to create a new environment. You can do this by going to the Environments tab and selecting "Add Environment".The new environment will have its own unique embed code, allowing you to test only your newest changes and keep them separate from the rejected library.

1847368_pastedImage_1.png

1847668_pastedImage_17.png

It sounds like your team's workflow would not permit merging your newest changes into the rejected library, but technically speaking that would be one option as well.

Answers (0)