Schedule for Update Center 2.0 JavaOne (GF V3 TP2) Release

• Requirements from GF V3 TP2
• High level description of the supported feature list for JavaOne (GF V3 TP2) release.

Milestone	Start Date	End Date	Description	Status
Milestone 1	1/29/08	2/8/08	Build system ready, nightly build setup, unit test framework ready	-
Milestone 2	2/11/08	2/22/08	Nightly build setup with automated test cases, UC 2.0 milestone build	-
Milestone 3	2/25/08	3/07/08	UC 2.0 milestone build	-
Milestone 4	3/10/08	3/28/08	Feature freeze. Milestone 4 features working.	-
Milestone 5	3/31/08	4/15/08	Bug fixing, finalize TP2 release.	-
Milestone 6	4/16/08	4/28/08	TP release.	-

Milestones

Some of the features below reference the Update Center 1.0 use cases (referenced as UC1-#). This milestone plan is also based on the Stage 2 Example for Update Center 2.0.

Milestone 2 Features

M2 Toolkit Features

M2 Platform Support

Windows XP x86 32-bit with some limited testing of Windows XP x86 64-bit and Windows Vista x86 32-bit and 64-bit

M2 IPS Client and Image Assembly Features

• (DONE) On a Solaris x86 system, assemble a universal image per the image creation flowchart targeting Windows x86 for deployment.
  • (DONE) Since the bootstrap tool won't be available yet, pre-install the IPS client and Python for Windows in the universal image. (Due to the presence of the complete IPS client and the Python runtime, the image won't really be "universal" in M2).
  • (DONE) requires ips-solaris-x86.zip
  • (DONE) requires uc-universal.zip (hardcoded with Windows python)
  • (DONE) Instructions for how to build universal images (no bootstrap required because not really universal)
• (DONE) Availability of private repository (updates.sfbay, repo.zip, and ips-*.zip)
• (DEFERRED) Availability of public repository (pkg.updatecenter.java.net) (trm - P2 for MS2)
• (DONE) UC GUI package and its dependencies in repositories

M2 UC GUI features

• (DONE) GUI can be started and represents overall layout (overall structure of menus, frames, tabs, etc.)
• (DONE) ability to list installed packages (UC1-1, UC1-11)
• (DONE) ability to list available packages (UC1-1, UC1-6, UC1-12)
• (DONE) ability to install an available package (no config) (UC1-15)
• (DONE) installation dependency resolution (UC1-16)

M2 Toolkit Example Use

M2 Target Content

• (DONE) GFv2 IPS packages from example 1 in private repository (updates.sfbay)
• (DONE) At least one add-on IPS package (mysql-jdbc) in private repository (updates.sfbay)
• (DONE) To exercise install dependency resolution, some of the add-on content needs to have dependencies available in the repository (puffin depends on wxwidgets)

M2 Installation Experience

• (DONE) Wiki instructions on how to download an image, deploy it, and use it to install an add-on
  • (DONE) After installation, user manually adds UC GUI packages and dependencies via "pkg install ..."
• (DONE) GFv2.zip download distribution available (Windows only for Milestone 2)

M2 Testing

• UC Test Specification under internal review
• Manual Testing of UC implemented features in Milestone2 on the supported platforms (Windows XP x86 32-bit with some limited testing of Windows XP x86 64-bit and Windows Vista x86 32-bit and 64-bit) and verification that UC Use Cases are working
• Testing of available instructions

Milestone 3 Features

M3 Toolkit Features

M3 Platform Support

• (DONE)Carry forward Windows x86 support from M2

Add:

• Mac OS X 10.4 PPC and x86 (10.3 and 10.5 are nice to have for M3) (DEFERRED until at least 3/12)
  • (DONE) run from build space (exception: need local install of python, wxPython)
  • (DEFERRED) deliver distribution files
• (DONE) Solaris 9 and 10 on x86
  • (DONE) run from build space
  • deliver distribution files
• (DONE) Solaris 9 and 10 on SPARC
  • (DONE) run from build space
  • (DONE) deliver distribution files
• (DONE) OpenSolaris Developer Preview Release 2 x86
  • (DONE) run from build space
  • (DONE) deliver distribution files
• (DONE) Red Hat 5.x x86 32-bit (Linux in general)
  • (DONE) run from build space
  • (DONE) deliver distribution files

Priorities:

1) (DEFERRED)remerge IPS into ported IPS (top priority)

