Hi Chris, Peter , Some comments on the release/packaging topics :
* Update site : I also think this would really help developpers to start using nebula widgets. Users often expect CVS code to be 'dev/trunk' quality so they rather use zip files and get all the update problems that Peter told us. The only drawback I see with an update site is version management. As we're not releasing official versions and thus not incrementing version numbers when changes are done, we would have to use qualifiers to ensure updates are detected. If the update site is build daily, users will receive update notifications everyday... We could start real version numbering as Peter suggests or build this site weekly/monthly, ... * Next moon-of-Jupiter release : as most nebula widgets are used in some real applications, the current alpha/beta status mainly reflects the "no garantees for api changes". I believe that we could go to a 1.0 release even if some SWT API are not fully implemented yet and if some non-critical bugs exists, as long as the current API is OK and will not change. Some months ago, there were plans to have a widget code review by SWT developpers. Did any widget go through this already ? This should help a lot in order to freeze the API for v1.0 and improve code quality. Maybe we should define a process, for example : Complete javadoc (public/protected, no warnings) ->fix critical/major bugs -> api & code review -> fix detected problems -> snippets/doc -> ready for 1.0 release .. and publish each widget state in this process on the web site. This will give a better idea of each widget state and help us to keep these objectives in mind :-) * Web site : Chris, you were working on a new home page for the project. Can we help you on this ? Did you receive screenshots for all widgets ? Regards, -- Nicolas
_______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
