thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.2 2010-04-16T20:20:22Z 2010-04-16T20:20:22Z Carl Worth cworth@cworth.org 2010-04-16T20:13:12Z urn:sha1:e6d20b7b8f47bcd5da14639c31a4943e188c070d Finally, a single button to push to do all the uploading. 2010-04-16T20:00:35Z Carl Worth cworth@cworth.org 2010-04-16T20:00:35Z urn:sha1:80240877f836214e556f1ff75a058465a69f2dea Eventually I'd like to automate this so that one or the other of these files is canonical and the other is generated from it. Until then, add this check to the release process to avoid a skewed release being shipped. 2010-04-16T18:34:48Z Carl Worth cworth@cworth.org 2010-04-16T17:58:53Z urn:sha1:0786587f3cf42491629bbd00597b67c221086225 It is annoying to have an extra step here, but it does at least mean that we are back to just "make release" rather than "make VERSION=X.Y release". 2010-04-16T17:23:50Z Carl Worth cworth@cworth.org 2010-04-16T17:23:50Z urn:sha1:ac3dcac7e6d18b787fc65d02a3aa8db3eba805b4 I'd like to have this be fully automated in the future, but for now, it's an extra step. 2010-04-16T03:50:46Z Carl Worth cworth@cworth.org 2010-04-16T03:50:46Z urn:sha1:a29f49b943689e426f0d7c1beba8ac8e76b3d76b We actually want this version to be incremented by the commits that extend the interface. So the release process really is not to just verify two things (NEWS and libnotmuch version), then run "make VERSION=x.y release", and send the mail. Quite nice. 2010-04-16T03:14:54Z Carl Worth cworth@cworth.org 2010-04-16T03:03:30Z urn:sha1:00263dd1a9e08ab1fa947fa58d1c2ad62e8b9653 Where by clean, we check that no files are known to git to be modified. 2010-04-16T02:55:11Z Carl Worth cworth@cworth.org 2010-04-16T02:55:11Z urn:sha1:8700de6fb77fb0ebd7956be7b0a90443ef3e3989 The entire "make sure the code you want is in place" thing is part of a larger release process that we don't document here at all. Instead, we just focus here on the mechanics of pushing things out once the larger process has determined the code is ready. And the fewer steps there are, the better, (for making the release-process as painless as possible and for avoiding any mistakes). 2010-04-15T23:09:43Z Carl Worth cworth@cworth.org 2010-04-15T23:09:43Z urn:sha1:cb08eade5826ff2d9d2057fab95ee68d671d4984 We've now changed to using "git describe" to automatically report a version number that changes with every git commit. So we no longer need to manually update anything in the Makefile during the release process. 2010-04-15T23:08:37Z Carl Worth cworth@cworth.org 2010-04-15T23:08:37Z urn:sha1:f3428823e5cfa8e524e3ea7be8b497020d0693ba This drops one manual step from our release process, (helping to ensure we don't forget anything during the release). 2010-04-10T02:12:36Z Carl Worth cworth@cworth.org 2010-04-10T02:12:36Z urn:sha1:e1bc5fc9c7766fb53f687dbca2db3dd9d0df0e9f We pass this in on the "make release" command-line rather than editing the Makefile.