2) "ant run-puffin" target must work on:

• (DONE) Windows
• Mac OS PPC (assuming external python and wxpython) (Manpreet)
• (DONE) Solaris x86 (Tom)
• (DONE) Solaris SPARC (Joe, Kasso)
• (DONE) Ubuntu x86 (Ckamps verified)

3) get deliverables built (repo_*.zip, uc_universal_*.zip and ips_*.zip) for (until we have a universal image)

• (DONE) Windows
• (DONE) Solaris x86
• (DONE) Solaris SPARC
• (DONE) Linux

Priority call: make end to end functionality work, including truly universal image, before expanding support to many more platforms

M3 IPS Client and Image Assembly Features

• (DEFERRED) Make universal image truly universal
• (DEFERRED) Bootstrap command available in image
• (DONE) Minimized multiplatform python in repositories for use by bootstrap (limited platforms see above)
• (DEFERRED) Bootstrap automatically downloads and install UC GUI and its dependencies

M3 UC GUI Features

• Edit -> Preferences (UC1-3, UC1-4, UC1-5) (Kasso) (proxy config a P1, all others a P2 for TP2)
  • (DONE) Proxy Configuration - but the proxy info is not used by puffin
  • (DONE) Proxy used by puffin
  • (DONE) GUI Configuration File and API

• Package data display (UC1-13)
  • (DONE) Component categories - first implementation (Ckamps) - Overall approach to model understood. Publishing category description package and beginning GUI integration work today (March 12) to deliver poor man's implementation by end of March 14 (i.e. similar to NetBeans plug-in manager, display categories as new "{Category" column in "Installed Components" and "Available Add-ons" views rather than implementing separate scrolling pane for categories. We'll implement separate category pane later.)
  • (DEFERRED) Package/component Title rather than package name (Tom)
  • (DEFERRED) HTML-based Package/Component Description (Tom)
  • (DEFERRED) Layout "Additional Data" along with Description to ensure UC 1.x data is covered (Ckamps)

• Installation (Manpreet)
  • (DEFERRED) Prompt to accept license during install (UC1-24) (Joe) - Understand approach by March 7, implementation/integration following week.
    • Model - Where is the license store and API to fetch it (Joe)
    • View - TBD
  • (DONE) First implmentation of progress display for package download and installation (Manpreet)
  • (DONE) Silent configurator invoked during package installation (Joe)

• (DONE) Ability to remove a package (UC1-17) (Manpreet) (first iteration - still open questions about dependencies)

• (DONE) Initial implementation of Update Processing (Manpreet)
  • Ability to list available updates (UC1-1) (Manpreet)
    • Model (Manpreet)
    • View (Manpreet)
  • (DONE) Ability to check for available updates manually (click refresh button) (UC1-10) (Manpreet)
  • (DONE) Ability to install updates
    • (DEFERRED) Dialogs for the flow (Manpreet)
    • (DONE) Initial implementation of showing what else will be installed in the view pane

• (DEFERRED) Notification Support
  1. Purely non-GUI tasks (Kasso)
     • Notification applet impl or windows (P2) (For M3 launch by hand?)
       • Design
       • Implementations
         • for Windows
         • for Solaris
         • for Linux
         • for Mac OSX
  2. GUI Tasks (TBD)
• Notification applet installed for Windows (M2) (TBD)
  • • installation implementations
      • for Windows (M3) (For M3 launch by hand?)
      • for Solaris (M4?)
      • for Linux (M4?)
      • for Mac OSX (M4?)
• Notification detects newly published updates (UC1-7) (Kasso)
  • API
    • for Common Configuration access (See first task in GUI features list) (Kasso)
    • for Locking/concurrancy (Kasso)

• (DONE) Initial build out of "Help->Contents" content. - initial implementation - widget is there with sample content, but no real help text - Mike has been working with the HTML help demo app. HTML help feature needs to be tied to GUI's Help -> Contents option. A well-defined 2-3 hour task apart from ongoing integration of help content. Menu integration could be done by end of March 14th, but it depends on prioritization of other GUI features.

• (DONE) Initial implementation of changing the number of columns in different views * (DONE) INSTALL (Manpreet) * (DONE) UPDATE (Manpreet) * (DONE) REMOVE (Manpreet) * (DEFERRED) NO MODE VIEW (Milestone and assignment TBD)

M3 Toolkit Example Use

M3 Installation Experience

