Anybody able to give me a definition of exactly what the beta release is!? i.e. feature complete? targeted at which set of users?! Or if somebody could point me in the right direction..

Rahul Sundaram wrote: > Jonathan Roberts wrote: >> Anybody able to give me a definition of exactly what the beta release >> is!? i.e. feature complete? targeted at which set of users?! >> >> Or if somebody could point me in the right direction.. > > Refer > > http://fedoraproject.org/wiki/Releases/9/Schedule > http://fedoraproject.org/wiki/Releases/Schedule > > Beta is feature freeze and string freeze. Alpha is targeted for > developers. Beta for early adopters and Release Candidate for full > community participation. > > Rahul > So whats going on with the single source summary then does that get replaced with the beta release notes?

On Mon, 2008-03-03 at 19:50 +0000, Jonathan Roberts wrote: > On 01/03/2008, Marc Wiriadisastra <marc(a)mwiriadi.id.au&gt; wrote: > > > > So whats going on with the single source summary then does that get > > replaced with the beta release notes? The Alpha/Beta release notes (single wiki page) are a subset of the SingleSourceSummary. > I think so for now Marc...got my head in a big spin with the > SingleSourceSummary! Not sure anybody totally understands it actually, > though perhaps Karsten does and when he returns things may look > rosier. For now though, feel free to move content from SSS or add > stuff to the Release Notes :) FWIW, Paul may also understand it, so we have being-hit-by-a-bus protection. Does this explanation work? :: Problem -- multiple summaries (relnotes, press releases, wiki pages, announcements, blog entries, articles) being written for a given release (Alpha, Beta, RC, Gold), all repeating work; no clear place to go for a good _summary_ of a given release. Solution -- one single page that contains all the _potential_ content (source) for any one of the given target summaries. Call this the SingleSourceSummary (SSS). What the SSS is not -- It is not a page meant to be read of itself: two sections may contain nearly identical content but be written in two styles, such as "Big and happy!" and "Terse and descriptive". It does not require a consistent writing style for sections: see above examples Stable: expect it to change constantly; don't use it with an Include() macro but copy/fork

What the SSS is -- A resource for *anyone* writing about a given Fedora release A collaboration amongst various parts of Fedora -- Marketing, Docs, Rel Eng, etc.

On Thu, 2008-03-06 at 22:00 +0000, Paul W. Frields wrote: > On Tue, 2008-03-04 at 17:22 -0800, Karsten 'quaid' Wade wrote: > > What the SSS is not -- ... > > Stable: expect it to change constantly; don't use it with an > > Include() macro but copy/fork > > This last item is where you lose me, but then again, I'm easily lost (as > anyone who's ridden in my car knows). One of the goals of a SSS -- I > thought -- was to allow us to include the content elsewhere multiple > times, and not have to repeatedly check multiple pages to see that > they'd all been changed uniformly. This was a big problem in the last > Release Notes cycle where a contributor made a change to one source > document, and I (as one of the release notes editors) had to carry that > change, and fix the resulting translation POT material, in several > documents. Maybe I was a bit overboard with that description. Maybe it's more that, unlike other parts that we Include(), this one is apt to change during the release cycle. Don't stick it in and forget to occasionally re-read -- to make sure your lead-in makes sense, the formatting is sane, that it doesn't now have information that you covered in another part of the page that uses the Include() macro, etc. So instead: The SSS is not: Overly stable: expect it to change throughout the release cycle, so if you Include() it, make sure to check that the meaning/format still works where you included it. ???