Replies: 1 comment 1 reply
-
What would be improved by that proposal? Who will run the development & sync with platform releases? Some new contributors or the same people who do not have time to work on SWT already? Why not wait for a constant stream of patches for SWT that would require independent development cycles, and once we see the need we can discuss whether moving to a different organisation would improve the process? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
SWT is currently part of eclipse-platform but:
Therefore SWT is more an own framework/library and could benefit from independent development cycles and seems perfectly suited to be an own project. This does not mean platform can't build/use against "latest" SWT ... it just would mean SWT can be released / developed independently.
I therefore like to suggest to split SWT from eclipse-platform, a first step could be to simply move the repository to its own organization (thanks to github redirection this would be quite transparent to users).
Beta Was this translation helpful? Give feedback.
All reactions