Reputation
1,262
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
2 10 21
Impact
~47k people reached

  • 0 posts edited
  • 1 helpful flag
  • 25 votes cast
Aug
21
awarded  Nice Question
Aug
20
comment How do you achieve a numeric versioning scheme with Git?
@JonPurdy Tags are not traditionally used to define a "starting" point, however. In any case, the start will always be the commit tagged as the last release. So I don't see a reason to tag a commit 2 times for this purpose.
Aug
20
comment How do you achieve a numeric versioning scheme with Git?
How can this work when the tag is generated last. Normally you want builds going forward to have the next version of your product. But they will always be forced to use the last version in this case. Only the final, shipped build will have the proper number.
Aug
20
comment Is it good practice to store software version numbers in VCS?
Also between releases, builds will be tied to previously released version instead of the next version (because for weeks, git describe will pick up the tag of the previous release, future builds for the next release will use this number, which is misleading)
Aug
20
comment Is it good practice to store software version numbers in VCS?
I find myself unable to accept this answer, as nice as it sounds, because it has a fundamental flaw: The tag must exist before the build. This does not mesh well with CI build systems, because the builds usually occur immediately on push. And you won't accept something as a release until CI builds and tests are a pass. The flow goes like this: CI Build -> Tests -> Release (Tag) whereas this flow requires: Release (Tag) -> CI Build -> Tests If the build or tests fail, I have a bad tag.
Aug
18
comment Is it good practice to store software version numbers in VCS?
Hmm, I'm not sure what you mean by "you would like it to remain that way". However, you're right that the CI build server controls pretty much everything, especially concerning releases. I guess the real question is: what about our CI server process has to change to support the new SCM-driven release model? It certainly seems as if automated, per-commit builds won't work on the master branch. However, I can't customize the build rules on a per-branch basis without another plan. We're probably getting too bamboo-specific at this point, and risk going off topic.
Aug
18
comment Is it good practice to store software version numbers in VCS?
My point is, that the tag would need to be created in advance of the release so that commits after it are properly versioned with a base number. This goes against the principle of tagging during or at the time of release. Bamboo picks up builds automatically based on commits to master (from develop, remember I'm using gitflow). What if someone pushes a merge to master without a tag? It won't use the proper version (in fact it would use the version of the last release)
Aug
18
comment Is it good practice to store software version numbers in VCS?
I really love this idea, but this seems difficult to manage with JIRA + Bamboo. Bamboo only functions on branches, not tags, so you'd have to make sure a tag is pushed before a build is generated. This is error prone.
Aug
18
comment Is it good practice to store software version numbers in VCS?
@5gon12eder The difficulties or feelings about the merge itself is irrelevant. It's just a negative aspect of the overall solution.
Aug
17
accepted Tracking internal builds versus public builds
Aug
17
accepted When to have bug triage meetings in SCRUM process?
Aug
17
asked Is it good practice to store software version numbers in VCS?
Aug
10
comment When to have bug triage meetings in SCRUM process?
I've heard of "triage meetings" all the time, where QA and sometimes developers get together, look at open issues, and decide if it's a valid issue or not. Close them, assign target versions, etc. Maybe the kind of triage the article is talking about is more agile-specific?
Aug
10
revised When to have bug triage meetings in SCRUM process?
added 677 characters in body
Aug
10
accepted In Agile SCRUM, how do you handle even distribution of work in a sprint between “experts”?
Aug
10
accepted How to setup build system for unit testing + mocking?
Aug
10
asked When to have bug triage meetings in SCRUM process?
Jul
20
awarded  Yearling
Jun
18
comment How to setup build system for unit testing + mocking?
Thanks for the edit. What about symbols that are built into the lib that are used but don't need to be mocked?
Jun
18
comment How to setup build system for unit testing + mocking?
Can you explain more about your first option? How do you do that?