Oct. 26th, 2009

mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark
Okay, by request of [personal profile] afuna I am now tagging releases. I am going to adopt the version scheme suggested by [personal profile] 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?

Profile

dw_dev: The word "develop" using the Swirly D logo.  (Default)
Dreamwidth Open Source Development

July 2025

S M T W T F S
  12345
6789101112
13141516171819
20212223 242526
2728293031  

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Aug. 29th, 2025 08:56 am
Powered by Dreamwidth Studios