As part of the "API is forever" philosophy, SWT committers spend a lot of time exploring naming, package visibility and the way an API works, a long time after the code works. There is always tension between the smallest number of classes, methods and constants needed to get the job done, consistency with similar concepts in the toolkit and the future. The future is important because "API grows like fungus", however twisting today's API for a future that may never come makes today's API cumbersome and hard to maintain. So, before an API makes it out, we've considered the likely futures and have concrete ideas about what we will do should they arise. As you can imagine, all this discussion is very stressful.
I love the fact that the Germans have a word for something I feel every once in a while.