Difference between revisions of "User talk:Otto ter Haar"
(→Release Schedule) |
(Behavior guidance) |
||
| Line 5: | Line 5: | ||
Please don't update the [[Release_Schedule|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 | Please don't update the [[Release_Schedule|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.[[User:Otto ter Haar|Otto]] ([[User talk:Otto ter Haar|talk]]) 06:55, 29 June 2015 (UTC) | :In that case it would be easy to correct the entry in the Release Schedule.[[User:Otto ter Haar|Otto]] ([[User talk:Otto ter Haar|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 | ||
Revision as of 14:30, 29 June 2015
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
