@Kohsuke. I disagree with your statement as well. On-request direct push/release permissions will lead to the violation of common plugin development practices (compatibility, core dependencies, etc.).
If a person wants to contribute and get the new version ASAP, it's better to provide a review of his pull pull request and then merge and release it if everything is OK. понедельник, 8 июня 2015 г., 22:42:54 UTC+3 пользователь Kanstantsin Shautsou написал: > > >> As a rule of thumb, I'd like to reduce us blocking people who are >> interested in contributing, so we should grant the commit access in >> parallel to suggesting to talk to the current maintainer. >> > Sorry but i don't like such idea. Plugins had not enough quality at all > and initial maintainer/dev always providing feedback that enforces > reworking code. > I will prefer to see and require for new plugins instructions whether such > thing is allowed (or repo based doc in cause of maintainers disappearing). > I don't think that everybody (50k installations?) will be happy if i commit > directly and release git plugin while 2 maintainers will be unavailable. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/330344a3-0c82-4e07-bee0-7f143dccbd56%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
