Hmm. Yes, it seems like what folks use the Closed state for is open to interpretation. We used it as part of our release review process. We could have used Verified as well I suppose.
I'll copy you on communication with the webmaster around the webstart issue. By the way, are you able to see the nattable.core hudson job configuration? (https://hudson.eclipse.org/hudson/job/nattable.core/configure) We gave you full access to our build. Would you be willing to give Dirk and myself access to the nebula builds so we can emulate your configuration for publishing? Thanks, Edwin On Mon, Sep 24, 2012 at 6:46 PM, Wim Jongman <[email protected]> wrote: > Well, after reading the bug again, this is still not clear. So you can > just ignore my previous advise and make up your own mind after reading the > bug. > > Regards, > > Wim > > > On Tue, Sep 25, 2012 at 12:42 AM, Wim Jongman <[email protected]>wrote: > >> I see. Let me know if I can help. >> >> I have noticed another thing from your impressive changelog [1]: >> >> The bugs are all set to "Closed". Since a few months [2] I know that the >> status closed is used when nothing has been changed. >> >> so the status change should be: resolved-fixed and after that: >> resolved-verified. >> >> Regards, >> >> Wim >> >> [1] >> https://bugs.eclipse.org/bugs/buglist.cgi?product=NatTable&target_milestone=0.9.0&order=Last%20Changed&list_id=3014734 >> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=380833 >> >> On Tue, Sep 25, 2012 at 12:33 AM, Edwin Park <[email protected]> wrote: >> >>> Hi Wim, >>> >>> The webstart issue seems to be linked to Java 7. Looking around online a >>> bit indicates that webstart in Java 7 requires jnlp files to be served via >>> HTTPS. I'll have to work this out with the Eclipse webmaster. In the >>> meantime I have modified the webstart files to force the demo to run with >>> Java 6 only. >>> >>> You are right, there is no update site for this release. This is partly >>> because we were unable to figure out how to publish one from the hudson >>> build (we still cannot see the nebula configuration), and also several of >>> our extension projects require 3rd party dependencies that are not in Orbit >>> at the moment. These are short-term issues and I'm sure they will get >>> resolved, but we didn't want to hold up the release for this. I fully >>> expect our next release to have a p2 update site with signed jars, etc. >>> >>> Cheers, >>> Edwin >>> >>> >>> On Mon, Sep 24, 2012 at 6:18 PM, Wim Jongman <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> I don't see the NatTable update site location from the download site. >>>> >>>> Regards, >>>> >>>> Wim >>>> >>>> On Tue, Sep 25, 2012 at 12:08 AM, Edwin Park <[email protected]> wrote: >>>> >>>>> NatTable 0.9.0 has been released! An announcement has been posted to >>>>> the forum and the web site has been updated to reflect the release. >>>>> >>>>> Thanks all! >>>>> >>>>> Edwin >>>>> >>>>> _______________________________________________ >>>>> nebula-dev mailing list >>>>> [email protected] >>>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> nebula-dev mailing list >>>> [email protected] >>>> https://dev.eclipse.org/mailman/listinfo/nebula-dev >>>> >>>> >>> >>> _______________________________________________ >>> nebula-dev mailing list >>> [email protected] >>> https://dev.eclipse.org/mailman/listinfo/nebula-dev >>> >>> >> > > _______________________________________________ > nebula-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/nebula-dev > >
_______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
