Search results

*** Tasks for the Spins SIG attached to each milestone ** Renaming the incomplete-spins category?

== Discussion of Custom Spins == ...anged the topic of #fedora-meeting to: Fedora Release Engineering - Making releases a snap</td><td>13:11</td></tr>

...ground: #407a40"> f13</th><td class="text" style="color: #407a40">previous releases we just pinged maintainers- for name suggestions with link explenation</td> ...style="color: #818144">feature freeze is for the stuff that makes it onto spins?</td><td class="time"><a href="#t13:20" class="time">13:20</a></td></tr>

* Targeted release: [[Releases/13| Fedora 13]] ...will share upload credentials with Fedora kernel developers (Oxf13, 21:08:39)

...> notting</th><td class="text" style="color: #8c4a4a">jeremy: technically, spins aren't on the mirrors</td><td class="time">13:16</td></tr> .../th><td class="text" style="color: #4b904b">notting: given that all of the spins are live images, jigdo is irrelevant for them, so ... :)</td><td class="tim

* nirik and dgilmore will be proposing a new policy for deciding which spins to ship for F20 * With the new [[Changes]] policy, the F20 'feature list' is [[Releases/20/ChangeSet]]

== Spins == * http://fedoraproject.org/wiki/SIGs/Spins/SpinSubmissionProcess

* Targeted release: [[Releases/39 | Fedora Linux 39 ]] ...software we generate be improved? How will the process of creating Fedora releases be improved?

* pub/linux/fedora/releases/releases.list * Discussion about what releases need to be kept around and which ones can be deleted to free up space

|- id="t15:11:39" || [[#t15:11:39|15:11]]

Update the Fedora 39 GNU Toolchain to gcc 13.2, binutils 2.40, glibc 2.38 and gdb 13.2. The set of core GNU Toolchain packages for Fedora 39 are as follows:

|- id="t15:13:39" || [[#t15:13:39|15:13]]

...d class="text" style="color: #818144">notting: well, shooting for thursday releases in general gives us that, but when we slip, we should just slip a week rath ...>i seem to recall those being the same reasons for not doing early torrent releases</td><td class="time"><a href="#t13:18" class="time">13:18</a></td></tr>

== Spins == * Release Engineering is expected to produce custom spins for F8

...88"> warren</th><td class="text" style="color: #488888">we doing the same "spins" as F7 itself?</td><td class="time"><a href="#t13:06" class="time">13:06</a ...ass="action" colspan="2">* poelcat we were only using "devel" for all test releases</td><td><a href="#t13:24" class="time">13:24</a></td></tr>

* Targeted release: [[Releases/41 | Fedora 41 ]] ...software we generate be improved? How will the process of creating Fedora releases be improved?

|- id="t15:02:39" || [[#t15:02:39|15:02]]

* Some discussion of whether preupgrade bugs should block media spins: adam to propose changes on the list |- id="t15:05:39"

...release: [https://docs.fedoraproject.org/en-US/releases/f39/ Fedora Linux 39] ...to manage what font packages should be installed for a Fedora release and spins, such as comps, langpacks, lorax, workstation-ostree-config, and fedora-kic

{{Release_validation_instructions|testtype=Installation|release=39|milestone=Rawhide|compose=|date=20230708.n.0}} ...|Milestone !! Test Case !! Everything !! Server !! Workstation !! Cloud !! Spins !! Labs