Re: Using test distribution & Apache's Jenkins pipelines was: Time it takes for Test PHP Cluster
Dne pátek 24. září 2021 17:25:39 CEST, Eric Barboni napsal(a): > Hi, > > I juste retrieved an old mail for Jaroslav. ;-) > I'm a bit "irritated" because of > CI. I'm haunted by the "restart job button". I can live with the "restart button", but I agree: Such frequent failures aren't professional. > Is a only Apache jenkins build + PR review something we can do ? > or would we have some limitation and should rely also on GA or travis too? > > > Hector started something https://github.com/apache/netbeans/pull/2443 to do > jenkins PR test. > > BUT on jenkins > This build trigger test error: > https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux/ > ant build test-platform build-nbms generate-uc-catalog build-source-zips > => 1 issue on > org.openide.filesystems.annotations.LayerBuilderTest.testSourcePath The > same ant call on my ubuntu > => 0 issue > > Complicated to trust jenkins too. > But I would like to see the CI issues tackled so Release Manager,commiter, > reviewers may have better life :D. -- +1 My original may was however about "test distribution" - e.g. build the IDE and the test distribution once, and then use it for running the tests across different nodes. Yes, Jenkins pipelines (on Apache own infra) would be ideal for that I think. -jt > -Message d'origine- > De : Jaroslav Tulach > Envoyé : lundi 26 avril 2021 06:16 > À : dev@netbeans.apache.org > Cc : Petr Zajac > Objet : Using test distribution & Apache's Jenkins pipelines was: Time it > takes for Test PHP Cluster > Dne pátek 16. dubna 2021 18:53:31 CEST, Tomáš Procházka napsal(a): > > I stareted conversion of other jobs > > (https://github.com/apache/netbeans/pull/2708) but stopped given > > current status of Github Actions > > (https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+sta > > tus) > > Hello guys, > maybe there is a time to improve the structure of build jobs and to increase > the throughput by eliminating duplicated tasks. > > These days every job builds the IDE, builds the tests and then it executes > some tests. We can do better than that! There has been a "test > distribution" in NetBeans for years and according to its creator Petr > Zajac, it is still working! > > It would be good to have one job that builds the ZIP of the IDE and builds > the ZIP for the test distribution. Only then other "testing" jobs are > started, download the two ZIP files and use them to perform the tests only. > > Btw. When at it, shouldn't we consider to use https://ci-builds.apache.org/ > ? It is an infrastructure that fully runs on Apache's hardware - e.g. we > aren't going to be influenced deals with external providers like Travis or > Azure. Moreover Jenkins supports pipelines to pass the ZIPs from one job to > another... > > Together we can save the planet! > -jt > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Jira: NetBeans 12.5 still unreleased
Hi, NetBeans 12.5 is still marked as unreleased in Jira: https://issues.apache.org/jira/projects/NETBEANS?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=unreleased Cheers Benjamin - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Apache JIRA vs GitHub issues / discussions
On Fri, 24 Sept 2021 at 14:01, Eric Bresie wrote: > When adding a link in JIRA on a ticket to the PR it seems to link up > there. Is the concern this is a manual step instead of more automated? > > Is the concern the # of JIRA tickets not going down? If it switched to > GitHub would that change really? Is it really just people dedicated to > management of the tickets? ... > Seems like some of this is some features are being used in JIRA and others > in GitHub which are in many ways competing products Any / all of the above! I certainly don't think it's a panacea. Might it help change things, possibly. All I know is that over the releases I've been involved in, JIRA has seemed more and more unwieldy. It's difficult to get a real sense of release progress, and what are true critical and blocking issues for release. There's a load of tickets that should have been closed, have entirely the wrong priority, or milestone. Just having one place with common sign-in, common milestones, automatic closing on merges, etc. would at least help. The linked post just struck a chord with me, which is why I shared. You might need to be subscribed to the list to read it though. More eyes on everything would of course help even more! As well as people happy to explain why someone's bug is being moved from blocker to minor when justified. :-) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Remove JAR and NBM files from archive (was: Re: [DISCUSS] JAR files in Apache NetBeans 12.5 release)
Hi again, so I decided to go full JAR and NBM killer - with this PR: https://github.com/apache/netbeans/pull/3162 applied I get: matthias@enterprise:~/src/netbeans$ find . -iname "*.jar" -type f matthias@enterprise:~/src/netbeans$ find . -iname "*.nbm" -type f There are other archives, but I think this might be worth it. Opinions? Greetings Matthias Am Samstag, dem 11.09.2021 um 19:58 +0200 schrieb Matthias Bläsing: > Hi, > > I'm mildly irritated, that trivial JARs are considered a problem for > the 12.5 release, while a huge pile of files is completely excluded > from RAT scanning. > > I had a closer look at the JARs come down to this: > > > ./java/maven/test/unit/data/mavenmock/3.3.1/lib/fake331.jar > ./java/maven/test/unit/data/mavenmock/3.0.5/lib/fake305.jar > ./java/maven/test/unit/data/mavenmock/4.0.0/lib/fake400.jar > ./java/maven/test/unit/data/mavenmock/2.2/lib/fake221.jar > > - trivial pom.properties + MANIFEST.MF (both text files) > > > ./java/maven/test/unit/data/mavenmock/source.jar > > - trivial pom.properties + pom.xml + MANIFEST.MF (all text files) > > > ./platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdat > e/data/empty.jar > > - trivial MANIFEST.MF > > > ./enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar > ./enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar > ./enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar > ./enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar > > - one byte files > > > There is IMHO _nothing_ in this, that warrants doubts on the > cleanliness of the release. > > I'll see if I can remove them all all, but for 12.5 IMHO this is out of > scope and also unnessary. > > Greetings > > Matthias, putting away the zip tool for now > > > Am Samstag, dem 11.09.2021 um 18:34 +0100 schrieb Neil C Smith: > > On Sat, 11 Sept 2021 at 17:08, Laszlo Kishalmi > > wrote: > > > The only thing bothers me, that there are 5 new jars under > > > java/maven/test/unit/data/mavenmock > > > > > > They are only test data, but they are real jars indeed. It seems that > > > one even slipped through the 12.4 phase (I have not checked the jars > > > that time.) Introduced in 95d4fd144eabe7dfc07fe7c5e7c8d81e1e26d013 > > > > They certainly didn't slip through in 12.4, and they're allowable if > > they don't contain executable code. Same as a few .zip files we have. > > They were checked for that - it's even the reason for my comments on > > this legal thread at the time > > https://lists.apache.org/thread.html/rcddc30dd1f0c7f20709e09de7202d4d6885d6235a7fce1c1ab46e4ed%40%3Clegal-discuss.apache.org%3E > > > > Mentioning here as you (or anyone else) might want to review and > > verify they're allowable in voting. > > > > > It might be not a show stopper, but we have to take a remedy action that > > > these jars would be generated from real source during build time in the > > > next release. > > > > Real source might be a moot point, but whether the .jar and .zip files > > we have should be generated is probably worth some thought, as > > archives in general make reviewing more difficult (mentioned by others > > in same legal thread above). That bit is a discussion we should move > > off the vote thread though. > > > > Best wishes, > > > > Neil > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > > For additional commands, e-mail: dev-h...@netbeans.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Release Team for 12.6?
On Fri, 24 Sept 2021 at 14:53, Glenn Holmer wrote: > On 9/24/21 03:39, Geertjan Wielenga wrote: > > Who'd like to volunteer to join Neil and me on the release team for 12.6? Me! Although I seem to have been volunteered already. :-) > > What you'll be doing -- verifying issues, trying out builds, giving > > feedback, being the go-to people around the time of the release, coming up > > in the next month or two, help identify the important bugs to be fixed, etc. ... > > Sounds like NetCAT :) Agreed! Some of those are not what my original release team idea was about. Which was to replace the single release manager per release with a small group of people who share those jobs, and work (to varying amounts) across all releases. ie. no one single contact, no trying to find an RM for the next release, etc. At the moment, that would mean that the release team is probably limited to PMC members. Theoretically ASF projects can allow committers to be release managers, but we're not set up for that at the moment. Other than managing the release tasks, and turning the go-to person into go-to people, I'd be wary of making it seem like the rest of those things are specific to the release team. In my opinion, everything else listed is the common responsibility of everyone on this list! Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Using test distribution & Apache's Jenkins pipelines was: Time it takes for Test PHP Cluster
Hi, I juste retrieved an old mail for Jaroslav. I'm a bit "irritated" because of CI. I'm haunted by the "restart job button". Is a only Apache jenkins build + PR review something we can do ? or would we have some limitation and should rely also on GA or travis too? Hector started something https://github.com/apache/netbeans/pull/2443 to do jenkins PR test. BUT on jenkins This build trigger test error: https://ci-builds.apache.org/job/Netbeans/job/netbeans-linux/ ant build test-platform build-nbms generate-uc-catalog build-source-zips => 1 issue on org.openide.filesystems.annotations.LayerBuilderTest.testSourcePath The same ant call on my ubuntu => 0 issue Complicated to trust jenkins too. But I would like to see the CI issues tackled so Release Manager,commiter, reviewers may have better life :D. -- Best Regards Eric -Message d'origine- De : Jaroslav Tulach Envoyé : lundi 26 avril 2021 06:16 À : dev@netbeans.apache.org Cc : Petr Zajac Objet : Using test distribution & Apache's Jenkins pipelines was: Time it takes for Test PHP Cluster Dne pátek 16. dubna 2021 18:53:31 CEST, Tomáš Procházka napsal(a): > I stareted conversion of other jobs > (https://github.com/apache/netbeans/pull/2708) but stopped given > current status of Github Actions > (https://cwiki.apache.org/confluence/display/BUILDS/GitHub+Actions+sta > tus) Hello guys, maybe there is a time to improve the structure of build jobs and to increase the throughput by eliminating duplicated tasks. These days every job builds the IDE, builds the tests and then it executes some tests. We can do better than that! There has been a "test distribution" in NetBeans for years and according to its creator Petr Zajac, it is still working! It would be good to have one job that builds the ZIP of the IDE and builds the ZIP for the test distribution. Only then other "testing" jobs are started, download the two ZIP files and use them to perform the tests only. Btw. When at it, shouldn't we consider to use https://ci-builds.apache.org/ ? It is an infrastructure that fully runs on Apache's hardware - e.g. we aren't going to be influenced deals with external providers like Travis or Azure. Moreover Jenkins supports pipelines to pass the ZIPs from one job to another... Together we can save the planet! -jt - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Release Team for 12.6?
People will assign tasks to themselves. The point is for this to be lightweight and with a small group of volunteers who want to try things out, give quick feedback on fixes and features, etc. Join in, Glenn. :-) Gj On Fri, Sep 24, 2021 at 3:58 PM Eric Bresie wrote: > Didn't there used to be a "Release" JIRA ticket with all the "sub-tasks" > defined underneath it? Then they can be assigned or volunteered as > applicable. > > Eric Bresie > ebre...@gmail.com > > > On Fri, Sep 24, 2021 at 8:53 AM Glenn Holmer > wrote: > > > On 9/24/21 03:39, Geertjan Wielenga wrote: > > > Who'd like to volunteer to join Neil and me on the release team for > 12.6? > > > > > > What you'll be doing -- verifying issues, trying out builds, giving > > > feedback, being the go-to people around the time of the release, coming > > up > > > in the next month or two, help identify the important bugs to be fixed, > > etc. > > > > > > Not all of these will be done by anyone, just a few of these, those > that > > > you're most comfortable with and can fit into your schedule. > > > > Sounds like NetCAT :) How will you be assigning tasks to the volunteers? > > > > -- > > Glenn Holmer (Linux registered user #16682) > > "After the vintage season came the aftermath -- and Cenbe." > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > > For additional commands, e-mail: dev-h...@netbeans.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > >
Re: Release Team for 12.6?
Didn't there used to be a "Release" JIRA ticket with all the "sub-tasks" defined underneath it? Then they can be assigned or volunteered as applicable. Eric Bresie ebre...@gmail.com On Fri, Sep 24, 2021 at 8:53 AM Glenn Holmer wrote: > On 9/24/21 03:39, Geertjan Wielenga wrote: > > Who'd like to volunteer to join Neil and me on the release team for 12.6? > > > > What you'll be doing -- verifying issues, trying out builds, giving > > feedback, being the go-to people around the time of the release, coming > up > > in the next month or two, help identify the important bugs to be fixed, > etc. > > > > Not all of these will be done by anyone, just a few of these, those that > > you're most comfortable with and can fit into your schedule. > > Sounds like NetCAT :) How will you be assigning tasks to the volunteers? > > -- > Glenn Holmer (Linux registered user #16682) > "After the vintage season came the aftermath -- and Cenbe." > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >
Re: Release Team for 12.6?
On 9/24/21 03:39, Geertjan Wielenga wrote: Who'd like to volunteer to join Neil and me on the release team for 12.6? What you'll be doing -- verifying issues, trying out builds, giving feedback, being the go-to people around the time of the release, coming up in the next month or two, help identify the important bugs to be fixed, etc. Not all of these will be done by anyone, just a few of these, those that you're most comfortable with and can fit into your schedule. Sounds like NetCAT :) How will you be assigning tasks to the volunteers? -- Glenn Holmer (Linux registered user #16682) "After the vintage season came the aftermath -- and Cenbe."null - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Apache JIRA vs GitHub issues / discussions
I logged in and can't seem to get to that thread. Eric Bresie ebre...@gmail.com On Thu, Sep 23, 2021 at 9:43 AM Neil C Smith wrote: > Hi, > > I've long felt that our use of JIRA and poor integration with the PR > process, etc. is more of a hindrance than a help, particularly during > releases. This email just popped up on users@infra (needs sign in) > about Apache Airflow's switch a couple of years back. Found it very > interesting - food for thought? > > > https://lists.apache.org/thread.html/r65aae462b9f26454adaf9e5854dda06b2acd10273cb1b34b3e6b1227%40%3Cusers.infra.apache.org%3E > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Apache JIRA vs GitHub issues / discussions
When adding a link in JIRA on a ticket to the PR it seems to link up there. Is the concern this is a manual step instead of more automated? Is the concern the # of JIRA tickets not going down? If it switched to GitHub would that change really? Is it really just people dedicated to management of the tickets? If so (think I mentioned this before but) is some form if change control needed? Maybe a CCB mailing list is needed to focus on this sort of thing? JIRA provides dashboards and burn down reports which can help monitor things as well ( https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333642) Not sure if this helps any or if this is already in use in some way but JIRA has integration with GitHub. https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/ Atlassian suite offers bitbucket, review, CI, and other related tool sets. Is this maybe partly an issue that those are not in use on the project? Assume having those involved would possibly be an additional cost for usage. Seems like some of this is some features are being used in JIRA and others in GitHub which are in many ways competing products Eric On Fri, Sep 24, 2021 at 7:16 AM Christian Lenz wrote: > I see a big Benefit out of it also to have everything in one application > (Pipeline, Discussions, Issues, etc.). As the other one, on the other > mailinglist already mentioned: > > > That was such an amazing improvement in the overall workflow and > contributor's engagement > > > Cheers > > Chris > > > Von: Eric Barboni > Gesendet: Freitag, 24. September 2021 13:29 > An: dev@netbeans.apache.org > Betreff: RE: Apache JIRA vs GitHub issues / discussions > > I don't know. Would be happy with both. I suspect, we will still have lots > of opened untackled issue on git issue too. > > Would be good to hear from major our major contributor. > > Best Regards > Eric > > -Message d'origine- > De : John Mc > Envoyé : jeudi 23 septembre 2021 22:42 > À : dev > Objet : Re: Apache JIRA vs GitHub issues / discussions > > Interesting point, > > JIRA seems very decoupled from everything else at the moment. We have a > lot of open tickets there ~3000 and we're not doing a great job keeping an > eye on it. > > it might allow people to raise bugs more freely as more users would have > GH accounts then Apache JIRA accounts so it make it easier for users to > submit bugs.. > > Regards > > John > > On Thu, 23 Sept 2021 at 15:43, Neil C Smith wrote: > > > Hi, > > > > I've long felt that our use of JIRA and poor integration with the PR > > process, etc. is more of a hindrance than a help, particularly during > > releases. This email just popped up on users@infra (needs sign in) > > about Apache Airflow's switch a couple of years back. Found it very > > interesting - food for thought? > > > > > > https://lists.apache.org/thread.html/r65aae462b9f26454adaf9e5854dda06b > > 2acd10273cb1b34b3e6b1227%40%3Cusers.infra.apache.org%3E > > > > Best wishes, > > > > Neil > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > > For additional commands, e-mail: dev-h...@netbeans.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > -- Eric Bresie ebre...@gmail.com
Re: Apache JIRA vs GitHub issues / discussions
GitHub issues are better and people know it and use it more than JIRA. I think that Spring prove that using GitHub issues instead of JIRA good way. For example I have problem with Apache JIRA that you have search only in the NetBeans project. But it is only my opinion. On the other hand this would be the second migration of issues in "short" time. On Fri, Sep 24, 2021, 14:16 Christian Lenz wrote: > I see a big Benefit out of it also to have everything in one application > (Pipeline, Discussions, Issues, etc.). As the other one, on the other > mailinglist already mentioned: > > > That was such an amazing improvement in the overall workflow and > contributor's engagement > > > Cheers > > Chris > > > Von: Eric Barboni > Gesendet: Freitag, 24. September 2021 13:29 > An: dev@netbeans.apache.org > Betreff: RE: Apache JIRA vs GitHub issues / discussions > > I don't know. Would be happy with both. I suspect, we will still have lots > of opened untackled issue on git issue too. > > Would be good to hear from major our major contributor. > > Best Regards > Eric > > -Message d'origine- > De : John Mc > Envoyé : jeudi 23 septembre 2021 22:42 > À : dev > Objet : Re: Apache JIRA vs GitHub issues / discussions > > Interesting point, > > JIRA seems very decoupled from everything else at the moment. We have a > lot of open tickets there ~3000 and we're not doing a great job keeping an > eye on it. > > it might allow people to raise bugs more freely as more users would have > GH accounts then Apache JIRA accounts so it make it easier for users to > submit bugs.. > > Regards > > John > > On Thu, 23 Sept 2021 at 15:43, Neil C Smith wrote: > > > Hi, > > > > I've long felt that our use of JIRA and poor integration with the PR > > process, etc. is more of a hindrance than a help, particularly during > > releases. This email just popped up on users@infra (needs sign in) > > about Apache Airflow's switch a couple of years back. Found it very > > interesting - food for thought? > > > > > > https://lists.apache.org/thread.html/r65aae462b9f26454adaf9e5854dda06b > > 2acd10273cb1b34b3e6b1227%40%3Cusers.infra.apache.org%3E > > > > Best wishes, > > > > Neil > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > > For additional commands, e-mail: dev-h...@netbeans.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > >
AW: Apache JIRA vs GitHub issues / discussions
I see a big Benefit out of it also to have everything in one application (Pipeline, Discussions, Issues, etc.). As the other one, on the other mailinglist already mentioned: That was such an amazing improvement in the overall workflow and contributor's engagement Cheers Chris Von: Eric Barboni Gesendet: Freitag, 24. September 2021 13:29 An: dev@netbeans.apache.org Betreff: RE: Apache JIRA vs GitHub issues / discussions I don't know. Would be happy with both. I suspect, we will still have lots of opened untackled issue on git issue too. Would be good to hear from major our major contributor. Best Regards Eric -Message d'origine- De : John Mc Envoyé : jeudi 23 septembre 2021 22:42 À : dev Objet : Re: Apache JIRA vs GitHub issues / discussions Interesting point, JIRA seems very decoupled from everything else at the moment. We have a lot of open tickets there ~3000 and we're not doing a great job keeping an eye on it. it might allow people to raise bugs more freely as more users would have GH accounts then Apache JIRA accounts so it make it easier for users to submit bugs.. Regards John On Thu, 23 Sept 2021 at 15:43, Neil C Smith wrote: > Hi, > > I've long felt that our use of JIRA and poor integration with the PR > process, etc. is more of a hindrance than a help, particularly during > releases. This email just popped up on users@infra (needs sign in) > about Apache Airflow's switch a couple of years back. Found it very > interesting - food for thought? > > > https://lists.apache.org/thread.html/r65aae462b9f26454adaf9e5854dda06b > 2acd10273cb1b34b3e6b1227%40%3Cusers.infra.apache.org%3E > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Apache JIRA vs GitHub issues / discussions
I don't know. Would be happy with both. I suspect, we will still have lots of opened untackled issue on git issue too. Would be good to hear from major our major contributor. Best Regards Eric -Message d'origine- De : John Mc Envoyé : jeudi 23 septembre 2021 22:42 À : dev Objet : Re: Apache JIRA vs GitHub issues / discussions Interesting point, JIRA seems very decoupled from everything else at the moment. We have a lot of open tickets there ~3000 and we're not doing a great job keeping an eye on it. it might allow people to raise bugs more freely as more users would have GH accounts then Apache JIRA accounts so it make it easier for users to submit bugs.. Regards John On Thu, 23 Sept 2021 at 15:43, Neil C Smith wrote: > Hi, > > I've long felt that our use of JIRA and poor integration with the PR > process, etc. is more of a hindrance than a help, particularly during > releases. This email just popped up on users@infra (needs sign in) > about Apache Airflow's switch a couple of years back. Found it very > interesting - food for thought? > > > https://lists.apache.org/thread.html/r65aae462b9f26454adaf9e5854dda06b > 2acd10273cb1b34b3e6b1227%40%3Cusers.infra.apache.org%3E > > Best wishes, > > Neil > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org > For additional commands, e-mail: dev-h...@netbeans.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Release Team for 12.6?
Up :D -Message d'origine- De : Geertjan Wielenga Envoyé : vendredi 24 septembre 2021 10:39 À : dev Objet : Release Team for 12.6? Hi all, Who'd like to volunteer to join Neil and me on the release team for 12.6? What you'll be doing -- verifying issues, trying out builds, giving feedback, being the go-to people around the time of the release, coming up in the next month or two, help identify the important bugs to be fixed, etc. Not all of these will be done by anyone, just a few of these, those that you're most comfortable with and can fit into your schedule. Especially if you tend to find problems with NetBeans right after a release, this is your opportunity to find them in a time period when they can be fixed. Please speak up and volunteer by replying to this invitation! Gj - To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Release Team for 12.6?
Hi all, Who'd like to volunteer to join Neil and me on the release team for 12.6? What you'll be doing -- verifying issues, trying out builds, giving feedback, being the go-to people around the time of the release, coming up in the next month or two, help identify the important bugs to be fixed, etc. Not all of these will be done by anyone, just a few of these, those that you're most comfortable with and can fit into your schedule. Especially if you tend to find problems with NetBeans right after a release, this is your opportunity to find them in a time period when they can be fixed. Please speak up and volunteer by replying to this invitation! Gj
