Hi, On 30/04/2012 16:45, Alan Steinberg wrote: > What percentage of release notes are created after the final build of > packages, during the final testing? I don't think we would consider > respinning a package just to add release notes, so we would end up > with a "mixed bag" of some release notes that are part of the > installation and some which are still in a documented "READ ME FIRST" > format. And, to a customer, we appear to be 'backpublishing' or updating SRUs even though there has been no binary change.
However we know that release notes do change, issues are found after release, workarounds and special install instructions for customer reported cases get added etc.. So a mechanism to alter the release notes after release would be nice. For example SRU5 shipped with an issue whereby you could not install it if you had library/xmlrpc-c installed. This was fixed in SRU5.5 and the README for SRU5 was updated to list the workaround. What would be nice is if we could alter the release note mechanism in SRU5 after it shipped to inform users who had library/xmlrpc-c installed that there was a workaround, and again to inform them if they explicitly tried to update to SRU5 that a fix was available in SRU5.5. Cheers, ~Al _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
