The CAPTCHA was a surprise for me :( It appears on the top of the page, but noting fields are located in the bottom (Firefox).
It took some time to find the captcha, but IMO the spam protection worth some inconveniences воскресенье, 2 ноября 2014 г., 6:23:45 UTC+3 пользователь R Tyler Croy написал: > > (replies inline) > > On Sat, 01 Nov 2014, Christoph Kutzinski wrote: > > > Can someone with administrative power block the Wiki spam account "adib > > samsul"? > > I've nuked that person's account from orbit. > > > I also went ahead and temporarily enabled captchas for all users to help > deter > spam, we'll see how quickly we get complaints. > > > > > > -------- Weitergeleitete Nachricht -------- > > > > > > > > > > > > > > > > > > > > > > > > Space: Jenkins (https://wiki.jenkins-ci.org/display/JENKINS) > > Page: Issue Tracking ( > https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking) > > > > > > Edited by adib samsul: > > --------------------------------------------------------------------- > > {note}The Jenkins JIRA is not a support site. If you need assistance or > have general questions, visit us [in chat| > http://jenkins-ci.org/content/chat], or email one of the [mailing lists| > http://jenkins-ci.org/content/mailing-lists].{note} > > > > h1. How to report a bug, request an improvement, or propose a new > feature > > > > Please see the following wiki page for guidelines on how to create an > issue: [How to report an issue] > > > > > > h1. Lifecycle of an issue > > > > h3. Issue States > > > > Developers don't use the various issue states consistently. The > following description just gives a broad overview. [See here for a > description of states in JIRA| > http://issues.jenkins-ci.org/secure/ShowConstantsHelp.jspa#StatusTypes]. > > > > * Issues start out as *Open*. > > * When work has begun but not finished, the *Assignee* will often mark > the issue *In progress*. > > * When finished and a solution is checked in, the *Assignee* (or a bot > responding to commit messages) will mark the issue *Resolved* > > * Some users also mark issues *Closed* after a fix is confirmed by > others. > > * When an issue was resolved or closed before, but users still > experience the same problem, they may set the issue to *Reopened*. > > > > h3. Issues not requiring a change > > > > If an issue is considered to be a *Duplicate*, it will be marked as > resolved, and the original issue will be linked. It's not always the newer > issue that gets closed as duplicate, sometimes it's the older one, e.g. > when the description in the new one is better, or the new one has more > watchers. This depends on the developer resolving as duplicate. [obat > pembesar penis permanen|http://obatpermanen.com] > > > > > > Issues may be found to be *Won't Fix* or *Not a Defect* for various > reasons, e.g. when a developer determines that the issue isn't actually a > problem with Jenkins. > > > > Issues may be resolved as *Cannot Reproduce* when the developer is > unable to reproduce the issue as described, e.g. because it may have been > resolved since it was reported, or it is believed the issue is not with > Jenkins. [alat bantu sex aman|http://alatbatusexaman.com] > > > > > > Issues resolved as *Incomplete* do not provide a sufficient description > of the problem. > > > > h3. Issues requiring a change > > > > When a developer decides to work on such an issue, the *Assignee* field > is changed to that developer. It may be set to *In progress* while it's > being worked on.[obat aman|http://obataman.com] > > > > > > When a fix has been integrated, the issue is usually marked *Resolved* > (using the resolution *Fixed*), and sometimes marked *Closed* after the fix > has been verified. > > > > h1. Quick Links > > > > If you want to link to a Jenkins bug with a short URL, use e.g.: [ > http://jenkins-ci.org/issue/1234] instead of [ > https://issues.jenkins-ci.org/browse/JENKINS-1234] > > > > Change your notification preferences: > https://wiki.jenkins-ci.org/users/viewnotifications.action > > > > > > > > -- > > You received this message because you are subscribed to the Google > Groups "Jenkins Developers" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > > - R. Tyler Croy > > ------------------------------------------------------ > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F > ------------------------------------------------------ > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
