[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [nebula-dev] Nebula Build
|
Hi
I'll start working on a new homepage, based on
http://www.eclipse.org/swt/widgets/. Chris, can you send me the pictures you have ? (I'll also include the incubation logo on it.)
Is the following checklist for 1.0 ok for everyone ? Did I miss something ?
* Full javadoc (public/protected, no warnings)
* Fix all critical/major bugs
* API & code review w/ Nebula devs
* API & code review w/ SWT devs
* Fix identified problems during reviews
* Snippets / doc
We're not using the wiki right now, I think this would be the right place to put these requirements and each widget progress. I created a (nearly empty) page for Nebula :
http://wiki.eclipse.org/Nebula .
Regards
--
Nicolas
On 7/19/07, Chris Gross <
schtoo@xxxxxxxxxx> wrote:
Hi Nicolas,
I have not had any code (really API) reviews with the SWT devs. I have
some existing work to take care of in my widgets (primarily Grid) until
I'm ready for that. I think each widget developer should feel free to
set these up when it makes sense. I think Dave Orme (CompositeTable)
seemed ready but he hasn't responded to any emails on this list in
quite a while. If you or anyone is ready for one of these reviews lets
set something up.
Re process - yea I think thats a good idea but alot of it is probably
more about just defining requirements for a 1.0 rather than a specific
process. For ex, we need javadoc, snippets, etc.. done before we can
qualify something at 1.0. Perhaps the process should be more about
other committers verifying those things...? We could also schedule
internal Nebula reviews where other committers review the code/API
before a 1.0...?
Re web site - I never did get around to that. Everyone sent me pics
but the aforementioned Dave. If you or Peter want to jump on that I'll
try to dig up those pics (and send you my own).
Regards,
-Chris
Nicolas Richeton wrote:
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
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
--
Nicolas Richeton
