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
Can you please start using github releases already?
branch version2.1.1 is more then a month older than version2.1.0, why is that? 2.1.0 is newer than 2.1.1??
there's also test_version_2.1.0 with recent commtis, it's unstable?
master branch has very few config files and sql scripts, I take it as it doesn't represent any working version?
Overall if you don't want to use releases, maybe provide a readme in master, saying which branch is which? Maybe start calling branches differently with versions growing in chronological order?
The text was updated successfully, but these errors were encountered:
I see that Version2.1.0 branch have newer commits from time to time, shouldn't these commits be tagged as 2.1.1 then 2.1.2 then 2.1.3, etc... instead of using the branch as the version?
The reason I ask is because we would be able to checkout to a tag with a specific version and get it deployed on all envs (dev stage and prod). With the current workflow every time I run a pipeline gitlab will clone this repository and checkout to Version2.1.0 branch but this is not guaranteed that all envs will have the same version running. Dev pipelines runs much more frequently than stage and prod thus fetching the new commits often
When will the version2.1.0 branch get merged into master?
Can you please start using github releases already?
version2.1.1
is more then a month older thanversion2.1.0
, why is that? 2.1.0 is newer than 2.1.1??test_version_2.1.0
with recent commtis, it's unstable?master
branch has very few config files and sql scripts, I take it as it doesn't represent any working version?Overall if you don't want to use releases, maybe provide a readme in master, saying which branch is which? Maybe start calling branches differently with versions growing in chronological order?
The text was updated successfully, but these errors were encountered: