Glynn Foster wrote: > > On 25/10/2008, at 4:26 AM, Dave Miner wrote: > >> jmr wrote: >>> Hi - simple one liner to make sure users are pointed to the right >>> release notes url below after doing a successful Update All in UM: >>> http://opensolaris.org/os/project/indiana/resources/relnotes/200811/x86/ >> >> John, while the page is presently at that URL, it's not what I had >> specified to Glynn and docs, which was $release/$arch(/$build >> optionally) (hence 2008.11/x86) so let's make sure we have the URL >> finalized before you push. Catching up on my mail from earlier this >> week, it appears that Glynn slightly mis-transcribed that in the mail >> to indiana-discuss. > > I figured I'd wait until we actually cut the release before we created > the $build number URL (which will essentially just point at a non-build > number, until there's such a stage where we have build specific release > notes). I still wonder whether $build is actually a good idea, in > particular when we get on to the development releases ie. is $release > going to be 2008.11 or 2009.04 for the dev releases, and whether that > would likely confuse people into thinking they have something that they > don't? >
The issue is that you changed 2008.11 to 200811, when I'd asked to use fields from the release verbatim. If we're going to have the capability to produce and archive specific release notes per-build (which I think we should, it makes for less confusion for users) then we need $buildid. You can change $release to anything you want between releases, if that would abate the concern about advertising the builds as something they aren't. Dave _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
