tagging of non critical path package into F-12?

[Josh Boyer]

On Thu, Oct 15, 2009 at 08:59:13AM +0100, Peter Robinson wrote:
>On Thu, Oct 15, 2009 at 8:55 AM, Conrad Meyer <cemeyer at u.washington.edu> wrote:
>> On Thursday 15 October 2009 12:51:28 am Peter Robinson wrote:
>>> Hi All,
>>>
>>> I presume that the reason that tagging requests aren't being done is
>>> due to the upcoming beta but is there a reason that non core or
>>> critical path packages can't be tagged in. I have a number of Moblin
>>> packages that fix various issues, in particular a rebuild of
>>> network-manager-netbook to fix networking against the latest NM build
>>> that hit just before the cut off. Given that none of these packages
>>> would be anywhere near any of the official spins is there any
>>> particular reason they can't be tagged in? Or if not when will they be
>>> reviewed?
>>>
>>> Peter
>>
>> Hi,
>>
>> If they're not on any of the official spins, what benefit does tagging them
>> into dist-f12 provide over having them as updates? (Pushing updates is the
>> suggested approach unless there's some reason it won't work in your case.)
>
>Because it allows me to test them as part of what will become the F-12
>Moblin remix spin and allows others to test them rather than me having
>to setup a separate repository so I can test how the interact with the
>rest of the Moblin packages in Fedora.

We're at RC2 of the Beta spin and not really tagging anything until Beta is
out the door.  After that, tag requests will pick back up so things can be
included in the final release.

josh