Search results

== Talking Points on Specific Topics == ...king points on things beyond the current release. We should curate talking points for other topics so that Ambassadors and other folks in Marketing have easy

#REDIRECT [[Releases/9/SingleSourceSummary#Release Talking Points]]

...quickly present an overview of highlighted features when talking about the release. ...nts are based in part on the [[Releases/18/FeatureList|features]] for this release. Any Fedora community member can introduce a feature, using our [[Features

...se. For information on how these talking points were chosen, see [[Talking Points SOP]]. They are intended to * help [[Marketing]] create release announcements and press releases.

...is taking a more in-depth look at several of the features in the upcoming release. See the [https://fedorahosted.org/marketing-team/ticket/73 associated Trac ...ther interviews are welcomed / encouraged to highlight more of the talking points.

...quickly present an overview of highlighted features when talking about the release. In this case, the feature page is not the Fedora Features, but Upstream KD The Social Desktop technology introduced in the previous release has been improved with a central identity management and introduces libatti

...al, meaning they take a fun approach rather than a typically serious press release approach. ...st sense for the local community. This is a truly localized version of the release announcement for Fedora.

* [[Fedora 12 Talking Points]] * [[F12 release slogan]]

''Include an early link to the release notes:'' http://docs.fedoraproject.org/release-notes/f10

=== Prominent announcement in the Release Notes, talking points, marketings === Having testing and contingency plans helps make a quality release. Need feedback from QA about whether this has been helpful in getting test

This schedule depends on [[Releases/Schedule|Fedora general release schedule]]. ...release, this schedule should be copied over to a page named '''Marketing $RELEASE schedule''' to work with.

...ocess followed by the Marketing team to make a talking points for a Fedora release. If you have suggestions on how to improve these instructions, please edit === Talking Points ===

|Cycle the wiki pages to the new release |List potential talking points and feature profiles

...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/30/ChangeSet|Change Set]] for this release.

= Licensing Talking Points That Have Occurred To Me = * When I get the scope of what the Red Hat plan for document release is, I'll be able to use this phrase to indicate that I know what is going o

[https://fedoraproject.org/wiki/Fedora_27_talking_points Talking Points] [https://fedoramagazine.org/Announcing-the-release-of-Fedora-27/ Release Announce]

.../2010-08-03/fedora-meeting-1.2010-08-03-20.00.html weekly meeting, talking points work] ...g/2010-05-17/fedora-mktg.2010-05-17-15.07.log.html history of the one-page release notes deliverable]

...ra Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use them. # to capture PNGs which ''touch'' upon the [[Fedora 16 talking points]] as well as

...ra Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use them. # to capture PNGs which ''touch'' upon the [[Fedora 13 Talking Points]] as well as

...ra Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use them. # to capture PNGs which ''touch'' upon the [[Fedora 15 talking points]] as well as

...do ''not'' have to center around release-specific Feature List or Talking Points items. * And of course, Feature List / Talking Points owners

...ailed look at several [[Releases/11/FeatureList|features]] in the upcoming release. # Make sure that the feature is reflected on the [[F11_Talking_Points|talking points]].

...quickly present an overview of highlighted features when talking about the release. ...nts are based in part on the [[Releases/16/FeatureList|features]] for this release. Any Fedora community member can introduce a feature, using our [[Features

...ra Releases should be (if possible) ready-made 1-2 weeks before the actual Release date so that journalists can use them. # to capture PNGs which ''touch'' upon the [[Fedora 14 talking points]] as well as

...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/29/ChangeSet|Change Set]] for this release.

...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/31/ChangeSet|Change Set]] for this release.

= FEL Talking Points = ...dience Targetted|This wiki page is meant to provide press kits and talking points about Fedora Electronic Lab.}}

= Release Readiness Status = ...d to self-add. The Fedora Program Manager will reset this page before each release and send email reminders to the people listed.

** Talking Points ...interested parties to go through the list and choose 3-5 for showcasing at release. contact [[user:rrix]] for details. (sorry I can't be there)

...ora Marketing. We go through several successive phases during each 6-month release cycle, and every phase has different milestones and tasks that you can help * [[Marketing#Release_deliverables|Talking points]]

| style="color: #407a40" colspan="2" | 2. Release Parties updates | style="color: #407a40" colspan="2" | 2. Release Parties updates

** [https://pagure.io/i18n/issue/70 #70: Fedora 25 talking points] ** [https://pagure.io/i18n/issue/63 #63: Bug triaging activity post F24 Beta release]

...a Marketing. We go through several successive phases during each six-month release cycle, and every phase has different milestones and tasks that you can help ...tasks for the next upcoming Fedora launch. | Help us have another awesome release, by picking up tasks and handling them in our [https://pagure.io/fedora-mar

= Fedora 26 Release Party in Coimbatore, India = We will be organizing a Fedora 27 Release Party Event at Amrita School of Engineering, Coimbatore. The aim of this ev

* Reminder from Karsten - Release Announcements Talking Points (https://www.redhat.com/archives/fedora-ambassadors-list/2007-May/msg00129. May 24 15:17:37 tchung Reminder from Karsten - Release Announcements Talking Points

** [https://pagure.io/i18n/issue/49 #49: Internationalization talking points for Fedora 22] |release=22

...ps://pagure.io/i18n/issue/70 #70: Adding i18n feature in Fedora 25 Talking points] ** [https://pagure.io/i18n/issue/63 #63: Bug triaging activity post F24 Beta release]

** [https://pagure.io/i18n/issue/49 #49: Internationalization talking points for Fedora 22] |release=23

* [[Marketing#Release deliverables]] ...know is that there are resources that may be helpful to have at hand when release time comes. These resources will help inform the public and the press.

...time of this draft. ''Please do a reality check before using these talking points as anything other tnan a discussion draft!''}} ...features when talking about the release, and to help drive content for the release, etc.

| style="color: #407a40" colspan="2" | 1. Budget and Release Events status | style="color: #42427e" colspan="2" | should i send email to all the release party owners asking for their paypal information?

* [[Marketing#Release deliverables]] ...know is that there are resources that may be helpful to have at hand when release time comes. These resources will help inform the public and the press.

...came from FedoraBounties, "Publication of all man and info pages for each release". There is also a GSoC 2007 project based on the same idea, but with differ Some basic points here, I'll add more details as the project goes on. I have reserved 13 week

= Fedora 37 Release Party in Thessaloniki, Greece= ...'ll be running down some of the new and cool features of the new Fedora 37 release. It will also serve as an opportunity for people to find out what Fedora an

...time of this draft. ''Please do a reality check before using these talking points as anything other tnan a discussion draft!''}} ...features when talking about the release, and to help drive content for the release, etc.

= Fedora 13 Release Party - Tokyo, Japan = * Talking about Fedora 13.

...time of this draft. ''Please do a reality check before using these talking points as anything other than a discussion draft!''}} ...features when talking about the release, and to help drive content for the release, etc.

...time of this draft. ''Please do a reality check before using these talking points as anything other than a discussion draft!''}} ...features when talking about the release, and to help drive content for the release, etc.

= Fedora 29 Release Party in Christ University, India= ...'ll be running down some of the new and cool features of the new Fedora 29 release. It will also serve as an opportunity for people to find out what Fedora an

= Fedora 29 Release Party in Bangalore, India= ...'ll be running down some of the new and cool features of the new Fedora 29 release. It will also serve as an opportunity for people to find out what Fedora an

...describes how to write a final announcement for a Fedora operating system release. ...or to release. It should be complete by a week before the operating system release.

= Fedora 28 Release Party in Bangalore, India= ...'ll be running down some of the new and cool features of the new Fedora 28 release. It will also serve as an opportunity for people to find out what Fedora an

* A series of talking points to address different parts of the python community # Develop sets of talking points for each sub-community.

=== Create the feature profiles page for the current release === ...named '''F(number) feature profiles''' where (number) is the number of the release under development. For instance, [[F13 feature profiles]].

Fedora развивается на основе [[time-based release schedule|графика выхода новых версий на осно� ...tasks for the next upcoming Fedora launch. | Help us have another awesome release, by picking up tasks and handling them in our [https://fedorahosted.org/mar

** [https://pagure.io/i18n/issue/49 #49: Internationalization talking points for Fedora 22] |release=23

** [https://pagure.io/i18n/issue/49 #49: Internationalization talking points for Fedora 22] |release=23

..." that needs to be described. In some cases, a feature is part of a multi-release arc of work, and that context can be useful to provide. [[Category:Marketing]][[Category:F11]][[Category:Talking points]]

...time of this draft. ''Please do a reality check before using these talking points as anything other than a discussion draft!''}} ...features when talking about the release, and to help drive content for the release, etc.

15:15 < warren> abadger1999, I've been trying to lean on our folks to release the brew schema sooner, so it can be part of an elegant PDB design earlier. 15:21 < abadger1999> lutter has some good points.

...time of this draft. ''Please do a reality check before using these talking points as anything other than a discussion draft!''}} ...features when talking about the release, and to help drive content for the release, etc.

...edule. The new schedule allowed us, and will continue to, work within the release cycle and assign tasks based on time and priority. The schedule for Fedora ...ss which ensures that all parties are on the same page and working towards release readiness. For the future, and for F12, the goal should be to integrate in

** Check our [[Fedora_14_Talking_Points|Talking Points]] or the complete [[Releases/14/FeatureList|Feature List]] * Does Fedora have a PPC release?

* Talking Points Slide Deck. **have a joint mktg/ambassadors meeting once or twice a release on IRC

Fedora operado em uma [[time-based release schedule|agenda de lançamento baseada no tempo]]. Assim como o Fedora Mark ...ersionNumber|next}}_talking_points | F{{FedoraVersionNumber|next}} talking points]]

2. Plan talking points and agenda -t minus 1 day before - DONE The below points is historical documentation on how we arrived on this schedule decision.

Where you can find all kind of ready prepared Marketing Material, Talking Points, Projects, pressmaterial, etc. If you want directly to contribute on the upcoming Release or have some ideas and not knowing how to fill take a look at

...quickly present an overview of highlighted features when talking about the release. ...nts are based in part on the [[Releases/14/FeatureList|features]] for this release. Any Fedora community member can introduce a feature, using our [[Features

...00"><FONT COLOR="#FFFFFF">Leverage the community for Fedora marketing, PR, talking</FONT></TD> <TD ALIGN=LEFT BGCOLOR="#000000"><FONT COLOR="#FFFFFF">points, etc. to simply the FPL's job and amplify key messages.</FONT></TD>

...11 are also available, which describe the changes in Fedora since the last release, and are full of information for both new and experienced users. == Fedora 11 Release Overview ==

...ll help to plan and also track improvements happening in Fedora particular release. ...page will can be useful for them as well, with plan listed for particular release. New contributors can pick-up some task from list and ask existing owner to

..." that needs to be described. In some cases, a feature is part of a multi-release arc of work, and that context can be useful to provide. ...a-devel-list/2009-September/msg00924.html noted problems] with XZ, so this talking point should be considered '''''TENTATIVE'''''.}}

...quickly present an overview of highlighted features when talking about the release. ...nts are based in part on the [[Releases/15/FeatureList|features]] for this release. Any Fedora community member can introduce a feature, using our [[Features

...ilter on team, as well as other Fedora event and other happenings, such as release schedule. === Fedora Release Schedule ===

...Fedora 26 Beta, the next big step on our journey to the exciting Fedora 26 release in June. ...ere: [https://fedoramagazine.org/announcing-the-release-of-fedora-26-beta/ Release Announcement on the Fedora Magazine]

This page is the home of the [[Feature profiles]] for the F13 release. For more information on what feature profiles are or how this deliverable ...s by way of how some of these were collaboratively engineered. The talking points covered in this feature profile will include "experimental 3D extended to f

...design work for Fedora balloons for events and work on the Fedora 14 Alpha release banner. Our issue wraps up this week with a few security advisories for Fe ...blocker bugs and give a "go" or "no go" signal on the state of the Fedora release.

...rn how to write [[One page release notes]], please refer to the [[One page release notes SOP]].}} --> ...any volunteers. OpenOffice.org has been replaced with LibreOffice in this release. Thanks to Caolán McNamara from Red Hat for his upstream participation an

...as features and their supporting materials continue to evolve, the talking points themselves are continuously being filled in.}} ...quickly present an overview of highlighted features when talking about the release.

...quickly present an overview of highlighted features when talking about the release. ...nts are based in part on the [[Releases/19/FeatureList|features]] for this release. Any Fedora community member can introduce a feature, using our [[Features

...dora Electronic Lab]? Read its [[FedoraElectronicLab/TalkingPoints|talking points and press releases]]. ...e Fedora Project's name in such releases may damage the project. Any press release mentioning the Fedora Project should:

17:12 < dmalcolm> talking about test plans, I'm a little worried that having "plans" might discourage 17:29 * craigt points gumby_ to https://testing.108.redhat.com/ as well

* Fedora Magazine broke new records for views, especially near the release of a new version of Fedora. A major milestone we hit in November was 250,00 * good cooperation for the talking points amongst WGs. [[User:Mailga|gabri]]

...ollection of FAD EMEA related links. In marketing news, Fedora 12 talking points, Fedora Insight status and other current activities. In ambassadors, detai === F12 Talking points ===

| style="color: #407a40" colspan="2" | 2. Release events status (+ RE contest) | style="color: #42427e" colspan="2" | hhmm, is this for your release party?

...- development standards for activity developers. (What is testing, what is release.) * This is the release, pull it from git, and build an installable package == something that helps

* We need to review the requests next week and hit the high points If you are unsure of messaging, Fedora Talking Points is always a good source

<!-- 1. Gather material from the existing release notes and announcement, = Single Source Summary for Fedora 9 Release Announcements, etc. =

== Fedora 9 Talking Points == ...ommunity members, did all the work to integrate KDE 4 into Fedora for this release. The group set up its own roadmap and milestones, working in coordination w

...meeting last week as well as more internal detail on the Fedora 13 Talking Points, mentioned above. The Ambassador's beat includes coverage of last week's So ====Call for Participation - Fedora 13 Talking Points====

12:33 <@wwoods> yum is one of the most important parts of any release - pretty much anything else that's broken can be fixed if yum works ...December/msg00069.html is a really good link) outlined the need for better release criteria

...h during non-release time, and then as we coordinate the websites around a release.</font></tt></td></tr> ...h><td width="100%" bgcolor="#eeeeee"><tt><font color="#4d4d93">So for this release I've requested a list of all the links we're going to give out in press rel

...t KDE beat features news of KDE 4.3.1 hitting Fedora updates and some post-release fixes, news on several new KDE applications, and coverage of work of the KD ===F12 Talking points===

...k on Fedora 14 Talking Points in advance of FUDCon 2011, calls for the F14 release slogan and discussion around it. Two pieces with Fedora In the News this w ...rketing/2010-August/013326.html</ref> made a twits on the topic of Talking Points to make reference to a "upstream marketing" session on FUDCon Tempe. Kind o

...nt ces sujets de conversation ont été choisis, consultez la page [[Talking Points SOP]]. Ces sujets de conversation sont destinés à aider les [[Ambassadors ...s spins Fedora 14 officiels, visitez la page [[Releases/14/Spins|Fedora 14 Release Spins]].

= Fedora Release Engineering Meeting :: Monday 2008-03-03 = * delaying freeze and corresponding beta release by one week

In Announcements, we have "F9 Beta release announcement", "Rawhide 20080328 Snapshot", "FUDCon Lodging", "Fedora Pytho === F9 Beta release announcement ===

...o Hivex and kf translations submission issues, announcement of an upcoming release of Transifex v 0.8 rc1, and new members for the Fedora Localization Project ...owever critical path packages might not be pushed unless they are fixing a release blocking issue. Once we've validated all the fixes we will do more frequen

...up on us ... and it takes a bit to get images lined up. It's better this release with twu owning the QA side of the process, but it still feels like there i ...esults in a slip. See {{ticket|rel-eng|4844}}. None of the Alpha rel-eng release tickets have been filed at this time.

...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/27/ChangeSet|Change Set]] for this release.

...rketing team includes logs of the recent weekly meeting, Fedora 12 talking points development, and a Fedora Insight update. In Quality Assurance news, detai === Fedora 12 (Constantine) Alpha Release ===

[12:11] <hansg> as the jpp release tag extension is in a different already approved guidelines doc, and the ja [12:11] <hansg> get around to updating the jpp release tag guidelines

The contact points are: ...rder to have all non-x86 related information in one place we will still be talking about it here and offering all the tips & tricks we have.

...rn how to write [[One page release notes]], please refer to the [[One page release notes SOP]].}} --> * Fedora 14 release announcement (http://fedoraproject.org/wiki/Fedora_14_Announcement)

...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/28/ChangeSet|Change Set]] for this release.

* Changing Release Notes data 11111 * Two days before F11 was released, the release notes beats on wiki were still changing

...m all to the websites team wiki page, so we start getting a sense of who's talking where ...haeldehaan.net/2008/07/29/how-open-source-is-your-open-source/ dehaan's 12 points] are visible. Done.

...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/26/ChangeSet|Change Set]] for this release.

...ent discussion on Fedora 13 beta artwork, and the design suite as a Fedora talking point. This issue wraps up with pointers to last week's security advisorie release-engineering trac<ref>https://fedorahosted.org/rel-eng/newticket</ref>

* Release party ...tickets, coordinating with other Fedora groups such as the Program Manager/Release schedule and Marketing

=== Test release after merge? === * FESCo discussed whether to have a test release after the merge is finished. It was decided that the daily spins being cur

* Changing Release Notes data 11111 * Two days before F11 was released, the release notes beats on wiki were still changing

* '''16:45 - 18:45''' // Fedora Linux 39 Release Party & 20th Anniversary Celebration ...nsamyak || {{check}} || {{check}} || {{check}} || DEL <=> KTM || hi, en || Release Engineering, Fedora, community building, open source

= F33 Release Party Social Events = The Mindshare Committee is currently working on organizing a Release party event to celebrate F33.

...e who basically wrote lots of release note type stuff for us. We had an F5 release summary page on the wiki that was a list of highlights. And that was about * The beginning of one-page release notes: this was THE SINGLE BEST NEW WIKI PAGE that we had in a year. It was

<notting> what sorts of preparation are we talking about? <f13> We probably need a page that chronologs what each stage of a release needs

= Fedora Release Engineering Meeting :: Monday 2008-11-03 = == Preview Release ==

...formación sobre cómo se eligieron estos puntos de discusión, vea [[Talking Points SOP]]. La intención es ayudar a los [[Ambassadors]] a presentar rápidamen ...lte el vínculo [https://fedoraproject.org/wiki/Releases/15/Spins Fedora 15 Release Spins].

1. Can you tell me what new features users could see in the next release, 2. Microsoft is currently aiming for a 2009 Holiday release for Windows 7 and

15:13 < mmcgrath> glezos: we're just talking about mediawiki - https://publ= 15:16 * abadger1999 wonders how new install smolt checkins and release day=

...ers will take care of their to rebuild their own packages. Means: Increase release, put a comment like "Rebuild for FC5" in the changelog and request build. W 19:33 < mschwendt> | thl: good posting - sums up a few good points

= Fedora Release Engineering Meeting :: Monday 2008-02-25 = == Release Engineering Representative ==

...rn how to write [[One page release notes]], please refer to the [[One page release notes SOP]].}} --> * Fedora 14 release announcement (http://fedoraproject.org/wiki/Fedora_14_Announcement)

<!-- 1. Gather material from the existing release notes and announcement, = Release Talking Points =

* Release criteria == Release criteria ==

=== Multi-Lingual Release Announcement === ...rketing-list[1] - The time has come to produce the final list of talking points[2] we want

...e schedule / Milestones]] (General, not specific to F16 dates or any other release) ...Features/Policy/Status | What happens to features during the course of the release cycle]]

= Fedora Release Engineering Meeting :: Monday 2008-10-13 = ...gilmore and nirik to get additional seeders in place for the next snapshot release

...es team has been hard at work at this for a while and we're all excited to release it today. KarstenWade points out in his blog[1] ,

[12:06] <spot> Post Release Package guidelines [12:09] <scop> tibbs, moving the non-numeric part to the release tag

