Hi! On Tue, 23 Sep 2014 16:19:02 +0200, Justus Winter <4win...@informatik.uni-hamburg.de> wrote: > I understand you took care of the release process last time. Is this > process documented somewhere? I think that we should make another > round of releases. In fact, we should make one or two releases each > year. At the very least it brings us quite a bit of attention. > > If it's just a matter of doing this or that, please let me know how I > can contribute to this process.
The (technical) release process is not the problem; that I can do any time. For me, the question rather is, what constitutes the releases that we publish? Some new, exciting features (including considerable bug fixing, code re-writes, re-factoring, and so on), on the one hand, or regular time-based releases on the other (for example, annually). The former has the process that the new features are added, and then there is a stabilization period where only bug fixes go in, then the release is made, and the latter is basically just a snapshot of the repository at a more or less "random" date. Due to lack of manpower to maintain a "proper" release process, I see us more on the side of doing snapshots, which we can do any time we like. Now is a good time, you say? (I'm not disagreeing -- the previous release having been one year ago.) Given this, and with our last Hurd release having been 0.5, what would the next version be? 0.5.1? 0.6? Or, make it obvious that it is just a snapshot, and thus call that GNU Hurd 20140923 or similar? Grüße, Thomas
pgpbR8NwZMqCe.pgp
Description: PGP signature