> On 14. Dec 2024, at 18:16, Slawomir Jaranowski wrote:
>
> On Fri, 13 Dec 2024 at 12:12, Gerd Aschemann wrote:
>>
>> I see some drawbacks
>>
>> Before opening a new issue, I would like to search for similar issues (and
>> in particular if there are already solutions, workarcounds, more inf
Hi,
thank you for your summary, which contains every argument I think.
I'm with you and ask for a vote. We all know by the req. Java version
discussion where this will lead if we don't do this (seenoevil)
Am 15.12.2024 um 19:11 schrieb Slawomir Jaranowski:
Hi,
I try summary our discussion a
Hi,
I try summary our discussion about Switch issues to GitHub, so:
At beginning we have a propositions:
1/ try to migrate issues and make JIRA read only
2/ make all our JIRA projects unable to create new issues and new
issues would be raised on GH
3/ do not change JIRA but slowly switch to GH
On Fri, 13 Dec 2024 at 12:12, Gerd Aschemann wrote:
>
> I see some drawbacks
>
> Before opening a new issue, I would like to search for similar issues (and in
> particular if there are already solutions, workarcounds, more information
> about the environment etc.). Where should I search? First d
I see some drawbacks
Before opening a new issue, I would like to search for similar issues (and in
particular if there are already solutions, workarcounds, more information about
the environment etc.). Where should I search? First du a Jira search, then a
GitHub search?
If I find something in
On Mon, 9 Dec 2024 at 18:11, Richard Eckart de Castilho wrote:
>
> How about generating the changelog from the PRs themselves?
>
> https://github.com/apache/uima-parent-pom/blob/main/pom.xml#L1002-L1071
>
It can be next discussion how to technically generate release notes -
in many Maven project
I do agree.
The real work is doing some triage between sections such as: major changes,
bug fixes, dependency updates, build related stuff.
Basically, listing most important things at the beginning, and minor things
at the end on the GitHub release page.
GitHub does a nice thing at generating a sk
How about generating the changelog from the PRs themselves?
https://github.com/apache/uima-parent-pom/blob/main/pom.xml#L1002-L1071
-- Richard
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands,
On Sun, 8 Dec 2024 at 23:03, Elliotte Rusty Harold wrote:
>
> On Sun, Dec 8, 2024 at 9:47 PM Slawomir Jaranowski
> wrote:
> >
> > Hi,
> >
> > I see that more and more PR are not connected to Jira issues ...
> > So we simply take a decision and formally accept what we do
> >
>
> I think that might
tldr; when every JIra issue goes into the release notes, PRs that
don't belong in the release notes should not have Jira issues.
On Sun, Dec 8, 2024 at 10:11 PM Guillaume Nodet wrote:
>
> Le dim. 8 déc. 2024 à 23:03, Elliotte Rusty Harold a
> écrit :
>
> > On Sun, Dec 8, 2024 at 9:47 PM Slawomir
Le dim. 8 déc. 2024 à 23:03, Elliotte Rusty Harold a
écrit :
> On Sun, Dec 8, 2024 at 9:47 PM Slawomir Jaranowski
> wrote:
> >
> > Hi,
> >
> > I see that more and more PR are not connected to Jira issues ...
> > So we simply take a decision and formally accept what we do
> >
>
> I think that mig
On Sun, Dec 8, 2024 at 9:47 PM Slawomir Jaranowski
wrote:
>
> Hi,
>
> I see that more and more PR are not connected to Jira issues ...
> So we simply take a decision and formally accept what we do
>
I think that might be simply related to what the PRs do. Accrual bug
fix and new feature PRs are
Hi,
I see that more and more PR are not connected to Jira issues ...
So we simply take a decision and formally accept what we do
On Sun, 8 Dec 2024 at 11:27, Gerd Aschemann wrote:
>
> For the sake of completeness: I asked Chris Dutz whether he was aware of
> other ASF projects moving from Jira
For the sake of completeness: I asked Chris Dutz whether he was aware of other
ASF projects moving from Jira to GH issues.
* He performed such migration for the PLC4X project (but didn’t leave any tools
to automate that?). Here is a sample for a migrated issue:
https://github.com/apache/plc4x/i
Lets start discuss about convention
https://github.com/apache/maven-site/pull/588
On Wed, 4 Dec 2024 at 19:45, Slawomir Jaranowski wrote:
>
> Hi,
>
> I'm for #2
> - simply add issues to GitHub, disable the creation of new issues in jira.
> - I know that we have many projects ... but we should do
Hi,
I'm for #2
- simply add issues to GitHub, disable the creation of new issues in jira.
- I know that we have many projects ... but we should do it one by one
- if project contains not many open issues we can make it read-only at all
we also need a conventions for GitHub issues like is for Jira
16 matches
Mail list logo
