User talk:Otto ter Haar

test

signature Otto (talk) 19:18, 18 June 2015 (UTC)

Release Schedule

Please don't update the Release Schedule with an actual until I send the announcement. There's a lot of work between tagging the repo and actually making the release, and plenty that can go wrong and require a re-tag. --John Ralls

In that case it would be easy to correct the entry in the Release Schedule.Otto (talk) 06:55, 29 June 2015 (UTC)

But in the mean time it's wrong, because it says that the release actually happened and it hasn't. You're not the release tech, so unless you're volunteering to take that job over and are actually qualified to do so don't do the release tech's job.

More broadly: If you are going to edit the pages that the development team uses to communicate to the community then you need to engage the development team more directly so that you know what to say. That means discussing changes with them in advance either in gnucash-devel or on IRC. --John Ralls

This is in an open wiki, not a closed one just for developers. So I take the liberty to changes pages if I have reason to believe it is an improvement. In this case my source was the directory http://code.gnucash.org/builds/win32/maint/ where the numbering has been changed to 2.6.7. There are very few contributors to this wiki and more and more regular contributions of the developers on their own initiative should be welcomed. Otto (talk) 14:56, 29 June 2015 (UTC)

Oh, grow up. Liberty brings responsibility. Note that I didn't say "don't edit", I said "engage the development team" so that you actually know what's going on before you eidt. As for the source of your deciding that the release was ready, that's the wrong place to look. That number changes when the version in configure.ac changes, and that's the first step in the release process, not the last. The release is official when the announcement hits the website and the mailing lists. When there are problems that might be several days after bumping the version in configure.ac.