Skip to content

Existing j3 issues #38560

Answered by zero-24
brianteeman asked this question in General
Aug 23, 2022 · 3 comments · 18 replies
Discussion options

You must be logged in to vote

Yes this is the plan. It had been done for the 3.10-dev PRs but I did not had the time yet to to througth the issues flagged as J3 relevant.

About new PRs we had such message for 2.5 when i remember correctly that was done via the bot in the past and pretty harsh (maybe my memmory fools me on this). Not sure whether that is a good way of doing it? What do you think? Could you propose a text we could use there? Basicly saying the same as for issues but targeted at PRs created against 3.10-dev. As long as its not a massive it could also be done manually i guess.

Replies: 3 comments 18 replies

Comment options

You must be logged in to vote
16 replies
@zero-24
Comment options

@brianteeman
Comment options

@brianteeman
Comment options

@zero-24
Comment options

@zero-24
Comment options

Answer selected by brianteeman
Comment options

You must be logged in to vote
1 reply
@brianteeman
Comment options

Comment options

You must be logged in to vote
1 reply
@zero-24
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants