Search results

[ ] Emcee check session location is ready (IRC/other platform)

...e a kernel with realtime patches as found at PlanetCCRMA. Since this isn't ready for F14, this spin instead relies on reducing unwanted system and user serv <!-- When your spins page is completed and ready for review,

* Preparing to be ready at time

None needed - this is a new feature and can be safely deferred if it is not ready.

* '''TESTING/BATCHED''' - Your package is ready to go stable, and will wait until the next Tuesday's update batch to be mar * '''TESTING/STABLE''' - Your package is ready to go stable, and will wait until the next daily update push.

<!-- When your change proposal page is completed and ready for review and announcement -->

...long with the test case or package if its tagged as 'this is currently not ready to test' - Noriko

..."text" style="color: #407a40">kanarip: are you going to have the templates ready when we release it to mirrors?</td><td class="time">13:26</td></tr> ...7a40"> f13</th><td class="text" style="color: #407a40">again, it has to be ready at release time</td><td class="time">13:28</td></tr>

<!-- When your feature page is completed and ready for review -->

15:21 < warren> Perhaps let packagedb takeover owners.list if it becomes ready. 15:37 < mmcgrath> Smolt is up and ready, I've been adding some queries, breaking some things, this and that.

12:14 <@wwoods> mether: yes, but they aren't ready yet, and they'll need an upstream place to do development 12:16 < mether> if they are not ready for the distribution, are they ready enough for rawhide or fedora extras-devel

| application/pdf, application/x-pdf || .pdf || PDF || Documents ready for printing and viewing, held in the PostScript format in a compressed PDF

...got the big black usability box somehow. How do you put it together to get ready to run usability tests? Learn here!

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

This pre-planning should mean everything is ready and any major issues should have been shaken out before we "pull the trigge <!-- When your feature page is completed and ready for review -->

| <!-- subtask -->migrate to taskotron instead of tunir, when tasktron is ready (non-blocker) | <!-- status --> (Not ready / dropped)

15:00 < dgilmore> Everyone here and ready for the meeting? 15:29 < dgilmore> Legacy buildsys is setup and ready

* Not ready until 2010-07-12 * Not ready until 2010-07-23

...ule/ task schedule] for upcoming version, the release announcement must be ready to occur on release day. Work on the announcement can begin at any time but

...ke things easier [http://www.coolcomponents.co.uk/catalog/racer-p-993.html Ready made Bluetooth] cars for example

...riptions font packagers need to write, and upstreams do not always provide ready-to-use text snippets<ref>Or they do not provide them in English</ref>. Many

<!-- When your spins page is completed and ready for review,

<!-- When your change proposal page is completed and ready for review and announcement -->

...community rather than inside Red Hat. Note that !PackageKit is not quite ready to replace pup and pirut, but its design does address some issues with Fedo

...wnload website as a tool to create a live USB stick. If the new FMW is not ready at all to replace the old version, we can still keep linking the old versio ...t will be such a visible change that it should block a release if it's not ready.

<!-- When your feature page is completed and ready for review -->

* Upstream will also look at dropping individual features if they are not ready in time <!-- When your feature page is completed and ready for review -->

==== Be ready for Software Translation Deadline ==== ==== Be ready for System Wide Changes proposal deadline ====

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

When you are ready to burn the files or folders to disk click the ''Burn'' button.

<!-- When your change proposal page is completed and ready for review and announcement -->

schedules, Release Engineering will be ready to start scripted rebuilds

* The NetworkManager plasmoid isn't ready yet (it was scheduled for August).

Fedora has CLI packages ready to install for multiple cloud providers. Install any of these with `dnf ins

...CD labels and sleeves. At least a professional-printer (eg screenprinting) ready version of each needs to be made of the labels - 3 or 4 colors at most. An ...ith the websites and infrastructure teams to get a staging site set up and ready to go for the final release date.

Merge Fedora changes to upstream and make TigerVNC ready for Fedora

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...users, who do not have a good network (eg., Internet) connection at their ready disposal, to easily install new packages or update existing ones through th

This schedule is ready for [[Summer Coding 2010]]. Join the [http://lists.fedoraproject.org/mailm

...9/17: latest upstream fixes pushed into rawhide by agk; API not frozen but ready for use by applications

Oh no, its not ready for primetime yet. It's still very much an experimental fs that is under h '''Btrfs is not ready for widespread release yet. Is there a timeline for the project?'''

[[File:Anaconda Fedora31 Ready.png|frameless|Ready]]

<!-- When your spins page is completed and ready for review,

...ra-specific patches. (This work has already been completed locally and is ready for comitting). <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

...on on the new release, demos, speeches and, at last but not least, friends ready to answer all your questions.

**Deadline for items to be shipped and ready to hand out

...ucation_Spin | Education Spin]] || The purpose of this spin is to create a ready-to-go development environment for contributing to educational projects insi

<!-- When your feature page is completed and ready for review -->

## Code Ready Linux Builder (CRLB) * Red Hat Code Ready Linux Builder: https://developers.redhat.com/blog/2018/11/15/introducing-co

...ngency mechanism: not a System Wide Change, is the Frappe Framework is not ready for user we will point to the f24 release, unstable packages can be found [ <!-- When your change proposal page is completed and ready for review and announcement -->

...ted entry. Please be prepared to hear "no" if you are not considered to be ready. If you should not pass, you will have the chance to apply again.

* printable schedule - not ready yet * Android, Maemo, WebOS app/link - not ready yet

When you are ready to burn the files or folders to disk click the ''Burn'' button.

<!-- When your change proposal page is completed and ready for review and announcement --> * Other developers: Developers need to ensure that rawhide is stable and ready for the Fedora 36 branch.<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

* Now it's possible to work w/o external EPMD in production-ready applications <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

...d "dist-fc8" will be created when the buildsystem and CVS repositories are ready for Fedora 8 development to begin. The "dist-fc8" tag will inherit all of

Now you're ready to use this content for your new repository.

...e don't want to block the English release because not all translations are ready yet. Similar considerations apply to docs for specific Fedora versions. If

.... Supporting people immerse in Art, the Design Suite has many applications ready installed. For those needing IT forensics, the Security Spin will provide a

...t" style="color: #407a40">And that is to have as much of a prototype store ready by our December 5th meeting</td><td class="time"><a href="#t13:02" class="t ..." style="color: #97974f">maybe I could show you the fedora-fr store, quite ready to be opened on spreadshirt, so as to get an eye of what is doable</td><td

<!-- When your change proposal page is completed and ready for review and announcement -->

* '''Please note, this feature will not be ready in the F17 timeframe and will be move to the next release''' trusts to Acti <!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

If you are looking for ready-made presentations and ideas for talks, visit individual events pages, like

...preconfigured disk images with the operating system and required software ready to run on a selected virtualization platform. BoxGrinder converts simple pl

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

* Getting ready for mid-term evaluations. * Getting ready for the final evaluation.

<!-- When your feature page is completed and ready for review -->

minimal until the full set of packages is ready to land at once.

! Ready

schedules, Release Engineering will be ready to start scripted rebuilds

<!-- When your change proposal page is completed and ready for review and announcement --> ...dless authentication methods. This work is expected to land in Fedora once ready.

<!-- When your change proposal page is completed and ready for review and announcement -->

...alculator is [https://bugzilla.redhat.com/show_bug.cgi?id=1250082 not IPv6-ready] suggests we should deprecate ipcalculator and keep a single tool for the j ...alculator is [https://bugzilla.redhat.com/show_bug.cgi?id=1250082 not IPv6-ready] suggests we should deprecate ipcalculator and keep a single tool for the j

Once this is done Eclipse Fedorapackager is ready for use. Fire up Eclipse. Let's get started. Yay! The changes are ready to be pushed (or published) publicly when the locally committed changes are

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

and ready for free download, use, modification and redistribution.

schedules, Release Engineering will be ready to start scripted rebuilds

...rt up, even on reasonable hardware. We should be able to get from exec to ready to accept clients in under one second. X server shutdown should be similar

* code is all ready to go - plan is to have a test for f11alpha->f11beta upgrades

If it's not ready really it's just a matter of not announcing it. Aside from the initrd chan <!-- When your feature page is completed and ready for review -->

...n on the new release, demos, speeches and, at last, but not least, friends ready to answer all your questions.

<!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

...cal || [[User:Elad|Elad]]|| In stable repositories for Fedora 14 and 15 || Ready || [https://bugzilla.redhat.com/show_bug.cgi?id=697425 Review request] || Y * system-ready, ''plays when display manager starts''

<!-- When your spins page is completed and ready for review,

When the custom policy is ready, the product maintainer should create a build script (e.g. Makefile), attac When a Git repository with SELinux policy sources is ready, create your product .spec file (rpmbuild configuration file).

<!-- When your feature page is completed and ready for review -->

= Freeze after branching until compose is ready <!-- The name of your change proposal --> = ...is branched. This freeze will be removed as soon as a branched compose is ready.

<!-- When your change proposal page is completed and ready for review and announcement -->

[12:19] <spot> abadger1999: is Javascript ready?

<!-- When your feature page is completed and ready for review -->

CD ready to go.

<!-- When your feature page is completed and ready for review -->

...ar. When your splash screen (if you have one) disappears, your desktop is ready for use. You can now launch applications to access the Internet, manage fi

schedules, Release Engineering will be ready to start scripted rebuilds

...407a40" | We plan to meet again soon and discuss our work and see if we're ready to implement anything.

<!-- When your feature page is completed and ready for review -->

...a 14 has what you need. Thinking of coding in Python 3 down the road? Get ready now with Fedora's inclusion of '''Python 2.7''', which has increased effici ...f your CD drive - your hard drive won't be touched at all. And when you're ready, installation is just a click away.

schedules, Release Engineering will be ready to start scripted rebuilds

schedules, Release Engineering will be ready to start scripted rebuilds

.... Such packages can be submitted for review as per the regular process. Be ready to discuss why your package only applies to EPEL.

...o work with the design team to continue polishing their wallpaper so it is ready for final

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...ome polishing: I'll update the kickstart file and will - once it's somehow ready - submit it to the Spin SIG for technical approval.</td></tr> ...na</th><td class="text" colspan="2" style="color: #854685">sdziallas: lets ready for one week,</td></tr>

<!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

# Verify that empathy has Gtalk set up and ready to use <!-- When your feature page is completed and ready for review -->

* Better, production-ready [https://www.it.uu.se/research/group/hipe/index.shtml HiPE] support. <!-- When your change proposal page is completed and ready for review and announcement -->

schedules, Release Engineering will be ready to start scripted rebuilds

schedules, Release Engineering will be ready to start scripted rebuilds

...ix to co-ordinate with Thermostat test day runners to make sure they'll be ready or postpone the event'' - this was done, and the event went off fine * [[Test_Day:2013-05-28_Virtualization]] looked to be all ready

Media should now be ready to boot on the Banana Pi. Insert into the device and boot. Media should now be ready to boot on the Cubieboard. Insert into the device and boot.

...r the Fedora 19 "Schrödinger's Cat" beta release and confirmed it's alive! Ready to purr at the latest free and open source technology? Download it now: ...By bringing 3D printing tools into Fedora, you can get started with what's ready-to-go in the repositories without having to download binary blobs or run Py

The system gets closer to being IPv6-ready. While ping by itself is a minor tool, is a very popular tool for debugging <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

...Adamwill|Adamwill]] ([[User talk:Adamwill|talk]]) - release notes were not ready by RC time, no procedure in place to ensure they were built and submitted a

...t of studying). Once build, the image will be sent back to the main server ready for the user to download. The user will receive an email notification when

...ady to the Whiteboard field, indication that the review request is not yet ready, because of some issues they report. After you have addressed them, please ...elps other possible reviewers to notice that the review request is not yet ready for further review action.

<!-- When your feature page is completed and ready for review -->

...might not be finalized yet and the software itself might not be completely ready).

schedules, Release Engineering will be ready to start scripted rebuilds

Do not ship the result if not ready. Since the feature is not required for anything else in the system, there w <!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement --> ...tingency mechanism: (What to do? Who will do it?)<br>If the plugin is not ready in time, the other changes would preserve the status quo. So we can postpon

* [[Test_Day:2013-05-21_AnacondaNewUI_Followup]] looked ready or close to ready, and seemed to have some good test cases that could be adopted into the val ...ix to co-ordinate with Thermostat test day runners to make sure they'll be ready or postpone the event

* 2009-05-04 - Ready for use and modify.

* '''''still no full e2fsprogs support - will not be ready by GA, will update some time post-GA'''''

This draft is not ready, yet. It is currently be worked on by [[User:Till|Till Maas].

When you have the test ready, you have already chosen the right event for your test and configured it in ...one command after another. Still everything works ok? Then you test may be ready for publishing in AutoQA upstream, congratulations :)

That's it ! Your .iso should be built and ready to burn to DVD / CD... You might want to test it boots successfully using V

...remix and rework these files to help us get our Fedora 14 alpha wallpaper ready for 30-July-2010!

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

# If working in private space, copy over content when ready ...template in <code>example-tutorial</code> and write to the list when it is ready, so that a CVS admin can respond. Making a module includes creating a bugz

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...l tools and processes. Therefore, contingency plan is to slip until we're ready to upload full images of F12 and F13, whenever that happens to be.

...spot> should we revisit this one in a week, when overholt's got his script ready? [12:41] <overholt> it's not likely I'm going to have a script ready in a week. is it really a blocker?

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...k<code></code>Manager during the Fedora 8 release cycle the developers are ready to deliver some incredible new features, including ad-hoc networking, multi

<!-- When your feature page is completed and ready for review -->

...r components. If FeSCO or Wrangler think this does need a change page, I'm ready to drop it.] <!-- When your change proposal page is completed and ready for review and announcement -->

.... Such packages can be submitted for review as per the regular process. Be ready to discuss why your package only applies to EPEL.

15:06 < mmcgrath> Who's ready for a meeting? 15:22 < iWolf> Sounds like the old cvs-int box is ready to be rebuilt (still needs firmware updates on the hd's).

<!-- When your change proposal page is completed and ready for review and announcement -->

schedules, Release Engineering will be ready to start scripted rebuilds

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

* workable ibus-qt is ready ..." | tagoh3, I am working on ibus-qt. and the workable ibus-qt im module is ready

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

schedules, Release Engineering will be ready to start scripted rebuilds

Sep 12 14:11:15 <jnettlet> probably not ready yet, but I think conduit could really be a showcase service to include. ...I'm trying to use some time between test2 and f9 to get some other things ready for f9

If this feature is not ready by July 26, it can moved to a later Fedora version. If systemd is not LSB <!-- When your feature page is completed and ready for review -->

...in as a backup solution if it turns out the LVM DBus API is not production ready even for the installation use case. This results in a wonderful Contingency ...zime), make sure the LVM DBus daemon is packaged for Fedora and production ready for the installation use case (jbrassow)

<!-- When your feature page is completed and ready for review -->

...on on the new release, demos, speeches and, at last but not least, friends ready to answer all your questions.

<!-- When your feature page is completed and ready for review -->

By providing this software to them in a pre-packaged, ready to install Lab image, we hope to enable their work. This change provides computational neuroscientists with a ready-to-use Fedora based image to use in their work.

...that developer assigning the bug to him/herself). If they feel the bug is ready to be handled by a developer right away, they should try pinging the mainta

schedules, Release Engineering will be ready to start scripted rebuilds

<!-- When your feature page is completed and ready for review -->

...8c4a4a"> JonRob</th><td class="text" colspan="2" style="color: #8c4a4a">is ready to go this week</td></tr> ...td class="text" colspan="2" style="color: #8c4a4a">electronics lab is also ready to go :D</td></tr>

...able in gold. In theory the rest of the Fedora packages are already "gold ready".

...ng old ones, close really old ones, and move answered to meeting status if ready for discussion.</li>

...ld ideally rely on SSSD for most of its data storage needs. If SSSD is not ready or does not provide what we need, we can temporarily use our own data stora <!-- When your feature page is completed and ready for review -->

* otherwise we are really close to being ready to go

[12:19] <spot> ok. let us know when you're ready. [12:51] <spot> ill send an email to the mailing list when it is ready for everyone to fill in their "good times"

...ed up the process. Once this step is finished, your keys are complete and ready to use: Store the copy in a secure place, such as a locked container. Now you are ready to [[#ExportGNOME| make your public key available to others]] .

schedules, Release Engineering will be ready to start scripted rebuilds

* On a computer that's all ready running Fedora 12 you can do "yum groupinstall moblin-desktop"

* Have a USB image burning device ready

<!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

schedules, Release Engineering will be ready to start scripted rebuilds

schedules, Release Engineering will be ready to start scripted rebuilds

"validate-xml is all the checks, gets all the support files ready, etc., but does not build"

<!-- When your change proposal page is completed and ready for review and announcement -->

* TBD: Calendaring server should be packaged and ready to be added to Fedora 12.

<!-- When your spins page is completed and ready for review,

...lready undergone alot of work and community vetting and is pretty close to ready to ship in Fedora.

...thout Fedora claiming to be "Side-By-Side Capable", until all packages are ready. <!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

* Have a USB image burning device ready (Fedorator)

* If this feature is not ready by the deadline it will be included in the next Fedora release.

* Fedora 10 zero day updates are ready to go | style="color: #818144" | f13: all the torrent stuff is ready for the flip? do we have pre-seeders?

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

#* '''7.1-7.12'''<br/>Project is nearly complete. (90%)<br/>Ready for midterm evaluation. #* '''7.21-7.31'''<br/>The preparation of the documents.<br/>Remove bugs and ready for release.

...ver || || needed to enable evdev. Fedora disables it because evdev wasn't ready for F9. It may be in F10. - August 12, 2008

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

schedules, Release Engineering will be ready to start scripted rebuilds

- Remove the x86-64 tickless patches, they aren't ready.

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...s/builds go to testing, and the maintainer has a thing to say "ok, this is ready to push out as an update now" ...minor bugfix, version update, etc... and would be able to decide when it's ready to push... or use some default days or something.

<!-- When your feature page is completed and ready for review -->

..._Day:2012-04-17_JBoss_Application_Server|JBoss Test Day 2012-04-17]] looks ready to go ...st_Day:2012-04-19_Gnome_Boxes|GNOME Boxes Test Day 2012-04-19]] page looks ready but status of Boxes itself was uncertain: tflink to check with the maintain

No contingency plan necessary. If it's not ready, the feature can be removed from the documentation until a future release. <!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

<!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

#* '''7.1-7.12'''<br/>Project is nearly complete. (90%)<br/>Ready for midterm evaluation. #* '''7.21-7.31'''<br/>The preparation of the documents.<br/>Remove bugs and ready for release.

<!-- When your feature page is completed and ready for review -->

Once you've filled in all the forms, click on the "Ready to Publish" button to submit the article to the editing process.

...itative on our ambassadors. Event wiki pages and event information must be ready prior to the meeting voting. If you do not have your information posted on

** being ready/having the capacity to help out users with migration of their custom legacy ...one, so you can get on with other work and pick up the results when you're ready.

CD ready to go.

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

* If this feature is not ready by the deadline it will be included in the next Fedora release.

<!-- When your feature page is completed and ready for review -->

If it is not ready, it will go into Fedora 27.

The parts of OpenStack that are ready will be included in Fedora. There is no special contingency plan required.

<!-- When your change proposal page is completed and ready for review and announcement -->

If this is not ready in time, we can just push out that date at which we consider GFS2 stable. T <!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

...ing on cvs.fedora.redhat.com, and Sopwith has time to do some QA, it'll be ready |fedora.redhat.com in public CVS||GregDeKoenigsberg||17 Mar||Checked in and ready to go

It can also be used for applications or services which aren't ready to be official or up to the standards of Fedora Infrastructure.

before it's ready for Fedora 9, or are you quite happy with its current

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

..., organize and have a ready swag package (either digital/physical or both) ready for this already planned activities. ...need for: social media templates for advertisement of the events, posters, ready to go slide deck, suggestions for swag, and also a “how to” to get enab

=== Version 2.0.0 - ready for the future === This new release has been made truly ready for the future, with a move to [https://github.com/rdiff-backup GitHub], Py

...scheduled magazine posts announcing the sessions (ideally, these should be ready and scheduled in the preparation period).

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...the WEB GUI based installation process. After this, the YOURLS instance is ready for business - you can access the API at http://localhost/report/yourls-api

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

If test suites are not ready for the target release, NetworkManager will be used just as it was used bef

<!-- When your feature page is completed and ready for review -->

with [[Features/Python3F13#Python_3_already_in_Fedora|many more built and ready for Fedora 14]] ==== Python modules that appear to not yet be ready for Python 3 packaging ====

<!-- When your feature page is completed and ready for review -->

When stage4 is ready and matching exactly for both architectures, the koji build can then start.

* Not ready--scheduled for availability on 2008-04-11 * Toshio says that the tools (pkgdb, etc..) are ready for the mass branching.

I think this is ready for review by the gurus as I have gone about as far as I can.

#* '''7.1-7.12'''<br/>Project is nearly complete. (90%)<br/>Ready for midterm evaluation. #* '''7.21-7.31'''<br/>The preparation of the documents.<br/>Remove bugs and ready for release.

All extensions compatible with PHP 7.0 are ready for PHP 7.1 <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

...of the work for them. With the Database Server in place, users will have a ready to use datastore without lengthy configuration. <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

<!-- When your feature page is completed and ready for review -->

{{Admon/caution | Section is ready for conversion to XML}} {{Admon/warning | Section is ready for conversion to XML}}

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

The event schedule will be published here once it is ready.

schedules, Release Engineering will be ready to start scripted rebuilds

* 2018-10-10: '''RC3''': changes are ready in the [https://src.fedoraproject.org/rpms/php/commits/private-php73 privat <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your spins page is completed and ready for review,

...">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;because if it does i'll have samples ready by tomorrow</td><td class="time"><a href="#tApr 08 23:23:38" class="time">A ...="color: #407a40">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;next topic... are we ready for specific spins yet?</td><td class="time"><a href="#tApr 08 23:48:11" cl

<!-- When your feature page is completed and ready for review -->

# When your package is ready to submit for review, select '''File''' > '''Export''' from the main munu, == Ready to Ship ==

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

...Distribution Project]] that aims to distribute Updated Fedora Media (USB-Ready Installable Images) for free to individuals who can't afford to buy or down

<!-- When your change proposal page is completed and ready for review and announcement --> ...ode changes are mostly done and the integration changes are mostly already ready as bootupd has already been integrated in a similar fashion in Fedora CoreO

| Needs Review || Package is ready for review

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your spins page is completed and ready for review,

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...d send an email to the fedora-infrastructure-list explaining the ticket is ready. These discussions should happen in public. The submitter IS accountable

<!-- When your change proposal page is completed and ready for review and announcement -->

...s are required. These developers need to ensure that rawhide is stable and ready for the Fedora 22 branch. Given that glibc is backwards compatible and we h <!-- When your change proposal page is completed and ready for review and announcement -->

| style="color: #8c4a4a" | we woint import epel into koji until we are ready to switch ...rik: im in favour of having maintainers push to stable when they think its ready

-- :status: Is the package ready to be built, in review, or other?

== Once ready, move into Fedora proper == Ready can differ. For 3.7 it was when rc1 was released and all important stuff fr

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

When you're ready, go ahead and remove or hide (click on the eyeball icon to hide the layer)

...sensus from the Design team on whether or not the artwork was considered ''ready'' or not

...branching until compose is ready | Freeze after branching until compose is ready]]=== ...is branched. This freeze will be removed as soon as a branched compose is ready.

...p control applet. Specifically, the necessary QT-DBUS bindings are not yet ready. QT-DBUS bindings are currently expected to be available as part of KDE 4.0

[12:39] * spot will happily review the draft when its ready

** Code changes are ready. Merging is in progress.

== Packages ready to submit == Packages ready to submit in total: 39

...remental. The new user interface has already landed. If LVM support is not ready in time, we can just <!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

...remix and rework these files to help us get our Fedora 14 alpha wallpaper ready for 30-July-2010!'''

<!-- When your change proposal page is completed and ready for review and announcement --> To review and accept the PR when ready.

** Status: 120 color copies made, and ready to be packed. All set.

In order to keep track of which updates have been tested (and are therefore ready to be pushed to the wider Fedora community) and which ones have not been tr

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

15:28 < iWolf> I'm thte slow one, as I can get stuff ready to go even before the firmware is updated. 15:33 < abadger1999> That won't affect us until we're ready to upgrade past RHEL5, thoug,h, unles I'm missing something?

Media should now be ready to boot on the Banana Pi. Insert into the device and boot. Media should now be ready to boot on the Cubietruck. Insert into the device and boot.

* when we're ready we need some way of redirecting people from: fedorahosted.org/projectname/s

...pdates out of the Base branches, but they should be merged in when they're ready, not blasted in from the firehose. ...pdates out of the Base branches, but they should be merged in when they're ready, not blasted in from the firehose. (sgallagh)

<!-- When your feature page is completed and ready for review -->

==== Be ready for System Wide Changes proposal deadline ==== We'll have to be ready by then. Which mean ask the community to confirm the move, and projects to

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

schedules, Release Engineering will be ready to start scripted rebuilds

When you feel the page is ready, announce it to the Fedora community and solicit feedback. We suggest the f

...required. These three developers need to ensure that rawhide is stable and ready for the Fedora 21 branch and then rebase Fedora 21 using the official glibc <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

