Fedora board meeting minutes
[Mon Nov 20 2006] [12:04:17] <mspevack> ok, we're gonna get started
[Mon Nov 20 2006] [12:05:17] Join couf has joined this channel (n=bart@fedora/couf).
[Mon Nov 20 2006] [12:06:41] <mether> mspevack: calling
[Mon Nov 20 2006] [12:06:58] <mspevack> topic 1 -- art. Leadership needs
to be defined
[Mon Nov 20 2006] [12:07:06] <mspevack> clearly the two largest leaders
have been Maureen Duffy and Diana
Fong
[Mon Nov 20 2006] [12:07:37] <mspevack> there was a conversation last week
with Diana in which she offered to
put together some policy and
structure around the use of people
who are doing mockups, ideas,
etc. of the Fedora Mark.
[Mon Nov 20 2006] [12:08:09] <warren> mspevack, I recall Maureen did
quite a bit of work related to that
in the past. was she in the
discussion?
[Mon Nov 20 2006] [12:08:42] <mspevack> What the Board wants to do is
identify one person who can be the
clear leader of the art project.
Max will talk with Maureen and
Diana both, make sure they are on
the same page, see who wants to do
what, etc.
[Mon Nov 20 2006] [12:08:56] <mspevack> also
[Mon Nov 20 2006] [12:09:11] <mspevack> make sure that the Fedora art
project meets the requirements that
we have outlined on the wiki to "BE
A PROJECT"
[Mon Nov 20 2006] [12:09:22] <glezos> Note: Mairin is very active and
concerned about the proper way of
doing things. FYI, he's also a lot
into the GNOME website redesign.
[Mon Nov 20 2006] [12:09:32] <skvidal> glezos: she
[Mon Nov 20 2006] [12:09:37] <glezos> sorry.
[Mon Nov 20 2006] [12:10:23] <mspevack> We're going to make sure that
Maureen and Diana are both on board
-- but it's time to make one person
the "leader" but that doesn't mean
that only one person is capable of
leading.
[Mon Nov 20 2006] [12:10:46] <mspevack> So this action item is on Max, with
a goal to follow up with Diana and
Maureen
[Mon Nov 20 2006] [12:12:07] <warren> glezos, (Maureen and Mairin are
different spellings of the same
name, in case it isn't clear.)
[Mon Nov 20 2006] [12:13:48] <mspevack> moving on
[Mon Nov 20 2006] [12:13:53] <mspevack> Fedora Summit
[Mon Nov 20 2006] [12:14:10] <mspevack> FESCO meeting was last week
[Mon Nov 20 2006] [12:14:15] <mspevack> Rex -- it was surprisingly smooth
[Mon Nov 20 2006] [12:14:26] <mspevack> Rex -- biggest concern was "oh man,
now we have a bigger job to do."
[Mon Nov 20 2006] [12:14:35] <mspevack> more policy, more decisions, etc.
[Mon Nov 20 2006] [12:15:24] <mspevack> Max -- what does FESCO need to
become? Do we need to add folks?
2 or 3 red hat folks?
[Mon Nov 20 2006] [12:15:33] <warren> FESCo is excited about it, and
wants to know target dates for
things to happen and more of what
board wants FESCo's role to be. I
told FESCo that we are waiting on
RH internal decisions, but
meanwhile there are many things
FESCo can work on to prepare.
[Mon Nov 20 2006] [12:15:42] <mspevack> JesseKeating would probably be a
good person to add, or someone
blessed by Jesse
[Mon Nov 20 2006] [12:16:05] * f13 looks
[Mon Nov 20 2006] [12:16:15] <warren> During the FESCo, we proposed a
hybrid Red Hat assigned and
community voted membership model
for future of FESCo. I can
elaborate on this if the board
wishes it.
[Mon Nov 20 2006] [12:16:29] Quit chabotc has left this server ("Leaving").
[Mon Nov 20 2006] [12:16:35] <rdieter> warren: go ahead... elaborate away...
[Mon Nov 20 2006] [12:16:53] <mspevack> greg -- the success of the FESCO
model is what has gotten us to
where we are today
[Mon Nov 20 2006] [12:17:20] <mspevack> greg -- at a high level it seems
like f13 for sure needs to be on
there
[Mon Nov 20 2006] [12:17:29] <mspevack> jesse is going to be building the
tools that we are using in the new
world of fedora
[Mon Nov 20 2006] [12:17:39] <mspevack> rahul -- eventually we'll need a
new name
[Mon Nov 20 2006] [12:17:52] <mspevack> we'll talk about that near the end
[Mon Nov 20 2006] [12:17:56] <warren> FESCo remains a majority of
community voted slots (details of
that can be figured out later).
However there are a small number of
Red Hat assigned seats from major
RH engineering departments. This
is because 1) RH seats cannot be
voted out of their own job. 2) It
is important for each major RH
engineering department to have
someone accountable for community
outreach and communication.
[Mon Nov 20 2006] [12:18:11] <warren> Yes, definitely Jesse needs to be
on FESCo.
[Mon Nov 20 2006] [12:18:32] <f13> warren: I question whether or not
we need to be on FESCo itself, or a
subcommitee that ansers to FESCo
[Mon Nov 20 2006] [12:18:44] <warren> f13, that is a possibility yes.
[Mon Nov 20 2006] [12:18:56] <f13> because, frankly, I don't care
about the governance of getting new
users into the community and some
of those deals. I care about
making product releases
[Mon Nov 20 2006] [12:19:02] <mspevack> greg -- fesco is the first place
where we institutionalized real
power for the community, and that
is what has been successful
[Mon Nov 20 2006] [12:19:07] <mspevack> f13: nod
[Mon Nov 20 2006] [12:19:08] <warren> Anyhow this hybrid membership
proposal is only a strawman, we can
debate this in detail later.
[Mon Nov 20 2006] [12:19:21] <f13> so personally I envision a
subcomittee that would be like the
release cabal, they just answer to
FESCo or whatever.
[Mon Nov 20 2006] [12:20:09] <warren> I like the hybrid model, because it
makes it very clear that RH
engineering has contacts who are
accountable to maintaining
communication. If we can find a
better way to achieve that goal,
then I would be willing to discuss
that.
[Mon Nov 20 2006] [12:20:34] <warren> Each RH engineering department
*MUST* not be insulated away from
community.
[Mon Nov 20 2006] [12:20:59] <f13> warren: I agree. I just think that
trying to shove it all in FESCo
might make FESCo itself unweildy
and unable to accomplish anything.
[Mon Nov 20 2006] [12:21:07] <mspevack> JEREMY -- will take the action of
pulling Jesse into the FESCO'ish
fold, shielding Jesse from what he
doesn't need to deal with, and
making sure communication is
flowing.
[Mon Nov 20 2006] [12:21:11] <f13> compartmentalizing responsibility
is a good thing.
[Mon Nov 20 2006] [12:21:30] <warren> f13, I disagree that it would be a
bad thing, but anyway we can figure
out our options later.
[Mon Nov 20 2006] [12:21:34] <mspevack> Max -- what else from last week do
we need to discuss?
[Mon Nov 20 2006] [12:21:48] <mspevack> Rahul -- when do these proposals
from last week become policy?
[Mon Nov 20 2006] [12:21:54] <mspevack> Jeremy -- it depends on the
different pieces
[Mon Nov 20 2006] [12:22:05] <mspevack> Matt -- combination of core/extras
is the biggest thing for Fedora 7
development
[Mon Nov 20 2006] [12:22:21] <mspevack> Jeremy -- I have already started
having discussions with folks in RH
engineering management. continuing
that after this meeting
[Mon Nov 20 2006] [12:22:32] <mspevack> Jeremy -- the build system
conversations are going to be
difficult, but we knew that up
front
[Mon Nov 20 2006] [12:25:42] <mspevack> *conversation now about different
scenarios -- different possible
courses of action, depending on how
much buy-in we can get*
[Mon Nov 20 2006] [12:28:59] <mspevack> greg -- the open sourcing of better
build tools is INEVITABLE whether
we choose to open our own tools or
not. So the work is *going* to
happen eventually. Red Hat needs
to help make it happen, rather than
force re-implementation of the
wheel
[Mon Nov 20 2006] [12:29:06] <mspevack> jeremy -- +1
[Mon Nov 20 2006] [12:30:17] <mspevack> Board (therefore Max) is ultimately
responsible for driving all this
crap
[Mon Nov 20 2006] [12:30:25] <mspevack> Jeremy/DaveZ talked about liveCD
stuff on Friday
[Mon Nov 20 2006] [12:30:42] <mspevack> mail forthcoming -- not much more
of a summary than that, other than
"positive developments"
[Mon Nov 20 2006] [12:30:59] <mspevack> and all of it will happen on the
liveCD list
[Mon Nov 20 2006] [12:32:21] <mspevack> greg is now officially a member of
the fedora board
[Mon Nov 20 2006] [12:32:27] <mspevack> unanimously
[Mon Nov 20 2006] [12:32:37] * BobJensen claps
[Mon Nov 20 2006] [12:32:41] <glezos> yay!
[Mon Nov 20 2006] [12:32:46] <couf> hooray!
[Mon Nov 20 2006] [12:32:51] <mspevack> Matt -- I really like the release
process idea of extending the
lifecycle of core to 13 months
[Mon Nov 20 2006] [12:34:48] <mspevack> greg -- 13 months is a reasonable
commitment -- but not sure we can
commit to more than that. If we
get to a point where maybe we can,
it can always be revisited.
[Mon Nov 20 2006] [12:35:28] <mspevack> greg -- Legacy saw its best days in
the RHL timeframe. For folks who
need significantly more timeframe
than Fedora is prepared to do,
CentOS continues to be compelling
[Mon Nov 20 2006] [12:36:37] <f13> matt at BU was really the only one
who needs something between CentOS
and Fedora, but understands we
can't just accomodate him
[Mon Nov 20 2006] [12:36:43] <f13> he's largely happy with the plan
[Mon Nov 20 2006] [12:36:51] <mspevack> rahul -- so there's lots of details
still to be figured out. what's
the timeframe?
[Mon Nov 20 2006] [12:36:52] <warren> EPEL (Enterprise Extras) adds a
great deal of usability for folks
who choose to use CentOS or RHEL.
[Mon Nov 20 2006] [12:37:00] <mspevack> max/jeremy -- trying to get as much
done by the end of the year as
possible
[Mon Nov 20 2006] [12:38:32] <mspevack> Fedora 7 will be a success if we
have two things
[Mon Nov 20 2006] [12:38:43] <mspevack> 1) the "core/extras" merge
complete, and all the work around
that
[Mon Nov 20 2006] [12:38:58] <mspevack> 2) out of those tools, the ability
to have custom liveCDs
[Mon Nov 20 2006] [12:39:21] <mspevack> BRANDING
[Mon Nov 20 2006] [12:40:08] <mspevack> greg and max talked with chris
grams about some ideas of what we
can call "Fedora Universe"
[Mon Nov 20 2006] [12:40:56] <mspevack> Fedora * was one brainstorming
idea, but it's getting a bit
pooh-poohed. Ultimately, this is a
branding opportunity that needs to
continue. We've been saying Fedora
Universe a lot as a "code name" but
we really can't call it that.
[Mon Nov 20 2006] [12:41:13] <mspevack> max -- so, who will own all this?
[Mon Nov 20 2006] [12:41:15] <mspevack> greg is the owner
[Mon Nov 20 2006] [12:42:08] <f13> Feodra Pangaea
[Mon Nov 20 2006] [12:42:54] Join ahalsey has joined this channel
(i=ahalsey@dhcp113094.qlc.hawaii.edu).
[Mon Nov 20 2006] [12:44:35] <mspevack> still need an RPM announcement
[Mon Nov 20 2006] [12:44:46] <mspevack> max will ping bill
[Mon Nov 20 2006] [12:44:56] <mspevack> since we want to put that action
item to bed
[Mon Nov 20 2006] [12:45:02] <mspevack> rahul -- are there any issues with
MONO?
[Mon Nov 20 2006] [12:45:28] <mspevack> greg -- we've had no word from
legal on any problems with Mono.
Unless we hear that, then there's
no reason to pull it out of the
distribution.
[Mon Nov 20 2006] [12:45:57] <warren> Mono seems to be a big question
from community, even if it turns
out that due to OIN nothing changes
from our stance, we must make an
official statement.
[Mon Nov 20 2006] [12:46:36] <mspevack> warren: that's right. Nothing
changes. But what we've not seen
is a statement from OIN itself!!!
[Mon Nov 20 2006] [12:46:40] <mspevack> matt -- that is what we need to see
[Mon Nov 20 2006] [12:47:06] <f13> mspevack: I think Paul nasrat is
the holdup on the RPM
announcement.
[Mon Nov 20 2006] [12:47:07] <warren> mspevack, good point.
[Mon Nov 20 2006] [12:47:48] <f13> mspevack: We also should get
something from upstream Gnome and
if they have made any decisions
about mono being part of core Gnome
apps
[Mon Nov 20 2006] [12:49:42] <warren> f13, +1
[Mon Nov 20 2006] [12:50:00] <mspevack> *various Mono discussion*
[Mon Nov 20 2006] [12:50:24] <mspevack> seth -- we can get a list of
everything that depends on mono
[Mon Nov 20 2006] [12:50:55] <f13> we already somewhat have that for
Core
[Mon Nov 20 2006] [12:51:13] <mspevack> seth -- muses on the depth of mono
dependencies within the distro
[Mon Nov 20 2006] [12:51:19] <mspevack> jeremy -- it's more complicated
than you think!
[Mon Nov 20 2006] [12:52:19] <mspevack> greg -- use the GPL of java to work
toward community-driven
replacements of mono applications?
[Mon Nov 20 2006] [12:53:03] <f13> mspevack: will take too much time
[Mon Nov 20 2006] [12:53:09] <warren> GPL java and community replacement
is still highly theoretical at this
point.
[Mon Nov 20 2006] [12:53:13] <mspevack> seth -- the deper mono integrates
with gnome, the more complicated it
will get to extract it *if* there
was ever a desire to
[Mon Nov 20 2006] [12:53:17] <warren> As well as beyond March 2007.
[Mon Nov 20 2006] [12:53:32] <mspevack> warren, f13: nod. just recording
what greg stated
[Mon Nov 20 2006] [12:54:13] <mspevack> bottom line -- mspevack needs to
push to get some *real* statements
made about mono and communicate
them out
[Mon Nov 20 2006] [12:54:15] <warren> Sorry, I'm trying to limit my
chiming in only when I feel there
is some key point missing from
IRC.
[Mon Nov 20 2006] [12:57:08] <mspevack> we're going to move to weekly Board
meetings for the forseeable future
[Mon Nov 20 2006] [12:57:13] <mspevack> going to hash all that out on list
(Log in to post comments)
Fedora board meeting minutes
Posted Nov 20, 2006 23:05 UTC (Mon) by mitchskin (guest, #32405) [Link]
<warren> GPL java and community replacement is still highly theoretical at this point.I find this statement odd. I was often confused about Sun's direction when McNealy was CEO, but with Schwartz they've been pretty clear about GPL Java. It's already started, even! Why are people so skeptical about this? I can imagine people being worried about scheduling; like not wanting to commit to Fedora 7 using Sun Java in case Sun takes longer than expected to finish opening the libraries. In this context, though, the question is long-term replacement of Mono apps, which isn't particularly schedule-sensitive.
Fedora board meeting minutes
Posted Nov 20, 2006 23:21 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]
You probably are missing context. Its not about skepticism. The full code drop with the ability to build JVM's out of completely GPL'ed code is stated to happen sometime before March 2007. Currently there are bunch of missing pieces. The inclusion of Sun Java in Fedora is out of question for the next release and hence porting Mono apps over to Java is not feasible within that time frame. Longer term there are probably other alternatives.
Fedora board meeting minutes
Posted Nov 21, 2006 0:08 UTC (Tue) by wtogami (subscriber, #32325) [Link]
March 2007 is the release date, and even then it will be missing pieces making it not immediately usable for Fedora, like parts needed for PPC.
Another question is what happens to upstream GNOME. Will GNOME integrate Mono components as a deep and irremovable part of the standard desktop? Will GNOME try to promote a truly and unquestionably (post-March 2007) liberty GNOME-Java platform?
Yes, Sun made the right choice for the community in choosing GPL, but this is not a magic bullet that will solve all problems immediately.
Fedora board meeting minutes
Posted Nov 21, 2006 3:37 UTC (Tue) by pflugstad (subscriber, #224) [Link]
March 2007 is the release date, and even then it will be missing pieces making it not immediately usable for Fedora, like parts needed for PPC.Do you mean that they won't release the JVM implementation for PowerPC? Or what? I would expect most of what's coming out will be platform independent. Thanks. Any references?
Fedora board meeting minutes
Posted Nov 21, 2006 15:08 UTC (Tue) by rahulsundaram (subscriber, #21946) [Link]
The current Sun JVM does not work on the PPC architecture.
Fedora board meeting minutes
Posted Nov 21, 2006 21:43 UTC (Tue) by pflugstad (subscriber, #224) [Link]
I was thinking the gp had seen something else.
The Sun JVM is already x86 & SPARC portable. And IBM (and Apple) have one on PowerPC, which I've heard is just Sun's Java + patches.
In any case, I would expect that once the whole thing is GPL'd that it'll be made to work on PowerPC pretty quickly - probably by IBM.
Pete
Fedora board meeting minutes
Posted Nov 21, 2006 7:10 UTC (Tue) by thebluesgnr (guest, #37963) [Link]
Will GNOME integrate Mono components as a deep and irremovable part of the standard desktop?
Not likely, since a huge part of the GNOME community is against that idea.
Will GNOME try to promote a truly and unquestionably (post-March 2007) liberty GNOME-Java platform?
Promote in what way? GNOME has been shipping Java bindings for a while and yet Python, Mono and C++ are still more popular than Java (talking about GNOME apps here). The only effective way to promote a language within the GNOME community is, IMO, to write great applications that use the GNOME platform with that language. This is what Novell's been doing for a while with Mono, and in a way Red Hat with Python. Not even Sun is using the Java bindings at the moment.
Fedora board meeting minutes
Posted Nov 21, 2006 16:27 UTC (Tue) by phgrenet (guest, #5979) [Link]
Eclipse is a great application using the Gnome platform, using SWT. Granted it is not fully integrated in Gnome, because it just links to some gnome libs.Here is an idea: now that Sun's JVM is GPLed, why not integrating it within the Gnome desktop. This would lead to much better integration of applications and better performance (the same JVM can run any number of Java-based application).
Fedora board meeting minutes
Posted Nov 23, 2006 1:22 UTC (Thu) by drag (guest, #31333) [Link]
Well that would be nice.
but right now there isn't much point in getting rid of Mono or replacing mono with anything.
With Mono and software patents it's all just paranoia right now. In my eyes it's not any worse then any other part of Linux that was made a replacement for propriatory software (which is most of it)
Personally I think that Java has a bright future though. But the way things are looking it may not be until 2008 before GPL'd java becomes a real-world full-fledged language replacement for current JVM stuff.
Probably what would be nice is if somebody knowledgable in both C# and Java would write up a technical comparision between the languages..
Relatively security, performance, ease of programming, integration with existing C and C++ code and such things.
Fedora board meeting minutes
Posted Nov 23, 2006 1:30 UTC (Thu) by drag (guest, #31333) [Link]
And just a for-isntance.. Alright you have Java for GTK and such.. but how is java with it's integration into gconf, or gstreamer, or other such things that are standard in Gnome? I know that all those aren't complete but will be required to make Java a full-fledged language for Gnome.
What I think would be cool would be for Java to get together with KDE. KDE doesn't have the same thing aviable for it as you have with Python and Mono for Gnome, but they probably need it.
For instance C++ and how KDE works is very object oriented fasion. Well that is nice for Java.
QT folks are interested getting KDE working on every platform aviable, and Java is already there for most of their targets.
QT and Java on the Linux desktop. QT and Java on mobile devices. All sorts of stuff like that. Seems like a good match.
Fedora board meeting minutes
Posted Nov 21, 2006 4:39 UTC (Tue) by mspevack (subscriber, #36977) [Link]
I'm "mspevack" from the meeting log.
I think it's great that LWN covers Fedora like this, but it's important to realize that what you're reading here is a "as fast as we can type it" summary of larger conversations that are being had on a phone call with anywhere between 7-9 people on it.
So a lot of the notes are going to be a bit brief, or lacking in detail. So just take that for what it's worth as you read these notes.
The best place to really get information on what Fedora is up to is the Fedora Advisory Board mailing list:
http://www.redhat.com/mailman/listinfo/fedora-advisory-board
Fedora board meeting minutes
Posted Nov 21, 2006 11:44 UTC (Tue) by nedrichards (subscriber, #23295) [Link]
Cool, thanks for the clarification. Even better than LWN coverage is the people its covering adding clarifications in the comments!
Fedora board meeting minutes
Posted Nov 21, 2006 6:55 UTC (Tue) by jimmybgood (guest, #26142) [Link]
They didn't live up to their 12 month support commitment, why should we care whether they extend it to 13?
Fedora board meeting minutes
Posted Nov 21, 2006 8:55 UTC (Tue) by khim (subscriber, #9252) [Link]
Where have you got the idea about "12 months" support commitment ? The policy was always "FC N support is stopped 1-2 months before FC N+2 is released". And it was always honored AFAIK. It was good deal for developers (they only need to support two distributions, never three or more), but not so good for users (you can not skip FC releases - or you'll be without support at some point). If they'll offer some overlap between supported times of FC N and FC N+2 then user will be able to skip FC N+1 - big win!
Fedora board meeting minutes
Posted Nov 21, 2006 17:24 UTC (Tue) by davej (subscriber, #354) [Link]
actually, technically there are times when we have 3 distributions 'in flight'. Right now for example, we have FC5, FC6, and rawhide.
(Yes, rawhide isn't technically a 'supported release', but its equally as much work, if not moreso).
The Ministry of Truth
Posted Nov 21, 2006 21:12 UTC (Tue) by jimmybgood (guest, #26142) [Link]
You have redefined the outcome as the commitment, which is easy to do with the assistance of the good folks at "The Ministry of Truth". Here's a link to an article written on lwn.net which states, "Security updates are made for approximately one year...":
http://lwn.net/Articles/119892/
The original commitment was two releases a year with security updates available for FCN until FCN+2 was released. The month or two before part was added later and references to the original commitment were deleted. Notice how the original schedules have been removed and replaced with, well, a flat out lie.
Here is the original link to release schedules:
http://fedora.redhat.com/participate/schedule/
Which now makes the claim that "This Page Has Moved" and gives the new location:
http://fedoraproject.org/wiki/Core/Schedule
But compare what you find at that link with what the Wayback Machine has archived:
http://web.archive.org/web/20040402104236/http://fedora.r...
And you'll see that not only was the page moved, it was also revised and condensed so as to make the comparison of schedules and actual release dates impossible. Without the Wayback Machine, of course.
The Ministry of Truth
Posted Nov 21, 2006 21:59 UTC (Tue) by khim (subscriber, #9252) [Link]
The original commitment was two releases a year with security updates available for FCN until FCN+2 was released.
Care to elaborate? Where was it said? Yes, it was said that there are will be security updates "for approximately one year" and there are will be two releases per year - but I never seen any commitment to the FCN and FNC+2 overlap. A lot of people just assumed that "approximately one year" mean FCN and FNC+2 overlap (me included) but when FC3 was scheduled everyone found out that "approximately one year" mean "we'll stop support for FC1 before FC3 is released because we have limited resources and can not support both FC1/FC2 'in fligh' and do quality testing for FC3 release". There was some grumbling (because users hoped to switch from FC1 straight to FC3) - but I never seen any evidence that "approximately one year" ever was supposed to mean "slightly more then one year to allow FCN => FCN+2 transition" so it was left at that.
The Ministry of Truth
Posted Nov 21, 2006 23:41 UTC (Tue) by jimmybgood (guest, #26142) [Link]
It's fascinating what a little research will turn up. I'm dead wrong, at least as FC2 is concerned. You are also dead wrong and corbet was dead wrong in the article I cited. We were all just repeating rumours with our own spin.
I apologize to the fedora community.
I currently can find no indication that Fedora has any commitment to security or bug fix updates for any period. So I'll change my comment.
For me to believe that Fedora can be useful for any serious purpose other than demonstration or as a test bed for Redhat development, they need to clearly state how long they will provide support in the form of security updates.
The Ministry of Truth
Posted Nov 22, 2006 5:12 UTC (Wed) by mdomsch (guest, #5920) [Link]
http://fedoraproject.org/wiki/LifeCycle
http://fedoraproject.org/wiki/FAQ#head-9baa0612d025313054...
both indicate the previous updates and security policy. It lists the example that Fedora Core 3 was updated until Fedora Core 5 test2 was released. Under the new policy (using for example the same versions, just for comparison), Fedora Core 3 would be updated until Fedora Core 5 release plus one month. This is, in effect, an extension of maintenance by test2->release+1m.
Also discussed was "should the new policy be implemented retroactively" such that FC5 is covered until FC7+1m, or should it start with FC6. I believe there was concensus that it should include FC5 as well. This gives people a chance to do the upgrade from N to N+2 and be covered for the whole duration between, without forgoing security errata for a time, and without requiring an upgrade from N to N+1 to N+2 in order to get security errata during that time.
Fedora board meeting minutes
Posted Nov 21, 2006 15:12 UTC (Tue) by rahulsundaram (subscriber, #21946) [Link]
Updates from Fedora Core was never claimed to be 12 months. It was around 9 months. For details about the current change see http://fedoraproject.org/wiki/FedoraSummit/ReleaseProcess
