Help talk:CS1 errors/Archive 2
 | This is an archive of past discussions about Help:CS1 errors. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
| Archive 1 | Archive 2 | Archive 3 | Archive 4 |
Test and implementation processes
As someone who is familiar with professional implementation of computer code, I am familiar with finding bugs in multi-levelled code (down to kernal level), but for someone who is not they would have be pulling their hair out yesterday, and would have had no idea how to work out if it was a problem they had caused or a change elsewhere. While I appreciate that Wikipedia is an encyclopaedia that anyone can edit what are the test and implementation processes that for changing CS1 code?
I am deeply concerned that changes are being made to the functionality of the {{citation}} interfaces for which there have been no RfCs to agree the change in the functionality. This should be the first part change control process so that a functional specification can be generated .... But I assume I am teaching my mother how to suck eggs, because I assume that anyone messing around with this code is familiar with how user specification are drawn up; How a functional specification is generated from that user specification; how code is written from that functional specification and how tests are written to test against the functional specification to test the changes before implantation takes place. Luckily thanks to the history mechanism there is little need for a formal roll back procedure, but there should be a widely advertised forum where implementation errors can be discussed before a roll back takes place (as of course one has to identify cases of false positives). -- PBS (talk) 12:29, 25 August 2014 (UTC)
- I have asked before for some sort of specification or style guide for CS1. The community have thus far declined. Because you are familiar with software implementation, will you write a specification for us?
- In lieu of a formal process, whenever I make changes to Module:Citation/CS1, or to templates outside of this project, I always talk about it. Always. For CS1, changes are always made to the sandbox first; postings where I discuss the changes are usually here (unless started by someone else in some other place). Before I update the live module, I always post a notification here and at WT:AWB with links to the relevant discussions at least a week in advance of the update. All of this so that editors can check my work. This simple set of procedures is mostly effective. It doesn't always work as yesterday demonstrates. Do you have a better process that I should follow?