Alan Coopersmith wrote: > Shawn Walker wrote: > > On 02/ 3/10 09:46 AM, Alan Coopersmith wrote: > >> Alan Steinberg wrote: > >>> It's best for internal testers to wait for the announcement with release > >>> notes before proceeding with upgrading to a new release, even though the > >>> bits are available on the internal staging server. > >> > >> Will the update manager be fixed to not pop up the "New release now!" > >> notification until a flag is set on the repo indicating the release is > >> announced? > > > > No one's opened such an RFE, but I don't know how it could actually be > > implemented yet. > > >From a quick brainstorm of the two-birds-at-once school: > - Add a metadata item to entire or a similar package that has a unique > URL for the release notes for the build. > - Update manager should not show the build is available until that URL > resolves. Once it does, that link should be shown when offering the > new build. > > Should be no change to pkg itself, just to the publication process and > the update manager.
I'd prefer to see us implement a real staging server, like we used to have, and only put the bits on a more widely available server once whatever testing is required has been done from the staging server. Publishing bits and hoping they stay hidden doesn't work, regardless of how many hoops you put into the mechanism. Danek _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
