This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Promote Major Upgrade of IDE | ||
---|---|---|---|
Product: | platform | Reporter: | Jiri Rechtacek <jrechtacek> |
Component: | Autoupdate | Assignee: | dlipin <dlipin> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | anebuzelsky, av-nb, jkovalsky, pjiricka, pzajac, rnovak, sustaining, tmysik |
Priority: | P3 | Keywords: | PLAN, UI |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://wiki.netbeans.org/AutoupdateSupportsMajorReleaseUpgrade | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Jiri Rechtacek
2008-05-18 14:51:23 UTC
Reassigning to the new "autoupdate/*" owner dlipin. *** Issue 153521 has been marked as a duplicate of this issue. *** Any plans for this issue? Allmost all programs are installable via update (firefox, ubuntu, antivirus). This issue doesn't allow us to update platform with every minor release... Petr, The current plan (for 7.0) is to show information in the IDE (platform application) about the new major version released and probably to open specific URL in the browser where one can get(download) a new version. The real upgrade (e.g. from 6.5 to 7.0) by means of the IDE (platform application) is unfortunately not planned for 7.0. Dmitry Some more ideas here: http://wiki.netbeans.org/NetBeansMajorVersionUpgrade Fixed in http://hg.netbeans.org/core-main/rev/beaca5e3bd5f http://hg.netbeans.org/core-main/rev/2560f306da37 Now the promotion is done using "notification" element in the UC catalog: <notification url="someurl">some message</notification> When such element is found in the catalog, the appropriate notification is shown to the user using the standard NetBeans Notification API. The support for adding this element to the catalog (generate-uc-catalog/MakeUpdateDesc.java) is added in the second changeset. The recomended way to set notification is to write notification data - which is controlled by properties catalog.notification.message and catalog.notification.url - to notification.properties file, e.g. catalog.notification.message=New version of NetBeans IDE 6.8 is available! catalog.notification.url=http://www.netbeans.org/downloads and provide this file as the argument to ant: ant generate-uc-catalog -propertyfile <path-to-notification-properties> <other arguments> The "message" is divided into 2 parts in runtime : the notification title and details. The notification title is the first sentence in the message. It should be a plain text (no html tags) ended by \n or <br>. The second, optional, "details" part supports simple html elements like <a>, <br/>, <b>, <i> and others - everything that Java`s JTextPane supports as the HTML. It can be multi-line, separated either by \n or by <br>. URL attribute is optional but very desirable from the UI perspective, it is added to the end of "details" part. Each sentence should not be very lengthy (say, less than 200 chars) and worth being separated by the the new line character (\n or <br>). Examples: catalog.notification.message=New version of NetBeans IDE 6.8 is available!\n<a href="http://www.netbeans.org/community/ releases/67/">Learn more about the new release</a>.\nDownload new version at <a href="http://www.netbeans.org/ downloads">http://www.netbeans.org/downloads</a> catalog.notification.url= catalog.notification.message=New version of NetBeans IDE 6.8 is available! catalog.notification.url=http://www.netbeans.org/downloads catalog.notification.message=New version of NetBeans IDE 6.8 is available!\nThis release contains <b>significant improvement</b> in the parsing speed. catalog.notification.url=http://www.netbeans.org/downloads The message and URL is certainly individual for each release and exact wording (and URL) are up to the marketing team. Both changesets worth be included in the next 6.7 patch (after verification, certainly). It would allow 6.7(.1) users be informated about 6.8 release in time (certainly, if they install updates for autoupdate modules). Such notifications can also be used for the milestone builds. E.g. we can let 6.8 Beta users know when 6.7 RC build is ready if add the appropriate notification to the 6.8 Beta UC standard (stable) catalog. Integrated into 'main-golden', will be available in build *200909010201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/beaca5e3bd5f User: Dmitry Lipin <dlipin@netbeans.org> Log: Issue #135279 Promote Major Upgrade of IDE Yet another fix to MakeUpdateDesc.java (core-main#9d764fde7a4a): notification element should be the first one in catalog (before <module_group>, <module>, <license> and others). So overall patch contains 3 changesets: http://hg.netbeans.org/core-main/rev/beaca5e3bd5f http://hg.netbeans.org/core-main/rev/2560f306da37 http://hg.netbeans.org/core-main/rev/9d764fde7a4a Integrated into 'main-golden', will be available in build *200909021401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/9d764fde7a4a User: Dmitry Lipin <dlipin@netbeans.org> Log: Issue #135279 Promote Major Upgrade of IDE (notification element should be the first one in catalog) Notification is good - but will we support actually updating to the new version with the click of a button? Daily trunk oct 08. Can someone answer to Tor's question? It's really curious that you are not able to update whole product in single click. Notifications about new release is in the plan for 6.8 and it's implemented. I'm sorry, but upgrade itself is out of scope. Right now we want this change to be back-ported into 6.7 to notify users about 6.8 once avilable. The new issue about updating the IDE itself just filed: http://www.netbeans.org/issues/show_bug.cgi?id=174345 Restoring verification to allow back-porting. The fix has been ported into the release67_fixes repository. http://hg.netbeans.org/release67_fixes/rev/59de74d942fb http://hg.netbeans.org/release67_fixes/rev/e04634c96f21 http://hg.netbeans.org/release67_fixes/rev/dd4d9870d1eb I didn't know this was done, thanks a lot! It would be useful to update the wiki page so it contains the current status. Also, it would be good to see a mini-UI spec/screenshot: what will the notification look like when it appears? Thanks. |