• (DEFERRED) An install app in the GFv2U1 image that does bootstrap and initial config of pre-installed packages
  • at a minimum this might be executing a script after an unzip
• (DEFERRED)Bootstrap automatically adds UC GUI packages and dependencies via "pkg install ..."
  • Note on headless systems, this step is unnecessary and can always be done later via "pkg install".

NOTE: the installation experience for the toolkit example use for MS3 will be the same as for MS2 except that there will be multiple preinstall image file downloads available for the various platform.

M3 Testing

• (DONE) UC Test Specification published
• (DONE) Definition of the list of Acceptance Tests (or Quick look tests)
• (DEFERRED) Start Tests automation
• (WILL STILL BE ALL MANUAL) Mix of Manual and Automated tests execution based on features implemented in Milestone3 on supported platforms (except MAC-OS PPC because lack of this platform, only MAC-OS x86 will be covered)

Milestone 4 Features

In parallel to M4 the UC toolkit will be integrated with the GF V3 bits as part of the GF V3 project's TP2 milestones.

UC Toolkit focus areas for M4:

• Support delivery of usable GF V3 TP2 distros (e.g. ensure Java bootstrap and distro assembly support is delivered)
• Presentable, but basic GUI and notification UI
• Extremely solid support for Windows. Good support on other OS platforms
• Sufficient call home usage reporting (tentative)
• Solid, but basic update the update client capability
• Maximize awareness of available updates
• Legal requirements met

M4 Toolkit Features

Feature	Description	Rationale	Notes	Status
UC Toolkit, General
OS Support: Mac OS X	* Minimized python in maven2 repo * WxPython in maven2 repo	Must Have Platform Support	Joe: committed as P1 for 3/28	DONE
OS Support: Solaris 9/SPARC and Solaris 10 before U4 support	Need to resolve issue with libmd.so	Must Have Platform Support	Raj: P1.5 - need to look at it, P1 that all standard client operations must work on S9U4 and later	DEFERRED (will be completed after MS4)
Finalize filesystem layout and package and tool naming	See post to dev alias	* Legal/Branding * Must Have Solid Initial Layout Structure	Joe: P1 committed for 3/28	DONE
Biz Intelligence
Minimum call home support	Need to spec out minimum requirements. Service Tag transmittal along with biz info should be considered for M4	* Must Understand Basic Usage Info to Begin Assessing Success of Both GF V3 and UC * Manage Subsequent Changes and Features	(ckamps) Need support from IPS to log the HTTP header information at the access log. Need to follow-up with IPS team .	RESEARCH STARTED
IPS
Update our IPS from gate		Must have latest IPS	Tom: P1 - commit for 3/28	DONE - initial porting changes pushed to gate. Note, this does not include the change for setting .org.opensolaris,pkg hidden on Windows
Java bootstrap	Bootstrap code with truly universal uc_universal.zip	Must Have to Support GF V3 Universal Downloads Bill:In general, are all of our paths out to the web able to use the system's proxy settings, so the user doesn't have to configure proxies for each separate program? Nazrul: We also need to support offline installation scenario and allow user to download UC runtime at a later timer after installation.	Tom: P1 - commit for 3/28.	DONE
Updating IPS	Ensure sufficient testing of updating IPS and its dependencies in place.	Maximize Ability to Deliver Follow-on Fixes via Updates	Raj: P1 requirement. Tom and Manpreet will help.	DEFERRED for after MS4
Windows: Hide .org.opensolaris,pkg Directory Name Under Root of Install Image		Initial Impressions	As a workaround for TP2, in the Java Bootstrap code, we'll call the Windows "attrib" command to make the dot directory a hidden directory. As long as the user has the default explorer settings, he won't see this directory.	DONE - this is done by the bootstrap code
Add License and Copyright File	Add necessary files to IPS install location			DONE
Desktop Notifier
Notification applet installed for all platforms	Targeting Windows task tray integration as a P1 requirement for TP2 while all others are a P2.	Maximize Awareness of Updates and Add-ons	Kasso: P1 committed for 3/28	DONE - Windows only
Hide Notifier Icon	Ability to hide notification icon when no updates are available		Kasso is planning on supporting this behavior UC1 Use Cases: UC1-8	DONE
Schedule update notifications	Support 3 or so basic frequencies	Need to give user the choice of how often the system should check for updates	Looks like we can support 3 or so basic frequencies UC1 Use Cases: UC1-2	DONE
Use Image Titles	Leverage image title from "title" file housed under .org.opensolaris,pkg/ directory in installed images			DONE
GUI
Update the Update Toolkit Support: Special handling for UC toolkit updates	* Attempt to apply updates to the toolkit first upon GUI startup * When user lists available updates and marks updates for installation, apply toolkit updates last or as a separate transaction * Whenever GUI recognizes that toolkit updates have been applied, ask the user to restart the GUI, shut it down and restart automatically	Must Have Solid UC Update Capability Bill: Doesn't Windows generally insist that you update the updater before installer any later updates? If later updates will only install with newer versions of the pkg tools, you might have to insist on that. If we can't handle this properly at the beginning, the way out is to put only the updated tools in the update center, and supply an update center update that switches to using a different remote repository for further updates. We probably ought to plan for "versioning" the remote repository at this lower level just in case.	This goes beyond just GUI and needs to have a complete strategy. Need discussion.	DEFERRED for after MS4
Update Handling	Express Install of Updates	Applies to Update Notifier and GUI: * GUI: preselect available updates (should be easy) * Notifier: per plan, support "Apply Updates" option which will take the user to the confirm dialog of the GUI. From UC1 use cases: User should be able to choose to install all the available updates or software components. If there is any failure, the details must be shown clearly. UC1 Use Cases: UC1-14	Could defer, but should be easy to ensure available updates are pre-selected in GUI. Kasso is planning to support the "Apply Updates" option from the notification applet. Bill: Not clear to me this is a P1.	DONE - if it's just checking all available updates by default.
Update Handling: Recognize available updates during startup and display		Must Have Solid UC Update Capability		(DONE) 1/2 - 1 day Commit: 3/28 (Checks updates for the default image (CWD or first in the list or newly added)
Installation Progress Part II of III: Make steps clear	Add clear titles to the steps and files, but retain the existing progress bar.	Basic Usability of Prominent Feature
Categories: Part II of III	Deliver category files via separate, per repository package and install in IPS data area	Supportability (repo owners must be able to assign and update categories without having to redeliver UC GUI packages) Bill: Might be able to live without categories for TP2.	Ckamps delivering support by 3/28	DONE
Confirmation Dialogs	* Show abbreviated package names and display package names and versions in two columns. * Add remove confirmation dialog * Refer FSD and to xDesigns wireframes (see FSD for pointer).	Basic Usability of Prominent Feature		DONE)P1 - Remove dialog P2 - Rest
License: Click Through License Acceptance	* Applies to add-ons. Might also apply to updates. * Concatenated license is sufficient (UC 1.x is implementing concatenated approach to replace current separate tab per license approach).	Legal Requirement		DONE Joe model / Manpreet GUI.
Component Data: Add description data from packages	Display at least the description information from the package	Basic Usability	Using new description_long attribute convention in IPS packages.	DONE Note: Would need this implemented on IPS side too - manpreet.
Image Titles: Part I of II	Support setting and modifying title of image within an IPS image. e.g. "GlassFish V3 Technology Preview 2"	Notifier can't provide an easy to understand notification by just listing the fully qualified path of an installed image	Manpreet hatched a workaround by adding a file named "title" to the .org.opensolaris,pkg directory. Creating a new image via the GUI adds this title file to the appropriate location. The list of installed images in the left pane of the GUI displays the image title based on the content of the title file. For TP2, both the updatetool and notifier should use the string contained in this file if it exists. The GF V3 distro assembler folks will need to ensure that this file exists in their preinstalled image and contains the string of interest to them.	DONE
Hide Not Yet Implemented Features		Avoid Setting False Expectations with Users Bill: Again, hopefully easy, but I'd live without it.	The rest will be implemented in MS4 Commit: 3/28 for finishing Toolbar view toggles	(ONE
Application Icon: Integrate use of generic application icon	Otherwise, Python icon shows up in the task tray and possibly in the Mac OS X dock. Extra bonus: Provide some pizazz to the GUI and Notification UI.	In Your Face Feature	Already addressed for Unix and Windows. Mac OS X is TBD.	DONE Mac OS X DEFERRED
Component Data: Fill Component column with title of component rather than package name		Basic Usability of Prominent Feature	1/2 - 1 day Commit: 3/28	DONE
Create Image: Review and enhance text labels in Create Image dialog	Basic Usability		Commit: 3/28 for layout/text cleanup	DONE
Reconcile Refresh Buttons	xDesign feedback: * Why are two refresh buttons shown, one in toolbar and one next to action button after the list, when list views are displayed? * How does the user know what these buttons do? Perhaps rename to "Refresh List" and drop toolbar button in favor of button near each list. Consider moving refresh button to just above list or to lower left of list - away from action button	Basic Usability of Prominent Feature	1/2 day Commit: 3/28	DONE
Installed Image Properties: Display repository URL	When user clicks on installed image, display in read only mode the main properties of the image including the repo URL.	Supportability	Next phase needs to display image properties in a dedicated right pane along with an "Edit Properties..." button per the FSD.	DONE, initial implementation
List Views: Add view titles and summary info	Make it more clear as to the nature of the list being displayed by adding a title of the view just above each list. For list of updates, highlight number of updates available. See mockup in FSD.	Basic Usability of Prominent Features Maximize Awareness of Updates	1/2 day Commit: 3/28	DONE
Update Handling: Summarize and highlight available updates at top of components list per FSD		Maximize Awareness of Updates	Is this the same as above?	DONE
Add License and Copyright File	Add necessary files to updatetool install location			DONE
Configuration
Configuration handled for packaging uninstall and update
Configurator progress	TBD	TBD	Joe/Manpreet
Misc
Help: Completion of Help Content	English for TP2	Must Have Bill: Hopefully trivial help is doable, but if the update center is simple enough, I'd live without any help for TP2.	Mike Fitch is working with ckamps to check in initial content by end of March 28	DEFERRED - MS4 has help skeleton

M4 Toolkit Example Use

The final round of UC GUI features for TP2 will be exercised using the GF V2 example bits.

M4 Testing

• Execution of all the tests that apply to TP2 release (Functional Tests and System Tests)
• Acceptance Tests (or Quick Look Tests) fully automated but internal to QA workspace
• Progress made on other testing areas automation

Milestone 5 Bug Fixes

The primary goal of milestone 5 is to fix bugs that have accumulated so far. A secondary goal is to finish up features whose implementation was incomplete or which needs correcting.

Update Center bugs are tracked in two places:

• updatecenter2.dev.java.net IssueTracker (report)
• defects.opensolaris.org, pkg category, UC2 in whiteboard field (report)

Here is a record of the bug counts:

Date	UC2 P1	UC2 P2	UC2 P3	IPS P2	IPS P3	IPS P4	Total
4/3/2008 (MS4 completion)	1	8	19	3	8	6	45
4/4/2008 (iteam)	8	14	37	3	8	6	76
4/8/2008 (iteam)	5	14	49	3	10	7	88
4/10/2008 (iteam)	2	11	49	2	12	7	83

The target criteria for MS5 is:

• No unresolved UC2 P1 or P2 bugs
• No unresolved IPS P2 bugs

All issues that must be fixed for MS 5 must be recorded in one of these defect tracking systems. There will not be a separate list of changes for MS 5 recorded here. The report links above can be used to get the lists of bugs that are still unresolved.

Milestone 6 Bug Fixes

The goal of milestone 6 is to deliver fixes for stopper (P1) bugs that are discovered after MS5 was delivered but are essential for getting into the TP2 release.

• Open Stopper Bugs (priority = 1)
• Resolved bugs for MS6 (target milestone = TP2-MS6)

After Milestone 4, Updates to TP2

Intent would be to continue development past code freeze and deliver these features within updated packages. Users of TP2 could apply the updates to obtain these features.

Feature	Description	Rationale	Notes
IPS
Merge IPS port into IPS gate		Must Have Latest IPS, Must Move Away from Manual Resyncs	DONE
Desktop Notifier
Safe Config Access	Ensure applet does not read partially written/complete per user config		UC2 Issue 53
GUI
Component Data: HTML Component Description Support			UC2 Issue 45
List Views: Highlight Newly Seen Add-ons and Updates	Via "new" icon and sorted to the top of the list. UC1 Use Case: UC1-22		UC2 Issue 46
List Views: Display actual download size for updates	Currently lists complete download size.		UC2 Issue 47
List Views: Sortable columns	A basic, expected feature of column oriented views.		UC2 Issue 48
Categories Support: Part III: Support separate pane to list categories per GUI FSD			UC2 Issue 49
Business Intelligence
Enhanced call home support			UC2 Issue 54
Ability to Cancel Download Gracefully	UC1 Use Case: UC1-19	Probably Fundamental UI Guideline	2 days, UC2 Issue 50
Installation Progress Part III of III: Cleanup install add-on, apply updates, and remove component progress dialogs	Mimic design in xDesign wireframe. (See FSD for pointer) Why isn't a left to right progress bar being used?	Basic Usability of Prominent Feature	The install happens in 4 steps (Create Plan/Download/Install/Actions). Step sizes are not known beforehand. Some sizes are only know partially after some way into the process. Time: 2-3 days, UC2 Issue 51
Overall Status: Provide concise and prominent summary of updates across all images	Show status above selection of any one installed image. Needed to help ensure users notice updates for all installed images. Ties into the notifier's linkage to the GUI.	Maximize Awareness of Updates	Any operations which traverse the whole repository can get very slow. We need a precise definition of what this item will do. UC2 Issue 52

After TP2, Before Beta

Some of these features could be delivered as updates to TP2, but they may not be considered as a high of a priority as those listed above.

Feature	Description	Rationale	Notes
IPS
Image Titles: Part II of II	Using IPS APIs, support setting and modifying title of image within an IPS image. e.g. "GlassFish V3 Technology Preview 2"		Replace workaround with IPS APIs.
HTML-based Package/Component Description
Clean hiding of .org.opensolaris,pkg directory on Windows
GUI
Layout "Additional Data" along with Description to ensure UC 1.x data is covered
Prompt to allow opt-out of anonymous usage stats (UC1-9)
Preferences: Automatically Apply Updates	Option is set to "off" by default. (Since IPS doesn't have a marshalled form of packages, we can't support the related "Download updates automatically, but don't install them" option).
Right-click menus throughout	Consider right-click menus on components in list views and in installed images tree.
No Mode View	Integrate Welcome HTML in right pane when no install image is selected by default	Only applies when GUI is launched outside of install image context (doesn't really apply to GF V3 TP2)
Registration of Installed Distro	Generalize support already present in GF V2 UC 1 to help promote registrations of overall installed distro.
Registration of Add-ons	Ability to register add-ons based on service tags where appropriate
Multi-window Support	Ability to select File -> New Window to display new GUI window. Also addresses subseqent starts of the GUI app: they result in new window rather than new copy of the app Includes locking support to avoid corruption of per user GUI config data. BTW, what locking support does IPS itself support?
Component Data: Display Change log data for Updates
Component Data: List of installed files for installed components
Language Support: Multi-language Implementation	Address required languages in support of GF V3. (See separate i18n item above).
Image Settings: Platform independent repository URLs	Enable distro assemblers and repo maintainers to publish platform-independent repo URLs that can be used regardless of client OS platform.
Image Properties: Support multiple repositories	TP2 will be able to point to only one repository.
GUI Execution: Suppress command window on Windows
User Preferences: Add list of repos of interest	Helps support notion of pick list while creating and modifying image settings.
Language Support: Ensure implementation is I18n compliant		Avoid Rearchitecting Downstream	We are mostly compliant. However no G11n tests have been performed yet. ~1 day to perform some minimal testing and be compliant. Stretch goal for TP2
Accessibility Support: Section 508 ready	For GUIs	Big Rule

Open Questions

• Prompt to allow gathering of anonymous usage stats (UC1-9) (ckamps: P2 for TP2)
  • Included in GF V3 installer below, but what about the case where updatetool is installed via IPS CLI? Is this relevant for the TP2 situation? Perhaps in offline initial install situations where the Java bootstrap for UC cannot complete its task.
• Configuration handled for packaging uninstall and update
  • Need someone to help clarify this one and then suggest a prioritzation of it.

GF V3 TP2 Distro Features Related to UC Toolkit

GF V3 Distro
Installer: Automatically attempts to install Update Tool GUI	After triggering Java bootstrap, installer invokes "pkg install updatetool" to install GUI and dependencies on the fly Potentially for M4 UC team provides script installer to demonstrate this integration.	Maximize Awareness of Updates and Add-ons	(Snjezana) Installer plans to call the Java bootstrap.
Web Admin Display of Available Updates and Add-ons	Carry forward and possibly improve upon current implementation.	Maximize Awareness of Updates and Add-ons	Need a Java binding. Can point to a "Getting Started Guide" and the repository url (pkg.glassfish.org).
asadmin CLI Admin Display of Available Updates and Add-ons	Seems important, but need confirmation.	Maximize Awareness of Updates and Add-ons Bill: This would probably be pretty easy to do when starting up in "multi-mode", which is probably good enough for a first release. Probably need to limit this to situations where asadmin can tell that it's talking to a terminal.	Need a Java binding. Will not happen.
Prompt for UC Config During Distro Install	Enable GF V3 installer to feed config settings into UC user preferences. * Opt-in for update notification * Opt-in for sending anonymous usage info * Proxy settings UC1 Use Cases: UC1-23, UC1-25, UC1-9	* Update Notification and Usage Info: Legal Requirement * Proxy: Maximize Awareness of Updates and Add-ons	(Snjezana) Installer will have a checkbox similar to UC 1.x.
Launch update GUI at end of distro installation	* At user's option * consider using pkg CLI to make them aware of updates when installing via terminal (non GUI)	Maximize Awareness of Updates and Add-ons	(Snjezana) May be able to provide a button to launch UC?

JavaOne Launch Activities

Blog Storm

• Please request community feedbacks. Refer everyone to dev@updatecenter.dev.java.net email alias.
• Please use the following tags - updatecenter, opensource, ips, opensolaris, javaone, glassfish
• Please remember to send your blog url to theaquarium@sun.com
• If any information exists in a wiki document, please refer your blog readers to the wiki with a summary in your blog.

Area	Suggested Title	Scope	Owner
Business	Why Use UC 2.0?	Talk about the value proposition of UC 2.0? What problems does it solve? Why should someone consider using this toolkit? Is it better than other opensource solutions? etc.	Ed Conzel
Roadmap	UC 2.0 Roadmap	Talk about UC 2.0 roadmap and request feedbacks.	Ed / Christopher Kampmeier
Overview	Intro to UC 2.0	Talk about what this project is all about. This can serve as the high level quick start guide.	Christopher Kampmeier
CLI	How to Use IPS CLI	Wrapper blog about how to use the CLI.	Christopher Kampmeier
GAP	UC 2.0 participation in GlassFish Award Program	How the community can participate in GAP	Christopher Kampmeier
JavaOne	UC 2.0 @ JavaOne	Where users should go to see UC 2.0 in action and meet the developers.	Christopher Kampmeier
GUI	UC 2.0 UI Tour	A detail blog about how to use the toolkit UI.	Manpreet Singh
IPS	Road to Multi-OS IPS	Talk about the technical details on how IPS was made multi-platform. Why is this important?	Tom Mueller
Repository	Practical Guide to Setup Your IPS Repository	Wrapper blog that leverages the IPS screencasts and shares how one should setup the repository. We may talk about the script that syncs the different repositories, --readonly flag, etc.	Tom Mueller
Bootstrap	UC 2.0 Java Bootstrap	Talk about what does this do, when to use it, etc.	Tom Mueller
Adoption	How to Integrate UC 2.0?	Talk about what users need to do to integrate UC 2.0 with their software.	Tom Mueller
Notifier	Deep Dive Into the Notifier	Everything you wanted to know about the UC 2.0 notifier - what problems does it solve, interfaces, technical details, etc. This can be a series of blog also.	Chris Kasso
Client Side Config	UC 2.0 Client Side Config: User's Perspective	How and when to use client side config.	Joe Di Pol
Quality	UC 2.0: A Quality Perspective	Talk about what platforms are being tested for the JavaOne Technology Preview release. Set users expecctations. How people can help, etc.	Faouzia El Idrissi
Case Study	Ingetrating UC 2.0 with GF V3	Talk about the good, bad and the ugly of integrating UC 2.0 with GlassFish, lesson learned, etc. What advise would you give to others?	Snjezana Sevo-Zenzerovic
Download Page	The New UC 2.0 Download Page	Announce the new UC 2.0 download page, nightly build, promoted build and what is available for download?	Jason Zhou
Globalization	UC 2.0 Globalization: How you can help?	Talk about the globalization plans and how the community can help with the translation?	Julie Selby
Docs	UC 2.0 Help: Does it help?	Talk about the bundled help implementation and request feedbacks.	Michael Fitch
Docs	UC 2.0 Documentation Hub	Talk about the planned docs for UC 2.0 and request feedbacks.	Michael Fitch

This page (revision-84) was last changed on 18-Apr-08 13:39 PM, -0700 by TomMueller.
This page was created on 29-Jan-08 14:04 PM, -0800 by UCWiki.

More info...