[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 --- Comment #8 from Matthias --- Sure, thanks a lot for the quick fix. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 --- Comment #7 from Kevin Funk --- Updated the website title, front page heading and Features page. Hope that helps. Thanks for the hints! -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 --- Comment #6 from Sven Brauch --- QML can be mentioned but not Go, it has no released stable version yet. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 --- Comment #5 from Matthias --- "Plugins are "part of KDevelop", IMO. When reporting bugs the user will think of reporting the bug against the 'kdevelop' product first -- which part it happened in is secondary." I agree with you about this one. This is also the reason, why i think that KDevelop should stop to hide its features and mention Go and QML support also on this page: https://www.kdevelop.org/ I can open another report for it -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 Kevin Funk changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Kevin Funk --- I've added a "Language Support: Go" component to the kdevelop product. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 Kevin Funk changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Kevin Funk --- Adding them as components is the way to go. I'd love to have kdev-python in their as component there (for consistency reasons), but I think I once talked to Sven about it and he didn't like the idea. My reasons *for* adding plugins as components: - Scales much better (we don't have to maintain one product per plugin, and we also don't need to keep the versions/milestones in sync) - Plugins are "part of KDevelop", IMO. When reporting bugs the user will think of reporting the bug against the 'kdevelop' product first -- which part it happened in is secondary. -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 Friedrich W. H. Kossebau changed: What|Removed |Added CC||emati...@gmail.com, ||m...@svenbrauch.de --- Comment #2 from Friedrich W. H. Kossebau --- Question is if "kdev-go" should become a component "Language Support: Go" below kdevelop: https://bugs.kde.org/describecomponents.cgi?product=kdevelop or be a complete own products, with own components, like kdev-python: https://bugs.kde.org/describecomponents.cgi?product=kdev-python -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 382147] add kdev-go
https://bugs.kde.org/show_bug.cgi?id=382147 Ben Cooksley changed: What|Removed |Added CC||bcooks...@kde.org, ||kf...@kde.org, ||kosse...@kde.org --- Comment #1 from Ben Cooksley --- Adding KDevelop developers for their comments on this. -- You are receiving this mail because: You are watching all bug changes.