On Wed, 23 Mar 2022 at 02:07, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> wrote:
> Hello everyone,
>
> I've spent some time lately on looking at the pull-requests on
> jenkinsci/jenkins repository. For some old, inactive pull-requests I've
> pinged the authors and for some, added the
Nothing about release dates was in governance that I know about.
On Tue, Mar 22, 2022 at 6:12 AM 'Ildefonso Montero' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> Hello everyone,
>
> I'm not able to locate the 2.332.2 RC and release events in the calendar:
>
So the request isn't to enable bounty support, but to enable github
issues on the jenkinsci/jenkins repo?
It's not likely to be done any time soon, I think the general
conscensis is to have jira or github enabled, not both for a given
repo, and core is the hardest thing to change. There's so much
Heyo,
that is an interesting proposal. Currently, there are quite a lot of stale
pull requests, whether labeled with a stale-like label or not, which's
state is unclear how to proceed with them.
I think working with labels is easier, instead of converting the PRs into
drafts, because a stale
This seems reasonable to me. After some period of time (months? years?) the
PR is unlikely to be merged, so why keep it open if it's truly stale?
On Tue, Mar 22, 2022 at 9:07 AM Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> wrote:
> Hello everyone,
>
> I've spent some time lately on
Hello everyone,
I've spent some time lately on looking at the pull-requests on
jenkinsci/jenkins repository. For some old, inactive pull-requests I've
pinged the authors and for some, added the proposed-for-close label.
However, the label description nor any prior discussion on the mailing-list
Hello everyone,
I'm not able to locate the 2.332.2 RC and release events in the calendar:
https://www.jenkins.io/events/#event-calendar
Also, I miss the usual request for release lead mail.
Is there something that I missed from the last governance meeting about the
release dates? Not able to
At first, the most easy route seems to fund (add bounty) onto github issues
with services like: (with services like: gitcoin.co, bountysource.com ,
gitpay.me and etc ).
However, Jenkins repository doesn't have 'Issues' tab opened to public
(only Pull Requests are open), thus we are unable to
