Got it. I have access now. Thanks for your help.
Kevin
On Wed, Mar 30, 2016 at 4:18 PM, Baptiste Mathus wrote:
> Hi,
> Curious what led people to think that, but for future reference no, it's
> not enough to just edit the pom.
> But it's indeed really recommended to keep that section up-to
Hi,
Curious what led people to think that, but for future reference no, it's
not enough to just edit the pom.
But it's indeed really recommended to keep that section up-to-date since
this one is then used to generate the wiki page and show the current
maintainer(s).
The typical way to do that is t
Hey, acknowledging this. Gyus from IRC said adding one more developer section
in pom.xml is enough to be permited to commit to repo, but seems somenthing
went wrong.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from thi
Repo:
- https://github.com/jenkinsci/ease-plugin
Github ID:
- kwilson6744
Jenkins-CI ID:
- kwilson6744
The original developer of this plugin added me as a maintainer 2 months ago
but it appears I still do not have write access.
https://github.com/jenkinsci/ease-plugin/