As I think this is an important security problem I decided to release This is a one off service I felt compelled to release to help people, I

is to include a link in the debuginfo package that points to the elf file and the ...on, as the shortest way to transfer the information of which module we are talking about that was involved in some crash/backtrace. Since one might want to st

INPRGRESS - Adam Williamson posted feedback during the beta release readiness meeting ''36 issues were marked as beta blockers prior to freeze, === F-12 Talking Awesomeness talking points ===

17:11:00 <brunowolff> The timing is such that F12 will probably release with 2.6.31, though 2.6.32 will be releasing around the same time. 17:21:51 <brunowolff> documented, just not where the link points to.

Information about a package includes: name, version, release, license, ...pr, specifying a name and one of the supported architectures + fedora/epel release.

...} || {{check}} || {{check}} || {{check}} || PRG=>BRU || cz,sk,en || Fedora Release Engineering Team member, submitted talks for distro devroom ...ter audio routing were added on top of this infrastructure. The recent 1.0 release marked a big milestone in the development. This talk will detail the curren

= Fedora Release Engineering Meeting :: Monday 2007-08-13 = == Release Naming ==

{{draft | These are [[One page release notes]] for Fedora 13 and are still under construction. }} ...ured in each version of the one page release notes (if you look at the F12 release note translations, those were updated to be regional too, and that was very

[11:49] <racor> f13: no idea what you are talking about. multiple dir owners are common practice in perl packages for ages. [11:53] <nim-nim> I mean we don't have many data points because only one person foobared his font package so far, and the fact the

* Fedora 13 release announcement (http://fedoraproject.org/wiki/Fedora_13_Announcement) * Fedora 13 release notes (http://docs.fedoraproject.org/en-US/Fedora/13/html/Release_Notes/)

* release note the eula change * f13 remembers somebody talking to him about this

* Beta docs: There was a Beta release announcement which mentioned fedup and kparal and adamw worked on commonbug * To request a release note for a bug, set fedora_requires_release_note flag to ?

** Overall structure, documentation, entry points * I'm familiar with the Git/GitHub workflow - well, we're talking GlitterGallery, which does better ;)

...an="2" | *nirik doesn't have anything to add there. Someone needs to start talking to various upstreams... | style="color: #407a40" | so we're coming up on beta release reasonably soon now

** Overall structure, documentation, entry points * I'm familiar with the Git/GitHub workflow - well, we're talking GlitterGallery, which does better ;)

#* Ball now in the fedora-release-notes court, but since Adamw is a docs team member now, he might help raise [[User:jlaska]] gathered the QA talking points for the meeting ahead of time (see [[QA/Meetings/20090603#F-11_QA_Post-mort

"In preparation for the Fedora 9 release, I would like to add "The Fedora Unity Project is proud to announce the release of new ISO Re-Spins (DVD and CD Sets) of Fedora 8. These Re-Spin ISOs are b

MaxSpevack points out in his blog[1] , KarstenWade points out in his blog[1] ,

* Commit for a full release cycle--from one GA date to another * Refresh ''current triagers'' page at start of each release cycle

| style="color: #407a40" | Oh, the one other thing - anybody interested in talking to GNOME folks about their blogs setup? ...le="color: #407a40" | That'd be the case if it were in puppet too, but the points above still apply

...dora 7 one or two years down the road, the decisions that we made for this release will have proven to be as impactful as anything we've done in the Fedora sp === Fedora 7 Deep Freeze/GA release schedule change ===

...rn how to write [[One page release notes]], please refer to the [[One page release notes SOP]].}} --> ...any volunteers. OpenOffice.org has been replaced with LibreOffice in this release. Thanks to Caolán McNamara from Red Hat for his upstream participation an

..... "this is the time to do a lot of the things with Fedora that we've been talking about for the last few months. We've got management focus to really kick s Nov 13 10:11:32 <gregdek> "...we've been talking about a world in which anyone can contribute to Core, or 'opening Core' or

...ra-fad.2010-03-13-17.28.html Afternoon log] - discussion of [[User base]], talking about a marketing campaign aimed at downstream developers (for instance, Py * Entry points to Fedora - are they clear, simple, potential calls to action? Discussion o

...t mean driving the whole thing foward (just to make sure you know what I'm talking about) (10:24:46 AM) c4chris: maybe there are already several points taken care of (like builds in mock)

* Allowing freeform use of version control system data in the release field of snapshot packages. [12:21] <f13> racor: if you're only talking about CVS head sure, same with SVN you can check out SVN "head" at any date

16:29 < mspevack> | greg -- one compelling use case is bugzilla instances talking to each other using OpenID 17:25 < green_west> | wwoods: point taken, talking about that

...eKit permissions and a note on the current state of initial-setup make the release notes * Final release criteria need to be revised into the new format

...ystems, and a number of virtualization improvements have emerged with this release that use memory more efficiently, provide more flexible hardware and networ * Fedora 12 release announcement (http://www.redhat.com/archives/fedora-announce-list/2009-Nove

* release criterion change proposals still hadn't been sent out * status of Xen in re the release criteria was still being kicked around

[14:14] skvidal: how much patching are we talking about? [14:21] jcollie: ok, so what about what i was talking about before... the main repository for a package would still contain spec,

** if the distribution is a downstream distribution (i.e. talking about the benefits accrued from OLPC using Fedora might be appropriate) : #Fedora is adding FooBlah feature in the next release.

| style="color: #407a40" | For examples, look at FOSDEM, or some of the F10 release parties, or OpenExpo. ...="color: #407a40" | Ambassadors should know the high points of the current release -- [[Talking_points_for_F10]]

* brunowolff to ping release engineering about post-freeze update re-opening for f17 | style="color: #407a40" | hey everyone, let's keep talking nonsense about rolls for the first half hour

...e been completed and are ready for translation rebuild after the Fedora 11 Release Announcement. The Fedora Localization Project welcomed new contributors for ...around the Project, from work with the Fedora Bug Zappers, maintaining our release schedule, and facilitating meetings for many of our community teams. He wi

...roject is pleased to announce[1] the release of the fourth and final test release of Fedora 7! ...eed your help. Join us! This is the final test release before the Fedora 7 release, which is scheduled for May 24, 2007.

* look at FAS users and see how many reappear from release to release in the various FAS-authenticated channels (are they blogging, on lists, com ...sks that one can complete with Fedora (for instance, "deviantart users are talking about photo filtering... they could use GIMP")

| style="color: #407a40" | So I'd like to start by talking about RPM, it's basic benefits and why it's important to the world. | style="color: #407a40" | the release fc9

* 2010-03-25 - [[:Category:Fedora_13_Beta_RC_Test_Results|Test Beta 'Release Candidate']] * 2010-02-18 - [[:Category:Fedora_13_Alpha_RC_Test_Results|Alpha Release Candidate verification]]

* [[rhbug:820985|#820985]] is accepted as a blocker - violates the F17 alpha release criterion "The installer must be able to report failures to Bugzilla and lo ...ded, but upstream has not yet written the online documentation to which it points

...about advanced storage for release notes'' - this was done, install guide points advanced storage users to kickstart ...r: #407a40" | "viking-ice to let docs team know about advanced storage for release notes"

...(or point to existing documentation) for how bugs are noted (common_bugs, release notes, install guide etc...) How to determine which bugs land in which plac ...to existing tests and a reorganization of priorities based on the updated release criteria.

* Fedora 13 release announcement (http://fedoraproject.org/wiki/Fedora_13_Announcement) * Fedora 13 release notes (http://docs.fedoraproject.org/release-notes/)

= Fedora Release Engineering Meeting :: Monday 11-Jun-2007 = * See IRC log for discussion points

= Fedora Release Engineering Meeting :: Monday 07-MAY-07 = * need a document explaining how to get your package into the release... something like "If you did FOO before the merge, here is how to do FOO n

| style="color: #42427e" | I don't know what you all are talking about. It's 10:04am. :) | style="color: #488888" | Well, I laid out all of the decision points in my last long email...I can recap.

...og/20090902.html</ref> the security vulnerabilities affecting RHEL between release 5.3 and (the just-released) 5.4. === Release deliverables ===

...ion testing for Fedora 14, process for upstream bug reporting for the next release, and more details on a couple proven tester work areas. Translation news i To ensure high quality translations in the final release, please be aware Software String Freeze Policy <ref>https://fedoraproject.o

* Release criteria / test cases * ''tflink try again with asking other teams to review the updated release criteria'' - tim forgot about this, he'll do it now

| style="color: #407a40" | looks like Ian points out what we found as well ... with regards to manual category searching usi | style="color: #488888" | so i want to get this sorted before talking to luke and till about adding support to koji and f-e-k

| style="color: #818144" | jds2001 &amp; poelcat: what you two are talking about was the issue brought up on the test mailing list, correct? ...lay out the different tasks that need to happen at different points in the release cycle

* [jlaska] find Beta Release notes wiki page? ** '''Beta release notes''' - [[Fedora_11_Beta_release_notes]]

| style="color: #4d4d93" | jreznik: I think he's talking about RT | style="color: #407a40" | god, they lose many points for me - how can you scare people with an example ticket like "There is no

= Fedora Release Engineering Meeting :: Monday 2008-02-11 = * Release Engineering is expected to produce custom spins for F8

00:10 < CB6> I'm just curious what was migrated to.. are we talking to a new CMS? 00:20 < spevack> ok... CB6 and tw2113, you guys were briefly talking about content? how we decide what goes where?

| style="color: #407a40" | damnit, no talking before I set meetingname! :) | colspan="2" | * adamw points to ACME-branded product and grins at the camera

| style="color: #42427e" | and talking about the general challenge of building a strong Fedora community overall ...or: #42427e" | or perhaps an enterprising individual will take some of the points I make in these sessions and refresh the material :)

* Release criteria revision ...ite up the common bugs page and lobby for inclusion of major issues in the release announcement

| style="color: #407a40" | discussion points were in agenda | style="color: #407a40" | any feedback or points people want to disucss?

...Day, Software Freedom Day mentioned above, but also have helped on Fedora release party events. ...pending on the sponsors we can even have radio announcements. We have been talking with [http://www.guegue.com.ni Güegüe Comunicaciones] and most likely the

| style="color: #42427e" | Release is coming up soon it needs testing. ...eatures in the backend I am fixing. Ones that can't really be changed post release

| style="color: #407a40" colspan="2" | Well, we're going to release a Fedora Education Spin with F11 (wiki page is here: [[Education_Spin]]). N | style="color: #8c4a4a" colspan="2" | guys, i need a small help, i need few points for 'why Fedora Edu Spin not Kubuntu'

* adamw planning to draft a plan for improved presentation of the release criteria. tflink suggests moving the criteria out of the wiki could help, b * adamw to draft up a proposal for revising the presentation of the release criteria

| style="color: #488888" | Guest85807: I think that jreznik was talking about status updates from the fedup devel(s) ...| jreznik: you mean how done does fedup need to be before it doesn't block release from a QA perspective?

"Fedora 7 is the first release where the development was one hundred * http://docs.fedoraproject.org/release-notes

* Fedora 13 release announcement (http://fedoraproject.org/wiki/Fedora_13_announcement/ru) * Fedora 13 release notes (http://docs.fedoraproject.org/ru-RU/Fedora/13/html/Release_Notes/)

summer. Applications will open March 28, so start talking with developers in for a final release (or pushed as an update for any stable release). FPC

DimitrisGlezos points out in his blog[1] , KarstenWade points out in his blog[1] ,

...arazioni di stampa? Esse le puoi trovare su [[Fedora press archive| Press Release Repository]].<BR><BR> ...a diffondere come ambasciatore, [[Marketing/TalkingPoints| Fedora Talking Points]] può rivelarsi un buon punto di partenza.}}

"The Fedora Unity Project is proud to announce the release of new spin[2] , the Everything Spin. Included in this spin are all the pac For new features and other changes, please read the release notes of

* Release criteria / test cases == Release criteria / test cases ==

(10:11:04 AM) thl: f13, that's exactly one of the crucial points... ...packages need to make it through review to get everything done before fc7 release

ChristopherBlizzard points out in his blog[1] , AnthonyGreen points out in his blog[1] ,

= Fedora Release Engineering Meeting :: Monday 16-APR-07 = a. the final release.

| style="color: #407a40" | Two great points by tatica and kital -- and two points that we will probably discuss again later, but are worth mentioning again n ...bout the current release, you can talk about features that are in the next release, etc.

In preparation for 2009-08-12 - Release Readiness Meeting, I'd like to poll the team for thoughts on high profile a Upcoming release events:

| style="color: #854685" | are these goals overall or for just a partiular release | style="color: #42427e" | comphappy: =) nothing, jut we'd been talking about your metrics

RahulSundaram points out in his blog[1] , RolandWolters points out in his blog[1] ,

| style="color: #407a40" | Now we'll go into greater detail on all these points. | style="color: #407a40" | Setting aside Fedora Ambassadors for a moment and talking about the general challenge of building a strong Fedora community overall m

| style="color: #818144" | I know release notes were a hot topic ...lspan="2" | -!- quaid changed the topic of #fedora-meeting to: Docs mtg -- Release notes: i) Beta deliverable discussion; ii) process discussion

...Day, Software Freedom Day mentioned above, but also have helped on Fedora release party events. ...pending on the sponsors we can even have radio announcements. We have been talking with [http://www.guegue.com.ni Güegüe Comunicaciones] and most likely the

JonPhillips points out in his blog[1] , WarrenTogami points out in his blog[1] ,

| style="color: #407a40" | ok, lets move on to talking about mock's caching ability. | style="color: #407a40" | so mock can cache at 3 points (and does by default).

19:59 < ixs> | ahh? the release issue of having .3 in FC5 and .5 in FC4? 20:04 < nirik> | the pathalogical case here is directfb... new so every release. ;)

...media art prep for F11. Nicu's Fedora webcomic postulates on the F11 pre-release queue, and we complete this week's melange with much news on the virtualiza ...g/wiki/Releases/11/Schedule</ref> continues to list Tuesday, May 26 as the release date.

...y of ambassadors will want to spread how proud they are of their Fedora 11 release to the masses." ...hat could use some extra testing in preparation for the imminent Fedora 11 release.

MaxSpevack points out in his blog[1] , JohnPalmieri points out in his blog[1] ,

* 2009-10-07 - Beta Project Wide Release Readiness Meeting ...from there into general issues causing undesirable changes in late pre-pre-release phases

...release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the: Go/No-Go Meeting."

...ressing frustrations that his window to help the project is closing as the release engineering commitments increase. dpravec noted that from talking with Fedora users, seems to me that best what we can do to improve quality

..... "this is the time to do a lot of the things with Fedora that we've been talking about for the last few months. We've got management focus to really kick s 16:11 < gregdek> | "...we've been talking about a world in which anyone can contribute to Core, or 'opening Core' or

..... "this is the time to do a lot of the things with Fedora that we've been talking about for the last few months.&nbsp;&nbsp;We've got management focus to rea ...> gregdek</th><td class="text" style="color: #8c4a4a">| "...we've been talking about a world in which anyone can contribute to Core, or 'opening Core' or

== Release criteria updates == | style="color: #407a40" | #topic Release Criteria Updates

| style="color: #854685" | adamw, does not change matter there is no point in release criteria if it can be overruled ...#407a40" | Viking-Ice: there's nothing in any discussion about overriding release criteria

...e starts with announcements from the Project, providing much detail on the release of Fedora 14 beta. In news from the Fedora Planet, details on how FUDCon s ====Announcing the release of Fedora 14 Beta!!====

...4685" | don't we have a common bugs page for beta already, linked from the release notes? | style="color: #407a40" | but wanted a summary page somewhere. the release notes seems as good a place as any

...rchives/fedora-devel-announce/2009-January/msg00012.html</ref> that "after talking with Red Hat Legal about how we should be handling trademarks in package su I should probably have done one for Fedora 10 release, but (silly me) expected then that the new font packaging guidelines would

....redhat.com/show_bug.cgi?id=F15alpha. If you think a bug should block the release of F15 Alpha, set it as blocking that bug, and it will be reviewed at the m ...show_bug.cgi?id=f15alpha-accepted. This is for bugs which don't block the release but for which fixes should be allowed through alpha freeze. You can propos

pages, and IRC, when talking about Fedora. Many thanks to the people Download a torrent file there to begin downloading a release

...al other items. Translation includes reports of activity around Fedora 13 release notes, upcoming tasks, new modules and new team members.In Design team news ...Notes for Fedora 13'''. If you have content you would like to see the the Release Notes go to:

...suggested using ''critical severity bugs in in critical path packages'' as release criteria ...laska: no we are done and wouldn't want to degrade the quality of our next release :)

| style="color: #4d4d93" | you're talking about something for a more exhaustive test plan | style="color: #4d4d93" | you're talking about defining one of the cases for the *real* testing

...kert|Christoph Wickert]] embedded[13] a video interview with Mario Behling talking about [http://lxde.org/ LXDE] Fedora Release Party in Milan[17]

| style="color: #407a40" | mcloaked: I assume you're talking about bug#627789 ? ...you are welcome to propose it by adding blocks:F14Blocker and listing the release criteria you feel is impacted

ChristopherBrown thought that slipping the Fedora 8 Test2 release by a week and trying to contact maintainers and upon failure to rebuild all ...r to get the work done he suggested a script which would add a ".1" to the release and rebuild automatically any package not queued or rebuilt by some time.

* 2009-09-18 - Fedora 12 Snapshot #3 release | style="color: #818144" | markmc is online, i'm talking to him

...links for a wiki page describing how to update repoinfo.conf when branched release is available, linked from the existing branched SOP pages | style="color: #818144" | it's mostly just talking points for now

| style="color: #4b904b" | package test plans... what are we talking about? | style="color: #488888" | I think syslinux has a config file that points to images that might not get used until booting.

...t worked well, and what areas needed improvement for the recent F-12-Alpha release. | style="color: #407a40" | | yeah ... all good points

...] confirmed[3] that this was the case and expanded on the explanation: "If talking to NM fails, the app should either (a) assume a connection, or (b) could be ...ginal complaint had been about "yank[ing] out commands [...] from a stable release [Fedora 9]". [[ToddZullinger|Todd Zullinger]] discounted such complaints an

=== Fedora 10 Preview Release === ...e Fedora 10 Preview Release. The Fedora 10 Preview Release is our last pre-release offering before we let everyone taste the goods for real."

...pops some salient items out of the development maelstrom including a "New Release of libvirt-0.6.1" and SELinux "sVirt Support Committed". There's a lot more ...ml</ref> Chris on the new Teaching Open Source community and provided some points that came up while visiting with people who are in the trenches trying to t

...ed F13 critpath updates - https://admin.fedoraproject.org/updates/critpath?release=F13&amp;untested=True | style="color: #4d4d93" | j_dulaney: consider privmsgs for talking to the bot

...o a big responsibility. We must face this responsibility with every Fedora release and try to get the latest and greatest software into the new version so it ...mber of new features as we approach a well integrated and tested Fedora 14 release. I hope to see even more community involvment in setting the direction and

...ld improve focus around prioritizing test efforts, blocker bug review, and release criteria. Current efforts cast a very wide net, which may not be in line w ...ther this bug was a blocker or a day-0 worthy. Consensus was to request a release note for the bug and line up for day-0. f13 noted that he would accept thi

"The Red Hat Bugzilla team is happy to announce that the release of the ...the wiki. There are over a dozen cool features being set up for this next release."

Fedora, but points of reference (this application supports file formats like Wesnoth there is real tension between have a later release to play

"The Fedora Unity Project is proud to announce the release of new ISO Re-Spins (DVD and CD Sets) of Fedora 7. These Re-Spin[2] ISOs a ...currently under active development and the release notes in the last test release did mention that what was being offered is a preview. They use glib and gco

: autoqa-0.4.4 release ...is when we have a FAIL result for one update ... and an update to a newer release resolves the issue

...n epoch isn’t needed to fix things up when rawhide gets branched for a new release). Between this and KDE’s conversion to git, there should be plenty of doc The next morning, after waking up, eating breakfast, and talking with…well I can’t remember exactly who I talked to, so many people. I