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
Now, we want to start testing 5.0rc1 with some projects. This image have some changes.
We want to create a Feature flag that "no matter has the user selected for the docker image we want to use 5.0rc for container_image" when building the docs.
Once we have this feature added, we can start with 100, 500, 1500 and 5000 projects for a month and half and after that, release the new image.
The text was updated successfully, but these errors were encountered:
Yes, but we don't want to do that avoid future miss-understandings. We just released these images and we didn't know why there were projects with 4.0rc1, it it was because we wanted to test the image or because they needed something specific from that image. Now, we want to avoid that confusion by creating a Feature flag.
This flag, will be useful to test all the rc releases, not just this one in particular.
We just released
4.0
and5.0rc1
.So,
2.0
got deprecated3.0
becamestable
4.0
becamelatest
Now, we want to start testing
5.0rc1
with some projects. This image have some changes.We want to create a Feature flag that "no matter has the user selected for the docker image we want to use
5.0rc
forcontainer_image
" when building the docs.Once we have this feature added, we can start with 100, 500, 1500 and 5000 projects for a month and half and after that, release the new image.
The text was updated successfully, but these errors were encountered: