http://bugzilla.wpkg.org/show_bug.cgi?id=131 Summary: pinpointing a package to a certain revision Product: WPKG Version: 0.9.10 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: enhancement Priority: P2 Component: wpkg.js AssignedTo: mangoo at wpkg.org ReportedBy: kent at cpttm.org.mo QAContact: wpkg-users at lists.wpkg.org Suppose that there is an existing package which now has a new version, assuming that it can perform an in-place upgrade, it is easy to deploy the new version with wpkg: just modify the revision attribute and the install and upgrade commands. However, I'd like to deploy it to pilot group first. To avoid deploying to all users, I can't modify the existing <package>. It means I have to create a new <package>. A solution is to allow pinpointing a certain revision, such as: <profile id="p1"> <package package-id="whfc" revision="123"/> </profile> <profile id="p1-pilot"> <package package-id="whfc"/> </profile> This way all normal computers will belong to profile p1 and will continue to use the existing revision ("123"), while those in the pilot group will use profile p1-pilot and will use the latest revision. This is not only useful for piloting and phased deployments, but also useful if a certain group of users can't or are unwilling to upgrade due to application conflicts or other reasons. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |