Re: F35 Change: "Fedora Linux" in /etc/os-release

[Louis Lagendijk]

On Thu, 2021-03-11 at 13:57 +0100, Kevin Kofler via devel wrote:
> Matthew Miller wrote:
> > Check this out from back in the day:
> > https://fedoraproject.org/wiki/File:Logo-history-variations.jpg
> > 
> > Under that scheme, it was obvious that we did a number of different
> > things, all of them "Fedora".
> 
> But those things have one thing in common, they are all gone (except
> the 
> project): Core and Extras have merged, Legacy has been discontinued,
> the 
> Foundation has never materialized.
> 
> > The merger with Extras and creation of a real community project was
> > essential to our ongoing success, but it also introduced a
> > community /
> > output confusion.
> 
> All that is left from the above is the Fedora Project that produces
> Fedora. 
> I do not see a big confusion there. Every community-developed product
> is 
> produced by a project community.
> 
> And other attempts at resolving this alleged "community / output
> confusion" 
> in Free Software communities have only led to more naming chaos, not
> less, 
> see, e.g., the KDE rebranding fiasco. (There are about 99500 search
> engine 
> hits for "KDE 5", a phrase that officially does not exist due to the 
> rebranding from "KDE 4" to "(KDE) Plasma 4" in the 4.x era.)
> 
> In most cases, it is obvious whether Fedora, the GNU/Linux
> distribution, or 
> Fedora, the community that develops it, are meant. When not, it can
> be 
> easily clarified as Fedora GNU/Linux vs. the Fedora Project in the
> specific 
> context.
> 
> > This has gotten worse in recent years as we introduce new and
> > different
> > things, leading to things like people saying "Oh, that's in CoreOS,
> > not
> > Fedora", where the shorthand is more confusing than helpful.
> 
> And I think it makes sense to say that: CoreOS is a very different
> operating 
> system from Fedora as we know it (even if they share the GNU/Linux
> base) and 
> so should (continue to) have a completely different brand, not
> Fedora.
> 
> > > 2. Why Linux and not GNU/Linux? Linux is just a kernel. GNU/Linux
> > > is an
> > > OS.
> > 
> > Fedora Linux is an OS. Although GNU project utilities are indeed
> > essential, Fedora Linux consists of more than those plus Linux, and
> > the
> > contributions of many of those other projects is equally essential.
> 
> But the Linux kernel is just a small part of the operating system,
> and not 
> even the characterizing part: Android also uses the Linux kernel, and
> it is 
> a completely different operating system!
> 
> > Additonally:
> > 
> > * We are not part of GNU, and in fact listed by them as
> > specifically not
> >   endorsed because we have policy disagreements.
> 
> Fedora is not "part of Linux" either. The easiest way to avoid any
> such 
> confusion is to just call it Fedora.

Or if you want to separate the project and the product, avoid the Linux
and GNU additions and use something more generic:
Fedora OS vs Fedora project?
Louis L
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Fedora 32 System-Wide Change proposal: Enable fstrim.timer by default

[Louis Lagendijk]

On Fri, 2020-01-03 at 10:21 -0700, Chris Murphy wrote:
> On Fri, Jan 3, 2020 at 9:06 AM Robbie Harwood 
> wrote:
> > Nico Kadel-Garcia  writes:
> > 
> > > On Thu, Jan 2, 2020 at 2:48 PM Robbie Harwood <
> > > rharw...@redhat.com> wrote:
> > > > "John M. Harris Jr"  writes:
> > > > > On Friday, December 20, 2019 10:59:52 AM MST Chris Murphy
> > > > > wrote:
> > > > > 
> > > > > > Issuing the command once per week harms no one
> > > > > 
> > > > > Based on what's actual in the Change proposal, this is not
> > > > > the case.
> > > > > 
> > > > > Even if this goes through, in my opinion, it should only
> > > > > affect the
> > > > > GNOME Spin, or perhaps even "all graphical" spins at most.
> > > > 
> > > > No?  This is extremely useful for cloud environments - maybe
> > > > the most
> > > > useful.  It allows VM hosts to reclaim and reuse empty disk
> > > > space;
> > > > otherwise, the disk images just bloat to their maximum allowed
> > > > size.
> > > 
> > > Its most useful for the cloud *providers*, not the cloud clients.
> > > For
> > > the clients, getting the AWS space pre-allocated form EBS is
> > > often a
> > > notable performance improvement, and restoring it to AWS saves
> > > AWS
> > > resources. Not the client system performance.
> > 
> > Sure, but in many cases the client is also the provider.  Consider
> > running kvm on a laptop (which I and many others do for work...) -
> > you'd
> > really like the disk space back you're not using, rather than each
> > VM
> > taking 10-20G it doesn't need.  I end up having to edit every VM
> > configuration in two places after each install/provision in order
> > to get
> > that behavior - that's not reasonable.
> 
> By default, GNOME Boxes and virt-manager VM's, do not enable block
> device discards. So this feature is a 'no op' in that case. And also
> fstrim.service won't run in a container. I've updated the feature to
> reflect these two things.
> 
virt-manager does not enable discards on IDE or virtio disks. I think
it DOES enable discard on SCSI disks. So strictly speaking the above is
true as long as the default emulation layer is not SCSI but it is a
matter of a few clicks to enable it.

> 

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 32 System-Wide Change proposal: Enable fstrim.timer by default

[Louis Lagendijk]

On Fri, 2019-12-20 at 17:46 +0100, Lennart Poettering wrote:
> 
> Or let me ask this differently: the "discard" mount option of various
> kernel file systems, what does it differently than what this new
> fedora feature is supposed to do?
> 
fstrim does the discard once a week (or whenever it it triggered),
discard as a mount option does trigger discard when a block is freed.
Depending on the drive it may actually slow down IO as the SSD will
need more time to finish the IO. Doing an fstrim leaves the processing
to the SDD. That was the argument years ago. I don't know if this is
still true for modern SSD's. For older SSDs fstrim would stil be the
safer option. And automatic trimming is long overdue in my opinion.

Louis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: No longer supporting mailing lists:

[Louis Lagendijk]

On Tue, 2019-08-27 at 12:00 -0300, Gerald B. Cox wrote:
> Why is it when I say that I don't want to clutter up my email with
> mail from mailing lists I'm told it's a misconfiguration.  It's not a
> misconfiguration.  I don't want the forum email cluttering up my mail
> - and I don't want to use an NNTP gateway, I want to use Discourse. 
> Why is that so hard to understand?   
> 
> On Tue, Aug 27, 2019 at 11:47 AM John Harris 
> wrote:
> > On Tuesday, August 27, 2019 7:29:28 AM MST Gerald B. Cox wrote:
> > 
> > >  Using mail, I have to access the archives to read the full
> > thread.
> > 
> > 
> > 
> > This is just due to your configuration. You could easily either
> > save the 
> > 
> > mailing list to your mailbox, or use an NNTP gateway.
> > 
> > 
> > 
Different people have different work flows, you like to go to
Discourse, others prefer mail/nntp. For a lot of people (including
myself) the lack of threading is a show stopper for their workflow. 
The mail interface in Discourse is...lacking a lot of features for a
lot of people. Your comment "why is that so hard to understand" applies
both ways/Louis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Workstation and disabled by default firewall

[Louis Lagendijk]

On Tue, 2019-08-27 at 10:14 -0400, Robert Marcano wrote:
> On 8/27/19 10:03 AM, John Harris wrote:
> > 
> Any new Wifi connection could be identified by their SSID, so it
> could 
> still be secure by default and ask for that specific connection to
> be 
> opened because you trust them. As I proposed on another email, bring 
> back the NetworkManager zones UI to GNOME Settings, simplified with 
> being an option to confine that connection to the public zone.
> 
Yeah, the WIFI case can be as simple as that: let the use choose the
default zone. Public means closed firewall,  otherwise the workstation
zone can be as it is now. This protects the user from big mistakes as
unintended sharing of information over samba, media players et. 
> The problem of identifying wired connections still remains and needs 
> more thinking.
For this case NetworkManager could verify the gateway address/ MAC to
see if this is a known network, and if not offer the user to allocate
that connection to a public/private zone? I seem to remember that
Windows does something similar (sorry not a big Windows user)...
/louis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Plan to retire ffgtk (Fritzbox manager)

[Louis Lagendijk]

On Fri, 2019-04-26 at 11:28 +0200, Louis Lagendijk wrote:
> hi all,
> I am planning to retire ffgtk as I no longer use it and it does no
> longer work with "recent" Fritzbox modem firmware from AVM. Any
> objections?
> 
> I know Roger exists s replacement, but I have no interest in
> packiging
> it.
> 
> best regards, Louis

As nobody reacted I have no retired ffgtk from master. It will remain
available for released fedora versions
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Plan to retire ffgtk (Fritzbox manager)

[Louis Lagendijk]

hi all,
I am planning to retire ffgtk as I no longer use it and it does no
longer work with "recent" Fritzbox modem firmware from AVM. Any
objections?

I now Roger exists s replacement, but I have no interest in packiging
it.

best regards, Louis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Hiding the grub menu by default on single OS installs

[Louis Lagendijk]

On Thu, 2018-05-31 at 06:42 -0700, Gerald B. Cox wrote:
> 
> 
> On Thu, May 31, 2018 at 6:08 AM, Chris Adams 
> wrote:
> > Once upon a time, Hans de Goede  said:
> > > And for F30, single OS install we get:
> > > 
> > > 1) grub menu not shown, 0 second timeout, no way to get to the
> > menu
> > > 2) grub menu shown with 5 sec timeout after a failed boot
> > 
> > If I know I want the menu (say I need to boot single-user to fix
> > something), how would I do that in this setup?
> > 
> 
> I'm fine with changing the default - I understand that under normal
> circumstances most people could care less about seeing the screen -
> but I 
> do strongly agree with the comment above.  When things sometimes go
> south and you need that menu, there needs to be a simple, well
> documented
> way to get it... easily... without having to go on a google treasure
> hunt to find the instructions.  Otherwise, don't do it.

How would this feature interact with things like /.autorelabel? Would
the presentation of the grub menu in that case still depend on the
previous boot being marked as successful? Is a boot that only does a
relabel successful?

And how about differences between upgrades (I think that the boot
loader is in that case not re-installed IIRC) vs. new installations.
Could that cause issues?

/Louis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/TIQA4ZSYH2QGMY5NJR6CFXV2RNEJPWKL/

Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

[Louis Lagendijk]

On Sat, 2018-02-24 at 16:40 +0100, Andrea Musuruane wrote:
> Hi
> 
> On Sun, Feb 18, 2018 at 6:09 PM, Igor Gnatenko  project.org> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > Over this weekend I've performed scratch-mass-rebuild without
> > having gcc and
> > gcc-c++ in buildroot of all Fedora packages, many of which failed
> > due to random
> > reasons and I grepped all logs for some common errors found by
> > analyzing
> > hundreds of build logs.
> 
>  
> > [...]
> 
>  
> > List of packages and respective maintainers:
> > https://ignatenkobrain.fedorapeople.org/gcc-removal-pkgs.txt

I fixed cups-bjnp while I released a new version earlier this week.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: CUPS will change license since 2.3 version - now incompatible with GPLv2

[Louis Lagendijk]

On Wed, 2017-11-08 at 10:42 +0100, Zdenek Dohnal wrote:
> Hi,
> 
> CUPS upstream changed license of project to Apache license 2.0, which
> is
> now incompatible with GPLv2. This change will be in new minor release
> of
> CUPS - 2.3.0, which is currently in developing phase (not in Fedora
> for
> now). If someone takes code of CUPS and has its project under GPLv2,
> please change it to GPLv3 (which should be compatible according
> https://fedoraproject.org/wiki/Licensing:Main?rd=Licensing#SoftwareLi
> censes
> ) or try to argument with CUPS developers against this change on
> their
> mailing list c...@cups.org .
> 
> Is there someone who is influenced by this change?

My apologies fr the late response: I have been pretty busy.
cups-bjnp was affected as it was GPLv2 only. In versiob 2.0.1 It is now
changed to be GPLv2 or later. The new package has been built for
Rawhide and f28.

/Louis 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 System Wide Change: Rename "nobody" user

[Louis Lagendijk]

On Fri, 2018-01-12 at 07:20 -0500, Steve Dickson wrote:
> Instead of doing the blow by blow these threads
> always turn into I'm just going jump to the point.
> 
> systemd wants to use uid 65534 and it can't because
> NFS is using it. So instead of changing systemd needs
> they want to change NFS potentially break all NFS 
> environments. 
> 
> Is or isn't this what we are talking about without
> all the bloviation to justify the change.
> 
> steved.

Breaking all NFS environments is a (way?) too strong statement. My file
server is running Freebsd and it uses 65534 as userid for default.
Freebsd however calls it nobody, go, figure Now for nfs this is
nowadays no problem anymore as we have the id-mapper. It now maps
between 99 and  65534 and will start to automagically map between 65534
and 65534. 
Are there any real world examples of files owned by nobody left on
Fedora?

I guess that other OSs/distributions use 65534 for nobody, so this
change would improve inter-operability with other environments.

LouisL
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Packagers - Flag day 2016 Important changes

[Louis Lagendijk]

On Sun, 2016-12-11 at 18:34 -0600, Dennis Gilmore wrote:
> Greetings. 
> 
> As previously announced, releng has made a number of changes as part
> of
> it's 2016 "flag day". 
> 
> All package maintainers will want to make sure they have updated to
> the 
> following package versions (some may be in testing as of this email):
> 
>  python-cccolutils-1.4-1
>  fedpkg-1.26-2
>  fedora-packager-0.6.0.0-1
>  pyrpkg-1.47-3
>  koji-1.11.0-1
> 
With these updates I can kinit to my username. This almost works:

kinit llagend...@fedoraproject.org
Password for llagend...@fedoraproject.org: 
Password expired.  You must change it now.
Enter new password: 
Enter it again: 
kinit: Cannot find KDC for realm "FEDORAPROJECT.ORG" while getting
initial credentials

After changing the password in FAS I can login. But it is strange that
we use kerberos, but we cannot update the password
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: RFC: Change the default hostname for Fedora 26+

[Louis Lagendijk]

On Wed, 2016-11-09 at 12:58 -0500, Przemek Klosowski wrote:
> 
> On 11/09/2016 08:02 AM, Simo Sorce
>   wrote:
> 
> 
> 
> > > >   Although this is true, one thing we could do is set a default
hostname
> > > > that is static ("fedora" or similar is fine), and teach the
utilities
> > > > used to join an AD/IPA/etc.. domain to generate a new random
hostname if
> > they detect the hostname is the generic "static" one.
> > The hostname is used in the install-time-generated disk volume
names
> > (/dev/mapper/fedora_myhostname-home), so changing it is
confusing.
> 
> > Would it make sense to leave the old names? or rename the
volumes? 
> 
>   
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Is using a unique volume group name not actually preferable. 
If one needs to add a disk from one machine to another it avoids the
problem of having 2 volume groups with the same name and therefore
overlapping LV names.
I got bitten by that once.

/Louis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Specs using %define

[Louis Lagendijk]

On Thu, 2015-12-24 at 15:01 -0600, Jason L Tibbitts III wrote:
> cups-bjnp
Is fixed and built in Rawhide, F22/F23 are fixed but not built.
Louid
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: dial-up comps group?

[Louis Lagendijk]

On Sat, 2013-03-09 at 08:36 -0500, Nico Kadel-Garcia wrote:
 On Sat, Mar 9, 2013 at 6:48 AM, Dan Mashal dan.mas...@gmail.com wrote:
 
  Thanks Kevin for starting this discussion.
 
  Please remove isdn4k completely from comps and retire/block it from Fedora
  19. The maintainer is unresponsive, the service fails on boot, has scriptlet
  errors on yum update, and quite frankly if anyone is still using ISDN in
  2013 I feel sorry for them.
 
 A quick look at Wikipedia confirms that it's still in use in India,
 Japan, and fairly extensively in Europe. It's being phased out
 everywhere, but it reaches places that ADSL still does not, and it's
 higher bandwidth than consistent latentcies are valuable for some
 remote audio applications.  So you may feel sorry for them, but it's
 going to be around a while longer.
Even though I do not have an ISDN connection anymore, my ADSL/VDSL modem
still uses ISDN Capi over IP for internal usage. And my ffgtk package
uses that for sending faxes etc. I have found the maintainer to be
somewhat slow in responding but the bugs I submitted have been solved. I
definitely object to retiring/blocking it.
 


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Are 3.0 kernels working for anyone?

[Louis Lagendijk]

On Fri, 2011-06-10 at 15:06 -0500, Bruno Wolff III wrote:
 On Fri, Jun 10, 2011 at 20:17:46 +0100,
   Richard W.M. Jones rjo...@redhat.com wrote:
  
  Works very well for me, but:
  
  - Make sure you're running kernel-3.0-0.rc2.git0.2.fc16 with the
  ftrace bug fixed (thanks Kyle).
 
 Done.
 
  - Make sure you upgrade module-init-tools *before* installing the 3.0
  kernel.
 
 Done.
 
  - Make sure you've got the latest udev.
 
 Done.
 
 Looks like I need to spend some time capturing the error and filling out
 a bug report.
 
 Thank you everyone, for the feedback.
I had problems too. I guess that is was something in the initramfs. I
ended up removing the 3.0 kernels and then re-install it (yum update).
That solved it for me

Louis

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Gnome Shell Extension manager/framework planned?

[Louis Lagendijk]

On Fri, 2011-06-03 at 12:28 -0300, Michael Wiktowy wrote:
 Hello,
 
 I am seeing a metric ton of extensions showing up for Gnome shell that
 are enhancing the shell in positive ways. Some are packaged singly;
 some are grouped together in bundles; some are configured by editing
 .js files directly. I am hesitant to install any of them because of
 the manual, bolted on feel of them and the risk of them causing
 trouble in the future.
 
 Is there some sort of extension management planned that would handle
 the separate enabling/disabling/configuration of individual extensions
 via the grand unified Settings menu?
 
Am I alone believing that a lot of the extensions are due to missing
configuration options? E.g. I now see already competing extensions for
changing the menu to add a shutdown option without having to press the
alt-key, remove some menu etc., add another hotspot etc
Do we really need all these as extensions? I like Gnome3, and use one
of the extensions to add the shutdown option, but believe Gnome3 needs
more configurability so we can avoid all these corrections as
extensions. Or is there a better way to achieve the needs of people?

Louis

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Fixing the glibc adobe flash incompatibility

[Louis Lagendijk]

On Wed, 2010-11-17 at 17:11 -0500, Genes MailLists wrote:
 Lets also not forget that the motivation for changing memcpy was to
 get some speedup - has anyone seen evidence of any significant benefit
 of that glibc change?


There is one more reason to revert the change imho: abusing memcpy this
way is seen more often. I like the old adagium: be strict in what you
send but be liberal in what you expect


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Debugging printing problems

[Louis Lagendijk]

On Thu, 2010-03-18 at 17:43 +, Tim Waugh wrote:
 Hi,
 
 I've been meaning to expand the wiki page about debugging printing
 problems for a long time.  I finally got round to it today:
   https://fedoraproject.org/wiki/How_to_debug_printing_problems
 
 Tim.
 */
 
hi tim
great info indeed. Maybe you could consider adding info on the bjnp
backend (for Canon's proprietary network (usb-over-ip)  protocol:

bjnp is for Canon's proprietary bjnp network protocol (usually port
8611)

The bjp backend is available in the cups-bjnp package

Louis
 -- 
 devel mailing list
 devel@lists.fedoraproject.org
 https://admin.fedoraproject.org/mailman/listinfo/devel


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: Name that Tree!

[Louis Lagendijk]

On Sat, 2010-02-13 at 07:11 -0800, Jesse Keating wrote:
 On Sat, 2010-02-13 at 07:36 -0600, Mike Chambers wrote:
  
  rawhide - packages for rawhide dir
  testing - packages for current development release going to testing
  stable  - packages for current development release going to main dir
  release - packages for current officially released already gold dir 
 
 Right, this is the Debian naming.  The problem is that we have testing
 for releases too, and that gets a tag confusing if you just talk about
 testing.

cooking as in not yet ready

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel