What is the definition of "truly critical functionality"?

["Theodore Y. Ts'o" <tytso@mit.edu>]

Hi,

I'm trying to mean what is meant by "truly critical functionality
problem" in Section 5.5.1 in the Debian Developer's Reference:

    Extra care should be taken when uploading to stable. Basically, a
    package should only be uploaded to stable if one of the following
    happens:

        * a truly critical functionality problem
        * the package becomes uninstallable
        * a released architecture lacks the package

Does this mean "release critical"?

For example, #920767, which causes e4defrag to crash on 32-bit
platforms.  Relatively few people use e4defrag --- especially compared
to e2fsck or mke2fs.  So is a fix for something which is a second-tier
aspect of e2fsprogs's functionality, and which only applies to 32-bit
platforms, something which is "truly critical"?

Thanks!

					- Ted