Replies: 5 comments 8 replies
-
Overall - I think this is a great idea. I'm much more a proponent of "rolling" releases than Big Version Change releases. How would a January bugfix release work for a December release in your setup? |
Beta Was this translation helpful? Give feedback.
-
@getredash/maintainers What does everyone think of this? 😄 |
Beta Was this translation helpful? Give feedback.
-
Thanks everyone for the feedback! I proposed a github action to update the version string and tag a release candidate each month: |
Beta Was this translation helpful? Give feedback.
-
The periodic action to tag release candidates failed (https://github.com/getredash/redash/actions/runs/6366629264)
I'm not sure what permission needs to be changed. I think one way to solve this is to modify the default permissions granted to the I manually added the tag for October
|
Beta Was this translation helpful? Give feedback.
-
Reopening while we debug the github action |
Beta Was this translation helpful? Give feedback.
-
I have been thinking about the best way to get Redash into a private Jenkins pipeline so that my colleges and I can test it with the many tools we have built around it.
My I suggest that we tag a version with YY.MM every month and add a .NN for releases
Using this scheme we can include Redash in a larger CI pipeline regularly. Aside from the tag, it appears that the version number is also recorded in two files:
Beta Was this translation helpful? Give feedback.
All reactions