![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
Entry tags:
release tagging
Okay, by request of ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
afuna I am now tagging releases. I am going to adopt the version scheme suggested by damned_colonial:
X.Y.Z
X = major version (closed beta, open beta, release, quarterly milestones, etc)
Y = code push (individual code pushes within a major release)
Z = patches (minor things, probably bug fixes, not part of an announced push)
In this case, last night marked release 0.1.0 of Dreamwidth. A few patches later and things seem stable, so as of a few minutes ago I just tagged us up to 0.1.1.
Tagging is done on all repositories, but since some of our repos move very slowly I do not intend to be tagging them with every single version. The main repository that 99% of our code goes into is of course the dw-free repository. This means that, more than likely, you want to look at that for the latest version of the Dreamwidth code.
This seems more reasonable to me than having to maintain the same list of tags in all of the repositories. Thoughts?
afuna I am now tagging releases. I am going to adopt the version scheme suggested by damned_colonial:X.Y.Z
X = major version (closed beta, open beta, release, quarterly milestones, etc)
Y = code push (individual code pushes within a major release)
Z = patches (minor things, probably bug fixes, not part of an announced push)
In this case, last night marked release 0.1.0 of Dreamwidth. A few patches later and things seem stable, so as of a few minutes ago I just tagged us up to 0.1.1.
Tagging is done on all repositories, but since some of our repos move very slowly I do not intend to be tagging them with every single version. The main repository that 99% of our code goes into is of course the dw-free repository. This means that, more than likely, you want to look at that for the latest version of the Dreamwidth code.
This seems more reasonable to me than having to maintain the same list of tags in all of the repositories. Thoughts?