[GitHub] [plc4x] dependabot[bot] opened a new pull request, #651: build(deps): bump golang.org/x/tools from 0.2.0 to 0.3.0 in /plc4go
dependabot[bot] opened a new pull request, #651: URL: https://github.com/apache/plc4x/pull/651 Bumps [golang.org/x/tools](https://github.com/golang/tools) from 0.2.0 to 0.3.0. Release notes Sourced from https://github.com/golang/tools/releases;>golang.org/x/tools's releases. gopls/v0.3.0 Note: gopls now loads your entire workspace, where “workspace” is directory you opened in your editor. In module mode, you must open your module root (directory containing the go.mod file) or a subdirectory. In GOPATH mode, you must open your GOPATH/src or a directory within it. If you have a large GOPATH and you open your GOPATH as your workspace root, gopls may be very slow to load. Please see https://github-redirect.dependabot.com/golang/tools/issues/36899;>#36899 for further information. Autocompletion from unimported packages is on by default. You will get completions for something like fmt.Printf even if “fmt” isn’t imported yet. (https://github.com/heschik;>@heschik) Workspace-scoped references, rename, and go to implementation. These features use your workspace root as the search scope, so behavior will vary based on the directory you open in your editor. This may result in unexpected behavior. (https://github.com/muirdm;>@muirdm, https://github.com/matloob;>@matloob) Workspace-wide diagnostics. You will now see errors in your entire workspace, rather than just in your currently open files. Analysis errors will only be shown for packages with currently open files. Watch file changes on disk. This allows users to switch branches without reloading their editors. Also, changing configurations no longer requires an editor reload. GOPATH vendoring is fully supported. Previously, some features would ignore vendor directories, causing errors if packages weren't in GOPATH. (https://github.com/heschik;>@heschik) New autocompletion suggestions for type conversions. Improved completions for literal candidates and variadic functions. Better rankings, including rankings for builtin functions and keywords. (https://github.com/muirdm;>@muirdm) Highlighting improvements: Highlighting now applies not only to variables, but also to fields, methods, types, and imports. Additional highlighting helps visualize control flow in loops and functions. Highlighting of single character variables has better support. (https://github.com/ridersofrohan;>@ridersofrohan) Documentation on hover includes links to https://pkg.go.dev;>pkg.go.dev for exported symbols. (https://github.com/Southclaws;>@Southclaws) Improved support for cgo dependencies. All features now work for packages that have cgo dependencies. Authoring cgo packages is still not supported, but improvements are scheduled for Go 1.15 (see https://github-redirect.dependabot.com/golang/tools/issues/35721;>#35721). (https://github.com/heschik;>@heschik) Deep completions are now on by default. This feature of completion will search the fields and methods of all available candidates to see if there are any more candidates with the expected type. As an example, say you have imported the context package and are calling a function that takes a context.Context as a parameter. In the case that you don’t have a variable of that type in scope, deep completions will suggest context.Background() and context.TODO(). (https://github.com/muirdm;>@muirdm) Opt-in: staticcheck analyses remain opt-in and can be enabled by setting staticcheck: true in your gopls settings. Go 1.14 will support running the go command without modifying the user’s go.mod file. This new feature is used in gopls to show diagnostics and suggest edits in a user’s go.mod file rather than change the file without the user noticing. Currently, gopls will suggest removing unused dependencies and warn the user if there is a parse error in the go.mod file. Enable this behavior by using the go1.14 beta and setting tempModfile: true in your gopls settings. (https://github.com/ridersofrohan;>@ridersofrohan) gopls/v0.2.2 Fix concurrent map read and write when a file is created (https://go-review.googlesource.com/c/tools/+/210199;>CL 210199). Fix issue that caused errors to show up when a new file was created (https://go-review.googlesource.com/c/tools/+/209978;>CL 209978). gopls/v0.2.1 Fix for parse errors showing up as errors on the whole package (https://go-review.googlesource.com/c/tools/+/206597;>CL 206597). Commits https://github.com/golang/tools/commit/502c634771c4ba335286d55fc24eeded1704f592;>502c634 go.mod: update golang.org/x dependencies https://github.com/golang/tools/commit/bd04e329aedbea5310658e5d1afbfba4ce700178;>bd04e32 internal/jsonrpc2_v2: eliminate a potential Accept/Dial race in TestIdleTimeout https://github.com/golang/tools/commit/d41a43b94f2f49adda95493f62c78f57ba91eeec;>d41a43b internal/jsonrpc2_v2: fix a potential
[GitHub] [plc4x] dependabot[bot] opened a new pull request, #650: build(deps): bump netty-bom from 4.1.84.Final to 4.1.85.Final
dependabot[bot] opened a new pull request, #650: URL: https://github.com/apache/plc4x/pull/650 Bumps [netty-bom](https://github.com/netty/netty) from 4.1.84.Final to 4.1.85.Final. Commits https://github.com/netty/netty/commit/8a5b08dad5855c5ab202e9c51710b48509cc56fe;>8a5b08d [maven-release-plugin] prepare release netty-4.1.85.Final https://github.com/netty/netty/commit/75aac7c87d82fbc80b66e99ad5c8273e43aa56cd;>75aac7c WebSocket frame encoding: avoid redundant allocations on frame masking (https://github-redirect.dependabot.com/netty/netty/issues/12969;>#12969) https://github.com/netty/netty/commit/7127e6074c2f4b965305738d7756d196729b493e;>7127e60 Move validation of connection headers in HTTP/2 back to HpackDecoder (https://github-redirect.dependabot.com/netty/netty/issues/12975;>#12975) https://github.com/netty/netty/commit/ecf489fb75d25d0fd35992d53f2e9bc6d9861e47;>ecf489f Subclasses of FastThreadLocalThread can selectively permit blocking calls (https://github-redirect.dependabot.com/netty/netty/issues/1;>#1... https://github.com/netty/netty/commit/a4c37bc06d16ba2267a3f8cac151f29bd9118aad;>a4c37bc Close EmbeddedChannel and release all buffers once test completes (https://github-redirect.dependabot.com/netty/netty/issues/12962;>#12962) https://github.com/netty/netty/commit/a0bb7b4c7831d2a855206f9dc45367675ac60a7c;>a0bb7b4 fix typos in requireNonNull function (https://github-redirect.dependabot.com/netty/netty/issues/12961;>#12961) https://github.com/netty/netty/commit/de8a7efd054d1eedc833303b1c2c8c76e519d5e1;>de8a7ef Implement Early hints response status, do not poll the encoding with HTTP 1xx... https://github.com/netty/netty/commit/e1437fb468c5647f7f02fcd49b405af1259d8716;>e1437fb Avoid ignoring interrupts in testsuite (https://github-redirect.dependabot.com/netty/netty/issues/12958;>#12958) https://github.com/netty/netty/commit/cfcc5144578d3f998d353cc3c3b448fc56333e0d;>cfcc514 Avoid ignoring interrupts in SocketStartTlsTest and SocketSslEchoTest (https://github-redirect.dependabot.com/netty/netty/issues/12946;>#12946) https://github.com/netty/netty/commit/fe0b5ce16c4508387f999e530a85f2d968e90a3c;>fe0b5ce Use the recommended directory layout for native-image metadata. Simplify auto... Additional commits viewable in https://github.com/netty/netty/compare/netty-4.1.84.Final...netty-4.1.85.Final;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [DISCUSS] Rename Fields -> Tags?
Hi All, thanks for that. And just an update … I’m already working hard on this on my refactoring banch. Reason was, that I only wanted to break SNAPSHOT once for anyone that might be relying on it. Chris From: Xiangdong Huang Date: Wednesday, 9. November 2022 at 05:11 To: dev@plc4x.apache.org Subject: Re: [DISCUSS] Rename Fields -> Tags? +1 for Tag. Just want to share that I researched many historian systems (include OSIsoft PI, Siemens WinCC, Emerson DeltaV, etc.), all of them are using "Tag". --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Otto Fowler 于2022年11月9日周三 11:41写道： > > +1 > > From: Ben Hutcheson > Reply: dev@plc4x.apache.org > Date: November 8, 2022 at 15:20:51 > To: dev@plc4x.apache.org > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > +1, while I don't have your commitment to go around and change it. I think > it makes it better aligned with OT nomenclature. > > On Tue, Nov 8, 2022 at 2:21 AM Christofer Dutz > wrote: > > > Hmmm … ok, > > > > So, I count two people for using Tag and sort of Two for using Field. > > Am I correct with this? > > > > At least my LinkedIn question seems to be clear that most people would be > > expecting “Tag”. > > And I mean … I think we don’t need to work on having PLC4X accepted on > the > > IT side, but on the OT side. > > Making it more aligned with what the OT folks expect seems to be a better > > path for me. > > > > But I would really appreciate a bit more clear outcome of this > discussion… > > so anyone who’s not posted his opinion yet is highly encouraged to do so. > > > > I’d just hate to rename something like that after a 1.0.0. > > > > Chris > > > > > > > > From: jl hong > > Date: Tuesday, 8. November 2022 at 02:56 > > To: dev@plc4x.apache.org > > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > Hello Chris, > > I had the same confusion with Łukasz about what "Tag" meant when I first > > met it in using Rockwell > > PLCs.Maybe it is more difficult to understand than "Field".Also, I think > > "Field" is not accurate enough too. > > Finally, I think either "Tag" or "Field" is acceptable, and people should > > both be able to understand it from the document or context. > > By the way, we call it "Point Position" in Chinese, I translated > directly. > > > > Christofer Dutz 於 2022年11月8日 週二 凌晨4:49寫道： > > > > > Probably should rename „fieldQuery“ to „fieldAddress” (or tagAddress) > as > > I > > > split Fields and Queries as a query usually targets more than one > element > > > and an address normaly doesn’t. > > > > > > Chris > > > > > > From: Christofer Dutz > > > Date: Monday, 7. November 2022 at 21:40 > > > To: dev@plc4x.apache.org > > > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > > And regarding your points, Lukasz, > > > > > > The output from the Browse API is that it is a BrowseItem. This > contains > > a > > > Field (or Tag if we rename it) and loads of metadata. > > > Is the Field readable, writable, subscribable, loads of protocol > > dependent > > > options. > > > > > > The Field itself now should be able to produce an address string that > > > should be able to re-produce it. The APIs all support “addFieldQuery” > > which > > > takes this string representation or “addField” which directly receives > > the > > > field object. > > > > > > Chris > > > > > > > > > From: Łukasz Dywicki > > > Date: Monday, 7. November 2022 at 13:48 > > > To: dev@plc4x.apache.org > > > Subject: Re: [DISCUSS] Rename Fields -> Tags? > > > Hey Chris, > > > I do not insist on any side. Knowing how hard it is to get a "common > > > understanding" on certain things I think it is easier if we stick with > > > project specific concept. > > > > > > Other point, we do not need to re-use a PlcField and field notion > > > everywhere. For example output from browse api might be a descriptor > > > which can be used to construct a field address. After all, a browsing > > > functionality might provide more information than needed to fetch data > - > > > ie. human readable name, description or other elements which are > > > irrelevant for driver to get data. > > > > > > As a side note, I do acknowledge that best time to do naming and larger > > > API alignments is prior 1.x release. > > > > > > Best, > > > Łukasz > > > > > > On 6.11.2022 13:32, Christofer Dutz wrote: > > > > Hi Lukasz, > > > > > > > > even in protocols like ADS and EIP at Rivian everyone is referring to > > > any data point as a “Tag”. > > > > So far, I haven’t come across a single person saying something else > on > > > LinkedIn. > > > > > > https://www.linkedin.com/feed/update/urn:li:activity:6994584721582088192 > > > > > > > > And keep in mind: PLC4X is meant to be the bridge between IT and OT, > > and > > > we chose a lot of stuff (Like the address patterns, etc.) to match the > OT > > > expectations. After all, I will most probably be an IT person asking > the > > OT > > > person: Please give me the address for Field/Tag
Re: [DISCUSS] Enable GitHub issues?
Hi Dominik, It was straight foward and easy to use. :-) KR Lukas Am Mi., 9. Nov. 2022 um 11:36 Uhr schrieb Dominik Riemer : > Hi Lukas, > > great work! > Just out of interest, how was your experience when using the migration > tool? Are there any pitfalls/things one should be aware of when configuring > the migration? > > Cheers > Dominik > > -Original Message- > From: Lukas Ott > Sent: Wednesday, November 9, 2022 11:33 AM > To: dev@plc4x.apache.org > Subject: Re: [DISCUSS] Enable GitHub issues? > > successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately > it seems i do not have the rights to close down our JIRA: > "This can be done by turning off the create issue permission for all > non-admins and adding an announcement in Portal Settings redirecting people > to GitHub." > > Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott : > > > Updated: > > - Driver-Profinet -> Profinet > > - Driver-ADS -> ADS > > - API -> API > > - Driver-S7 -> S7 > > - Core -> ??? > > - Util-Pool -> ??? > > - newbie -> good first issue > > - Code-Generation > > - Driver-Modbus -> Modbus > > - Integration-NiFi > > - feature-request -> new feature > > - Driver-OPC-UA -> OPC-UA > > - documentation -> documentation > > - Scraper -> ??? > > - Driver-Fatek -> Fatek > > - Testing -> test > > - Integration-Camel -> we have donated this to Apache Camel > > - Driver-Ethernet/IP -> Ethernet/IP > > - beginnerv -> good first issue > > - feature -> new feature > > - low-hanging-fruit -> good first issue > > - easy-fix -> good first issue > > - PLC4C -> c > > - documentation-update -> documentation > > - docker -> ??? > > - Integration-Kafka-Connect > > - examples -> ?? > > - Build -> release > > - Driver-CANopen -> CANopen > > - PLC4J - > java > > > > On 2022/11/04 09:55:44 jl hong wrote: > > > Hello Lukas, > > > > > >- Driver-Profinet > > >- Driver-ADS > > >- API > > >- Driver-S7 > > >- Core > > >- Util-Pool > > >- newbie > > >- Code-Generation > > >- Driver-Modbus > > >- Integration-NiFi > > >- feature-request > > >- Driver-OPC-UA > > >- documentation > > >- Scraper > > >- Driver-Fatek > > >- Testing > > >- Integration-Camel > > >- Driver-Ethernet/IP > > >- beginner > > >- feature > > >- low-hanging-fruit > > >- easy-fix > > >- PLC4C > > >- documentation-update > > >- docker > > >- Integration-Kafka-Connect > > >- examples > > >- Build > > >- Driver-CANopen > > >- PLC4J > > > > > > The list which I got by jira-to-issues is current labels in our Jira. > > > Some of them are not on your list, such as "driver". > > > > > > Lukas Ott 於 2022年11月1日 週二 凌晨3:25寫道： > > > > > > > I started cleaning up the Issues on JIRA. > > > > Current status is 84 Issues. > > > > > > > > On Github I added a few labels. > > > > Current list of labels (17): > > > > > > > >- test > > > >- task > > > >- wish > > > >- new feature > > > >- bug > > > >- dependencies > > > >- duplicate > > > >- enhancement > > > >- go > > > >- good first issue > > > >- help wanted > > > >- invalid > > > >- java > > > >- python > > > >- question > > > >- wontfix > > > >- github_actions > > > > > > > > Open tasks: > > > > - Turn off new Jiras > > > > This can be done by turning off the create issue permission for > > > > all non-admins and adding an announcement in Portal Settings > > > > redirecting > > people > > > > to GitHub. > > > > - Migrating Existing Issues > > > > - Create / Add Issue Template > > > > > > > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson < > > > > ben.hut...@gmail.com>: > > > > > > > > > +1 > > > > > > > > > > This will make the issues more visible, which is probably a good > > thing. > > > > > > > > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott > > > > > > > > > wrote: > > > > > > > > > > > Thank you Dominik! This > > > > > > > > > > > > It seems we have less of the Cons they are mentioning :-) > > > > > > -> Google Summer of Code was not yet part of PLC4X We only > > > > > > -> need to migrate around 100 Jira issues I am not aware of > > > > > > -> any Milestones in our project that we track in > > > > Jira. > > > > > > > > > > > > Concerning preparation: > > > > > > - We already have list of labels List to be added: > > > > > > > > > > > > Category > > > > > > > > > > > > Values > > > > > > > > > > > > Priority > > > > > > > > > > > > "P0", "P1", "P2", "P3" > > > > > > > > > > > > Type > > > > > > > > > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", > > "Outage" > > > > > > > > > > > > Component > > > > > > > > > > > > One label per JIRA component, formatted "Component: > component>" > > > > > (e.g. > > > > > > "Component: sdk-go") > > > > > > > > > > > > Status > > > > > > > > > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate" > > > > > > > > > > > > > > > > > > - Yes we should add a issue template
RE: [DISCUSS] Enable GitHub issues?
Hi Lukas, great work! Just out of interest, how was your experience when using the migration tool? Are there any pitfalls/things one should be aware of when configuring the migration? Cheers Dominik -Original Message- From: Lukas Ott Sent: Wednesday, November 9, 2022 11:33 AM To: dev@plc4x.apache.org Subject: Re: [DISCUSS] Enable GitHub issues? successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately it seems i do not have the rights to close down our JIRA: "This can be done by turning off the create issue permission for all non-admins and adding an announcement in Portal Settings redirecting people to GitHub." Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott : > Updated: > - Driver-Profinet -> Profinet > - Driver-ADS -> ADS > - API -> API > - Driver-S7 -> S7 > - Core -> ??? > - Util-Pool -> ??? > - newbie -> good first issue > - Code-Generation > - Driver-Modbus -> Modbus > - Integration-NiFi > - feature-request -> new feature > - Driver-OPC-UA -> OPC-UA > - documentation -> documentation > - Scraper -> ??? > - Driver-Fatek -> Fatek > - Testing -> test > - Integration-Camel -> we have donated this to Apache Camel > - Driver-Ethernet/IP -> Ethernet/IP > - beginnerv -> good first issue > - feature -> new feature > - low-hanging-fruit -> good first issue > - easy-fix -> good first issue > - PLC4C -> c > - documentation-update -> documentation > - docker -> ??? > - Integration-Kafka-Connect > - examples -> ?? > - Build -> release > - Driver-CANopen -> CANopen > - PLC4J - > java > > On 2022/11/04 09:55:44 jl hong wrote: > > Hello Lukas, > > > >- Driver-Profinet > >- Driver-ADS > >- API > >- Driver-S7 > >- Core > >- Util-Pool > >- newbie > >- Code-Generation > >- Driver-Modbus > >- Integration-NiFi > >- feature-request > >- Driver-OPC-UA > >- documentation > >- Scraper > >- Driver-Fatek > >- Testing > >- Integration-Camel > >- Driver-Ethernet/IP > >- beginner > >- feature > >- low-hanging-fruit > >- easy-fix > >- PLC4C > >- documentation-update > >- docker > >- Integration-Kafka-Connect > >- examples > >- Build > >- Driver-CANopen > >- PLC4J > > > > The list which I got by jira-to-issues is current labels in our Jira. > > Some of them are not on your list, such as "driver". > > > > Lukas Ott 於 2022年11月1日 週二 凌晨3:25寫道： > > > > > I started cleaning up the Issues on JIRA. > > > Current status is 84 Issues. > > > > > > On Github I added a few labels. > > > Current list of labels (17): > > > > > >- test > > >- task > > >- wish > > >- new feature > > >- bug > > >- dependencies > > >- duplicate > > >- enhancement > > >- go > > >- good first issue > > >- help wanted > > >- invalid > > >- java > > >- python > > >- question > > >- wontfix > > >- github_actions > > > > > > Open tasks: > > > - Turn off new Jiras > > > This can be done by turning off the create issue permission for > > > all non-admins and adding an announcement in Portal Settings > > > redirecting > people > > > to GitHub. > > > - Migrating Existing Issues > > > - Create / Add Issue Template > > > > > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson < > > > ben.hut...@gmail.com>: > > > > > > > +1 > > > > > > > > This will make the issues more visible, which is probably a good > thing. > > > > > > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott > > > > > > > wrote: > > > > > > > > > Thank you Dominik! This > > > > > > > > > > It seems we have less of the Cons they are mentioning :-) > > > > > -> Google Summer of Code was not yet part of PLC4X We only > > > > > -> need to migrate around 100 Jira issues I am not aware of > > > > > -> any Milestones in our project that we track in > > > Jira. > > > > > > > > > > Concerning preparation: > > > > > - We already have list of labels List to be added: > > > > > > > > > > Category > > > > > > > > > > Values > > > > > > > > > > Priority > > > > > > > > > > "P0", "P1", "P2", "P3" > > > > > > > > > > Type > > > > > > > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", > "Outage" > > > > > > > > > > Component > > > > > > > > > > One label per JIRA component, formatted "Component: component>" > > > > (e.g. > > > > > "Component: sdk-go") > > > > > > > > > > Status > > > > > > > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate" > > > > > > > > > > > > > > > - Yes we should add a issue template This can be done by > > > > > turning off the create issue permission for all non-admins and > > > > > adding an announcement in Portal Settings > redirecting > > > > people > > > > > to GitHub. > > > > > - Update documentation after migration > > > > > > > > > > Next steps > > > > > - Turn on Github Issues Tab > > > > > - Turn off Jira Tickets (How do we do that?) > > > > > > > > > > > > > > > > > > > > > > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb
Re: [DISCUSS] Enable GitHub issues?
successfully migrated all 70 Jira Issues to Github Issues -> Unfortunately it seems i do not have the rights to close down our JIRA: "This can be done by turning off the create issue permission for all non-admins and adding an announcement in Portal Settings redirecting people to GitHub." Am Mi., 9. Nov. 2022 um 10:25 Uhr schrieb Lukas Ott : > Updated: > - Driver-Profinet -> Profinet > - Driver-ADS -> ADS > - API -> API > - Driver-S7 -> S7 > - Core -> ??? > - Util-Pool -> ??? > - newbie -> good first issue > - Code-Generation > - Driver-Modbus -> Modbus > - Integration-NiFi > - feature-request -> new feature > - Driver-OPC-UA -> OPC-UA > - documentation -> documentation > - Scraper -> ??? > - Driver-Fatek -> Fatek > - Testing -> test > - Integration-Camel -> we have donated this to Apache Camel > - Driver-Ethernet/IP -> Ethernet/IP > - beginnerv -> good first issue > - feature -> new feature > - low-hanging-fruit -> good first issue > - easy-fix -> good first issue > - PLC4C -> c > - documentation-update -> documentation > - docker -> ??? > - Integration-Kafka-Connect > - examples -> ?? > - Build -> release > - Driver-CANopen -> CANopen > - PLC4J - > java > > On 2022/11/04 09:55:44 jl hong wrote: > > Hello Lukas, > > > >- Driver-Profinet > >- Driver-ADS > >- API > >- Driver-S7 > >- Core > >- Util-Pool > >- newbie > >- Code-Generation > >- Driver-Modbus > >- Integration-NiFi > >- feature-request > >- Driver-OPC-UA > >- documentation > >- Scraper > >- Driver-Fatek > >- Testing > >- Integration-Camel > >- Driver-Ethernet/IP > >- beginner > >- feature > >- low-hanging-fruit > >- easy-fix > >- PLC4C > >- documentation-update > >- docker > >- Integration-Kafka-Connect > >- examples > >- Build > >- Driver-CANopen > >- PLC4J > > > > The list which I got by jira-to-issues is current labels in our Jira. > > Some of them are not on your list, such as "driver". > > > > Lukas Ott 於 2022年11月1日 週二 凌晨3:25寫道： > > > > > I started cleaning up the Issues on JIRA. > > > Current status is 84 Issues. > > > > > > On Github I added a few labels. > > > Current list of labels (17): > > > > > >- test > > >- task > > >- wish > > >- new feature > > >- bug > > >- dependencies > > >- duplicate > > >- enhancement > > >- go > > >- good first issue > > >- help wanted > > >- invalid > > >- java > > >- python > > >- question > > >- wontfix > > >- github_actions > > > > > > Open tasks: > > > - Turn off new Jiras > > > This can be done by turning off the create issue permission for all > > > non-admins and adding an announcement in Portal Settings redirecting > people > > > to GitHub. > > > - Migrating Existing Issues > > > - Create / Add Issue Template > > > > > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson < > > > ben.hut...@gmail.com>: > > > > > > > +1 > > > > > > > > This will make the issues more visible, which is probably a good > thing. > > > > > > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott > > > wrote: > > > > > > > > > Thank you Dominik! This > > > > > > > > > > It seems we have less of the Cons they are mentioning :-) > > > > > -> Google Summer of Code was not yet part of PLC4X > > > > > -> We only need to migrate around 100 Jira issues > > > > > -> I am not aware of any Milestones in our project that we track in > > > Jira. > > > > > > > > > > Concerning preparation: > > > > > - We already have list of labels > > > > > List to be added: > > > > > > > > > > Category > > > > > > > > > > Values > > > > > > > > > > Priority > > > > > > > > > > "P0", "P1", "P2", "P3" > > > > > > > > > > Type > > > > > > > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", > "Outage" > > > > > > > > > > Component > > > > > > > > > > One label per JIRA component, formatted "Component: component>" > > > > (e.g. > > > > > "Component: sdk-go") > > > > > > > > > > Status > > > > > > > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate" > > > > > > > > > > > > > > > - Yes we should add a issue template > > > > > This can be done by turning off the create issue permission for all > > > > > non-admins and adding an announcement in Portal Settings > redirecting > > > > people > > > > > to GitHub. > > > > > - Update documentation after migration > > > > > > > > > > Next steps > > > > > - Turn on Github Issues Tab > > > > > - Turn off Jira Tickets (How do we do that?) > > > > > > > > > > > > > > > > > > > > > > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer < > > > rie...@fzi.de > > > > >: > > > > > > > > > > > I've recently looked at other ASF projects which discussed > migration > > > > from > > > > > > Jira to Github, e.g., here are some discussions from Apache Beam: > > > > > > > > > > > > Feature Comparison: > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Enable GitHub issues?
Updated: - Driver-Profinet -> Profinet - Driver-ADS -> ADS - API -> API - Driver-S7 -> S7 - Core -> ??? - Util-Pool -> ??? - newbie -> good first issue - Code-Generation - Driver-Modbus -> Modbus - Integration-NiFi - feature-request -> new feature - Driver-OPC-UA -> OPC-UA - documentation -> documentation - Scraper -> ??? - Driver-Fatek -> Fatek - Testing -> test - Integration-Camel -> we have donated this to Apache Camel - Driver-Ethernet/IP -> Ethernet/IP - beginnerv -> good first issue - feature -> new feature - low-hanging-fruit -> good first issue - easy-fix -> good first issue - PLC4C -> c - documentation-update -> documentation - docker -> ??? - Integration-Kafka-Connect - examples -> ?? - Build -> release - Driver-CANopen -> CANopen - PLC4J - > java On 2022/11/04 09:55:44 jl hong wrote: > Hello Lukas, > >- Driver-Profinet >- Driver-ADS >- API >- Driver-S7 >- Core >- Util-Pool >- newbie >- Code-Generation >- Driver-Modbus >- Integration-NiFi >- feature-request >- Driver-OPC-UA >- documentation >- Scraper >- Driver-Fatek >- Testing >- Integration-Camel >- Driver-Ethernet/IP >- beginner >- feature >- low-hanging-fruit >- easy-fix >- PLC4C >- documentation-update >- docker >- Integration-Kafka-Connect >- examples >- Build >- Driver-CANopen >- PLC4J > > The list which I got by jira-to-issues is current labels in our Jira. > Some of them are not on your list, such as "driver". > > Lukas Ott 於 2022年11月1日 週二 凌晨3:25寫道： > > > I started cleaning up the Issues on JIRA. > > Current status is 84 Issues. > > > > On Github I added a few labels. > > Current list of labels (17): > > > >- test > >- task > >- wish > >- new feature > >- bug > >- dependencies > >- duplicate > >- enhancement > >- go > >- good first issue > >- help wanted > >- invalid > >- java > >- python > >- question > >- wontfix > >- github_actions > > > > Open tasks: > > - Turn off new Jiras > > This can be done by turning off the create issue permission for all > > non-admins and adding an announcement in Portal Settings redirecting people > > to GitHub. > > - Migrating Existing Issues > > - Create / Add Issue Template > > > > Am Mo., 31. Okt. 2022 um 19:26 Uhr schrieb Ben Hutcheson < > > ben.hut...@gmail.com>: > > > > > +1 > > > > > > This will make the issues more visible, which is probably a good thing. > > > > > > On Mon, 31 Oct 2022 at 12:06 pm, Lukas Ott > > wrote: > > > > > > > Thank you Dominik! This > > > > > > > > It seems we have less of the Cons they are mentioning :-) > > > > -> Google Summer of Code was not yet part of PLC4X > > > > -> We only need to migrate around 100 Jira issues > > > > -> I am not aware of any Milestones in our project that we track in > > Jira. > > > > > > > > Concerning preparation: > > > > - We already have list of labels > > > > List to be added: > > > > > > > > Category > > > > > > > > Values > > > > > > > > Priority > > > > > > > > "P0", "P1", "P2", "P3" > > > > > > > > Type > > > > > > > > "Bug", "Improvement", "New Feature", "Task", "Test", "Wish", "Outage" > > > > > > > > Component > > > > > > > > One label per JIRA component, formatted "Component: " > > > (e.g. > > > > "Component: sdk-go") > > > > > > > > Status > > > > > > > > "Awaiting Triage", "Fixed", "Not a problem", "Duplicate" > > > > > > > > > > > > - Yes we should add a issue template > > > > This can be done by turning off the create issue permission for all > > > > non-admins and adding an announcement in Portal Settings redirecting > > > people > > > > to GitHub. > > > > - Update documentation after migration > > > > > > > > Next steps > > > > - Turn on Github Issues Tab > > > > - Turn off Jira Tickets (How do we do that?) > > > > > > > > > > > > > > > > > > > > Am Mo., 31. Okt. 2022 um 18:48 Uhr schrieb Dominik Riemer < > > rie...@fzi.de > > > >: > > > > > > > > > I've recently looked at other ASF projects which discussed migration > > > from > > > > > Jira to Github, e.g., here are some discussions from Apache Beam: > > > > > > > > > > Feature Comparison: > > > > > > > > > > > > > > https://docs.google.com/document/d/1_n7gboVbSKPs-CVcHzADgg8qpNL9igiHqUPCmiOslf0/edit#heading=h.r8qwrrbs8odn > > > > > Migration Plan: > > > > > > > > > > > > > > https://docs.google.com/document/d/1powrXGbjMLMYl9ibRzMda5o5HM_p44XvBy5MZu75Q5E/edit#heading=h.wskna8eurvjv > > > > > > > > > > And Beam also open-sourced the migration tool they used: > > > > > https://github.com/google/jira-to-issues > > > > > > > > > > I've not yet tried it, but looks quite good > > > > > > > > > > Cheers > > > > > Dominik > > > > > > > > > > > > > > > -Original Message- > > > > > From: Lukas Ott > > > > > Sent: Monday, October 31, 2022 6:41 PM > > > > > To: dev@plc4x.apache.org > > > > > Subject: Re: [DISCUSS] Enable GitHub issues? > > > > > > > > > > I will look into that. > > >