...lspan="2" style="color: #818144">if its related to C++&nbsp;&nbsp;iam ever-ready ;)</td></tr>

October video demo of tools ready for post-Fedora-23 release: https://www.youtube.com/watch?v=r1jrqClho3U ...azine.org/using-tunir-test-fedora-cloud-images/ tunir] if Taskotron is not ready; the goal is to migrate to Tasktron when possible)

This change brings Boost 1.55.0 (as, Boost 1.56.0 was not ready in time) to Fedora 21.

Mark your calendars, and get ready to break out and have some fun: Fedora 14 will launch in early November. Fe

We will coordinate the work in a side tag and merge when ready. ...from {{package|python3}} in Fedora 28 (or 29 before this change) (package ready in git, will arrive on mass rebuild)

...ake on '''Dep Chain (#7)''' first. We have a perfect store for this data, ready to be filled: [https://pdc.fedoraproject.org PDC, the product-definition ce

...add the link to overall results chart., and an assessment if the image is ready.

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

*Copy [http://tekkamanninja.fedorapeople.org/boards/cubieboard/images/ the ready-made Fedora Remix image] and [http://tekkamanninja.fedorapeople.org/boards/ The SD card is ready. Now let’s prepare the Cubie!

<!-- When your feature page is completed and ready for review -->

* Contingency mechanism: If it looks like we won't have this ready in time for F26, we can simply kill it. <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement --> * Prepare a Linux Client Workstation ready to mount NFS share

...ked Date''' || '''Migration Date''' || '''Location''' || '''Notes''' || '''Ready to translate?'''

...so that we can print them right away. We are working on these and will be ready to go soon. AlexMaier will keep posted.

# After initialization: The new added builder's status should be ready in the list. *NOTICE:* builder won't ready until free space on /var/lib/mock is greater than 8GiB, and /var/lib/mock o

* Proposal owners: upstream the change is nearly ready to be committed to the master branch and a beta released. If the beta is re <!-- When your change proposal page is completed and ready for review and announcement -->

''When a feature is complete and ready for developer testing'', merge that branch to the ''devel'' branch. Refere

** If the vboxsf kernel driver is not yet ready we can ship with VirtualBox guest integration without shared-folder support

...a 14 has what you need. Thinking of coding in Python 3 down the road? Get ready now with Fedora's inclusion of '''Python 2.7''', which has increased effici ...f your CD drive - your hard drive won't be touched at all. And when you're ready, installation is just a click away.

Next let's get this into a file format ready for printing. ...'ve gone through all that, time to hit "Save." You should now have a print-ready PDF!

<!-- When your feature page is completed and ready for review -->

|Package is submitted for review and ready to be reviewed. Feel free to pick this package and do the review. <!-- When your feature page is completed and ready for review -->

...of a Modular Fedora Server that is actually usable. However, as we aren't ready for production yet, we would like to do a "preview" release so that people ...content we plan to release, even a small percentage of that content being ready will be enough to help prove the concept and generate feedback.

...ionKit|USB Stick Creation Kit]] || $5 || Under Construction || Should be ready by [[FedoraEvents/FOSDEM/FOSDEM2009|FOSDEM 2009]] along with EventBox EMEA

* Contingency mechanism: Feature will be deferred to Fedora 24 if it is not ready in time. <!-- When your change proposal page is completed and ready for review and announcement -->

...of cloud-native technologies, it's clear that the design world is at last ready to ...Neal Gompa's collaborative work with the Red Hat team has made our images ready for both without modification. Aarch64 is UEFI only.

<!-- When your change proposal page is completed and ready for review and announcement -->

...t></font></th><td width="100%" bgcolor="#eeeeee"><tt><font color="#407a40">ready for the N&amp;S A meeting?</font></tt></td></tr> ...488888">And since I'm coming to FISL, I want to make sure that everyone is ready.&nbsp;&nbsp;:)</font></tt></td></tr>

...al deployment and after recent rains is not available, but plan to have it ready in order to coordinate it with a LUG presentation about F10 features) | style="color: #9b519b" colspan="2" | will post on list when everything is ready, both at lug and with mirroring

<!-- When your change proposal page is completed and ready for review and announcement -->

...g well; schedule is almost finished; schwag is delivered; we're just about ready to go.

* OCaml guidelines; draft not yet ready for a vote: http://fedoraproject.org/wiki/PackagingDrafts/OCaml [12:34] <spot> i don't think the Ocaml draft is ready yet...

...questions are not clearly answered, don't send the email yet. You're not ready. Remember, be specific about what type of work you're looking to do. Sayi ...to ask for help without being annoying will show that you are serious and ready to contribute. Don't send this kind of message more than once every couple

.../th><td class="text" style="color: #407a40">so hopefully we'll have enough ready to go tomorrow</td><td class="time">13:08</td></tr> ...th><td class="text" style="color: #488888">f13: so, do we have the scripts ready to start the automated buildatron?</td><td class="time">13:35</td></tr>

[[File:Anaconda_Fedora32_Ready.png|frameless|Ready]]

...hen they are ready to submit the Change proposal, they set the status to "Ready for Wrangler". ...tatus back to "New" and inform the Change Owner of what's needed. If it is ready to process, then...

<!-- When your change proposal page is completed and ready for review and announcement -->

The most notable Wayland-ready toolkits are: ...ely this toolkit. Please note that apps using older GTK+ 2 are not Wayland-ready.

Media should now be ready to boot on the Cubietruck. Insert into the device and boot. Media should now be ready to boot on the BeagleBone. Insert into the device and boot.

I like the idea of open-source. I'm ready to try and learn new things and make use of what I learned until now.

* Contingency mechanism: Move implementation to next release (once ready and if possible, backport to old release) <!-- When your change proposal page is completed and ready for review and announcement -->

Since this is brand new functionality, if it isn't ready in time, nothing has changed. We just drop this feature page. <!-- When your feature page is completed and ready for review -->

21. I am very ambitious and I am ready to do whatever it takes to reach my goals.<br>

=== Fedora 13 User Guide Ready for Translation === The User Guide for Fedora 13 is currently ready for translation and submissions can be made to the 'f13' branch on translat

* Proposal owners: The RPM code base needs to get stabilized and release ready. The release candidates need to be tested in rawhide.

<!-- When your feature page is completed and ready for review -->

...stuff will be hidden by macros, we'll just need a rebuild once things are ready. [12:57] <spot> are we ready for a vote here? :)

<!-- When your feature page is completed and ready for review -->

| colspan="2" | * jskladan is ready to rock'n'roll | style="color: #818144" | we want to have it ready before F17 test cycle, somewhat middle Jan

<!-- When your change proposal page is completed and ready for review and announcement -->

...al years. While like most software it still has some bugs, we believe it’s ready to serve as a default that works for many users. ...s some of the most exciting changes, as we build more cloud- and container-ready tools into Fedora to create a fantastic developer platform. While Fedora 25

When your theme's wiki page is ready, send a proposal to [http://www.redhat.com/mailman/listinfo/fedora-art-list

<!-- When your feature page is completed and ready for review -->

...y that I have significantly tested along with others is Xfce. It should be ready to go ...0" | and are they ready for us to review/vote? (essentially would they be ready for FESCo if they were other features)

smoothed out and other parts of the puzzle are ready, we will merge Fedora 6 content

| style="color: #818144" colspan="2" | Fedora EMEA e.V. is ready to GO!

...leaf package affecting no other part of the system. If Review Board is not ready in time (unlikely; upstream indicates a final release to be coming within t <!-- When your change proposal page is completed and ready for review and announcement -->

...pers/HouseKeeping/Fedora11]] - poelcat will get the requests and templates ready for the "Mass Change Specification" with assistance from arxs , generating ...a month away from release day so it is time to start getting the requests ready

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

* Contingency mechanism: Feature will be deferred to Fedora 24 if it is not ready in time. <!-- When your change proposal page is completed and ready for review and announcement -->

...ade to provide a first [https://pagure.io/lxqt-remix impression] and it is ready for submission as an official spin.

May 24 15:11:30 fabian_a almost everything is ready for linuxtag...there were some changes at the fudcon schedule

...ackward compatibility. Most of the issues are resolved now and patches are ready for inclusion. This update adds around 8000 supported characters in Glibc, <!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

Failure of this feature to be ready for {{FedoraVersion|long|next}} only means that this feature will not be av <!-- When your feature page is completed and ready for review -->

...g is the really compelling aspect of this feature, and that part isn't yet ready. It works on various small examples, but there are plenty of examples of r <!-- When your feature page is completed and ready for review -->

Week 11: Getting it ready for reviews

* Proposal owners: Authselect is already ready and shipped with Fedora. Owners will provide compatibility tool to help wit <!-- When your change proposal page is completed and ready for review and announcement -->

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

<!-- When your feature page is completed and ready for review -->

| 2 || F16, how to get it ready to write and test your PHP web apps || Installing and configuring LAMP corr

<!-- When your change proposal page is completed and ready for review and announcement -->

schedules, Release Engineering will be ready to start scripted rebuilds

<!-- When your feature page is completed and ready for review -->

0:04 < thl> | abadger1999, any expected timeframe when it might be ready? 0:09 < thl> | I think this topic is mostly ready; I'll remove it from the schedule

But having the patches ready before the mass rebuild would help a lot with finding any issues. <!-- When your change proposal page is completed and ready for review and announcement -->

...2. In the unlikely event that the NSS and PAM portions of the SSSD are not ready for Fedora 11, they can be omitted with no harm to the release. <!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

# After initialization: The new added builder's status should be ready in the list. *NOTICE:* builder won't ready until free space on /var/lib/mock is greater than 8GiB, and /var/lib/mock o

<!-- When your feature page is completed and ready for review -->

15:00 < mmcgrath> Alllrighty, Who's ready for a meeting?

needed for rebases. When testing shows that this tree is ready, the

<!-- When your change proposal page is completed and ready for review and announcement -->

If version 4.0 is not ready in time for Fedora 19 but packaging is satisfactory, we can ship version 3. <!-- When your feature page is completed and ready for review -->

3. When a ticket is ready for discussion, add the 'meeting' keyword.

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

<!-- When your feature page is completed and ready for review -->

...cked with fantastic free and open source software, lovingly configured and ready to use.

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

* Upstream is not ready for the secureboot related changes yet. So we will have to carry all the pa <!-- When your change proposal page is completed and ready for review and announcement -->

...s are required. These developers need to ensure that rawhide is stable and ready for the Fedora 23 branch. Given that glibc is backwards compatible and we h <!-- When your change proposal page is completed and ready for review and announcement -->

...s are required. These developers need to ensure that rawhide is stable and ready for the Fedora 24 branch. Given that glibc is backwards compatible and we h <!-- When your change proposal page is completed and ready for review and announcement -->

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

== Fedora 16 Alpha RC4 ready-ness == | style="color: #407a40" | #topic Fedora 16 Alpha RC4 ready-ness

<!-- When your change proposal page is completed and ready for review and announcement -->

When the Fedora Infrastructure Team notifies you that your hosting space is ready, create the local and remote git repositories for your guide.

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

* Once you are all setup and ready to go drop by and say hello on {{fpchat|#fedora-bugzappers}}

...dora ARM Team is pleased to announce the release of Fedora 23 for AArch64, ready to run on your next generation servers. Fedora 23 is a game-changer for the

<!-- When your feature page is completed and ready for review -->

...ry /sys/kernel/debug/usb/usbmon/ has files in it, kernel support should be ready.

...the famsco list and will post our draft to the ambassadors list when it's ready.

...dora.next ideas (like including non-RPM packages directly) — but we're not ready for that now.}}

14:59 < rvokal_> so he gets that ready at the time we come

...f new and improved features to support cloud computing, including a "cloud ready" version of '''GlusterFS''', including additional auth*/crypto/multi-tenanc

<!-- When your feature page is completed and ready for review -->

...mmcgrath> Yeah. I'll have to check with stacy and mgalgoci. I think its ready. 15:15 < iWolf> mmcgrath: just let me know when it's ready and I can get started on it (hardware for db2)

<!-- When your feature page is completed and ready for review -->

* [[Test_Day:2013-05-07_ABRT]] looks ready to go, we just need to do some announcing * kparal to ensure abrt and sssd test days have live images ready

<!-- When your feature page is completed and ready for review -->

...waiting for management approval of the public demo, everything is lined up ready to go | style="color: #488888" | everything is set up and ready to go otherwise

<!-- When your feature page is completed and ready for review -->

...always try to have GlusterFS as a guide in the project I participate and I ready to do what will be need to get everything done in time since I will be cont

<!-- When your spins page is completed and ready for review,

...have a new option for trying and installing Fedora. Astronomers will get a ready-to-work installation.

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your spins page is completed and ready for review,

...tainers to be able to profit from this change (after the implementation is ready) <!-- When your change proposal page is completed and ready for review and announcement -->

...virt to work in F11, but the GUI for managing the environment might not be ready.

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your change proposal page is completed and ready for review and announcement -->

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

'''How's the work going on getting this ready to be easily available for Fedora 9? '''

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

...ill give us some accountability, and a greater sense if a feature won't be ready in time.</td></tr> ...bsp;accountability is something we don't have now.&nbsp;&nbsp;The sense of ready on time, though, feeds into "have a list of features at freeze time"</td></

<!-- When your change proposal page is completed and ready for review and announcement -->

...ry associate with them. Each one has a single repository that is marked as READY in the database, and those that were created earlier (chronologically) are

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

<!-- When your feature page is completed and ready for review -->

<!-- When your change proposal page is completed and ready for review and announcement -->

...s are required. These developers need to ensure that rawhide is stable and ready for the Fedora 24 branch. Given that glibc is backwards compatible and we h <!-- When your change proposal page is completed and ready for review and announcement -->

...easier access to a PowerPC VM for debugging build issues. Once we have it ready, we will update this section.

...y be good to assure that latest version of icaro and turtle art plugin are ready to install. Documentation may be good to help us with a good starting struc

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

<!-- When your change proposal page is completed and ready for review and announcement -->

We're always ready to improve our translation processes and guides. If you have any suggestio

...the link to overall results chart above, and an assessment if the image is ready. Please include the categories at the bottom of the page.

...I got boots when the CMSCONFFILE wasn't read because CMSDASD device wasn't ready ("could not set device online" error message)

<!-- When your change proposal page is completed and ready for review and announcement -->

<!-- When your feature page is completed and ready for review -->