On Wed, 6 Oct 2010 12:50:00 -0600 Kevin Fenzi wrote:
On Wed, 29 Sep 2010 09:19:08 +0200
Michal Schmidt mschm...@redhat.com wrote:
In the policy I do not see as clear distinction between F(n)
(current stable) and F(n-1) (old stable) as Jaroslav proposes. The
closest to it is this sentence:
On Tue, Oct 12, 2010 at 6:17 AM, Michal Schmidt mschm...@redhat.com wrote:
- remove any features
Michal
How do you guys update Gnome then? ;)
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, 12 Oct 2010 09:43:16 -0400 Brandon Lozza wrote:
On Tue, Oct 12, 2010 at 6:17 AM, Michal Schmidt wrote:
- remove any features
Michal
How do you guys update Gnome then? ;)
Perhaps you're confusing me with someone else. I have nothing to do with
Gnome.
But did Gnome ever
On Tue, Oct 12, 2010 at 9:48 AM, Michal Schmidt mschm...@redhat.com wrote:
On Tue, 12 Oct 2010 09:43:16 -0400 Brandon Lozza wrote:
On Tue, Oct 12, 2010 at 6:17 AM, Michal Schmidt wrote:
- remove any features
Gnome is known for removing features, it was a joke.
Perhaps you're confusing me
On Sat, Sep 25, 2010 at 01:03:13PM -0600, Kevin Fenzi wrote:
On Wed, 22 Sep 2010 22:21:33 +0200
Till Maas opensou...@till.name wrote:
Also can someone please explain the practical advantages of requiring
the autokarma threshold to approve the ability to push a non critical
path update to
On Wed, 29 Sep 2010 09:19:08 +0200
Michal Schmidt mschm...@redhat.com wrote:
On Tue, 28 Sep 2010 17:14:28 -0600 Kevin Fenzi wrote:
On Tue, 28 Sep 2010 18:45:11 +0200
Jaroslav Reznik jrez...@redhat.com wrote:
Ok - that's one problem - we sucks in selective updates and
information
On Mon, Oct 4, 2010 at 6:06 PM, Jesse Keating jkeat...@redhat.com wrote:
We knew that this would happen. We would lose some people. When a
project like us goes basically directionless for years it picks up
people who have different ideas about what they want to create and where
they want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/03/2010 07:07 AM, Brandon Lozza wrote:
On Sat, Oct 2, 2010 at 11:05 PM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sat, 2 Oct 2010 20:56:21 -0400, you wrote:
Fedora is just going to end up having a million repos for all the
software that
On Sat, Oct 2, 2010 at 11:05 PM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sat, 2 Oct 2010 20:56:21 -0400, you wrote:
Fedora is just going to end up having a million repos for all the
software that will not be updated for six months. And that makes us
look silly. Windows doesn't have
On Fri, Oct 1, 2010 at 2:23 PM, Gerald Henriksen ghenr...@gmail.com wrote:
Look, I realise you are passionate about KDE, and want the best KDE
experience in Fedora. But most people are not developers, they
instead are using their desktop environment of choice to get regular,
everyday things
On Sat, Oct 02, 2010 at 08:56:21PM -0400, Brandon Lozza wrote:
I'm not a developer at all. I'm a hardened power user and I got sick
and tired of not having the latest version of a particular application
and that led me to Fedora Linux. I'm a quick learner and these
disruptive changes often
On Sat, 2 Oct 2010 20:56:21 -0400, you wrote:
Fedora is just going to end up having a million repos for all the
software that will not be updated for six months. And that makes us
look silly. Windows doesn't have repositories for users who want the
latest firefox, they just download it and
On Thu, Sep 30, 2010 at 7:25 AM, Orcan Ogetbil wrote:
It shouldn't be. Never be afraid of learning, even in the tightest of
situations. It is good for your brain. It helps with analytical
thinking.
Once constant learning becomes part of your life, you really don't get
bothered with UI
On Fri, Oct 1, 2010 at 6:01 AM, Rahul Sundaram methe...@gmail.com wrote:
On Thu, Sep 30, 2010 at 7:25 AM, Orcan Ogetbil wrote:
It shouldn't be. Never be afraid of learning, even in the tightest of
situations. It is good for your brain. It helps with analytical
thinking.
Once constant
On Fri, Oct 1, 2010 at 6:05 PM, Brandon Lozza wrote:
The user has to tolerate some change. We can't cater to people who
never upgrade which seems to be what is taking place. Especially with
the fact that our end of life happens sooner, users must already
expect a constant stream of updates.
On Fri, Oct 1, 2010 at 6:01 AM, Rahul Sundaram wrote:
On Thu, Sep 30, 2010 at 7:25 AM, Orcan Ogetbil wrote:
It shouldn't be. Never be afraid of learning, even in the tightest of
situations. It is good for your brain. It helps with analytical
thinking.
Once constant learning becomes part
Orcan Ogetbil (oget.fed...@gmail.com) said:
What I am trying to say is, a redesign of an interface _usually_ have
valid reasons. Those users who don't want their menu items moving
around want to live like automated machines. Forbidding such changes
promotes lazyness.
If the update removes
On Fri, Oct 01, 2010 at 01:21:29PM -0400, Orcan Ogetbil wrote:
What I am trying to say is, a redesign of an interface _usually_ have
valid reasons. Those users who don't want their menu items moving
around want to live like automated machines. Forbidding such changes
promotes lazyness.
If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/1/10 10:41 AM, Chuck Anderson wrote:
How would you like it if you drove into work, parked your car, and
when you went out to your car at the end of the day to commute home
you found that the left-hand-drive changed to a right-hand-drive?
On 1 October 2010 19:21, Orcan Ogetbil oget.fed...@gmail.com wrote:
What I am trying to say is, a redesign of an interface _usually_ have
valid reasons. Those users who don't want their menu items moving
around want to live like automated machines. Forbidding such changes
promotes lazyness.
On Fri, 1 Oct 2010 08:35:45 -0400, you wrote:
The user has to tolerate some change. We can't cater to people who
never upgrade which seems to be what is taking place. Especially with
the fact that our end of life happens sooner, users must already
expect a constant stream of updates.
Yes,
On Fri, Oct 1, 2010 at 1:50 PM, Jesse Keating wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/1/10 10:41 AM, Chuck Anderson wrote:
How would you like it if you drove into work, parked your car, and
when you went out to your car at the end of the day to commute home
you found that
On Fri, Oct 1, 2010 at 1:28 PM, Bill Nottingham wrote:
Orcan Ogetbil (oget.fed...@gmail.com) said:
What I am trying to say is, a redesign of an interface _usually_ have
valid reasons. Those users who don't want their menu items moving
around want to live like automated machines. Forbidding
On Fri, 2010-10-01 at 14:51 -0400, Orcan Ogetbil wrote:
On Fri, Oct 1, 2010 at 1:28 PM, Bill Nottingham wrote:
Orcan Ogetbil (oget.fed...@gmail.com) said:
What I am trying to say is, a redesign of an interface _usually_ have
valid reasons. Those users who don't want their menu items moving
On Fri, Oct 01, 2010 at 02:47:23PM -0400, Orcan Ogetbil wrote:
On Fri, Oct 1, 2010 at 1:50 PM, Jesse Keating wrote:
On 10/1/10 10:41 AM, Chuck Anderson wrote:
How would you like it if you drove into work, parked your car, and
when you went out to your car at the end of the day to commute
On Tue, 28 Sep 2010 17:14:28 -0600 Kevin Fenzi wrote:
On Tue, 28 Sep 2010 18:45:11 +0200
Jaroslav Reznik jrez...@redhat.com wrote:
Ok - that's one problem - we sucks in selective updates and
information for users.
Other could be - change release scheme:
1. very similar to current
Rex Dieter rdie...@math.unl.edu writes:
[...]
On Tue, 28 Sep 2010 09:17:23 +0200
Dodji Seketeli do...@redhat.com wrote:
Brandon Lozza bran...@pwnage.ca writes:
Most of us KDE users want deliberate visible changes to the user.
That's the point in having the latest version.
Sorry if
On Wed, 29 Sep 2010 04:34:13 -0400
Orcan Ogetbil oget.fed...@gmail.com wrote:
On Sat, Sep 25, 2010 at 12:04 PM, Rex Dieter wrote:
Brandon Lozza wrote:
It seems like the policy would kill the use of an upgraded KDE
(4.5 to 4.6) because KDE almost always makes UI changes.
The kde-sig
On 29 September 2010 21:07, Kevin Fenzi kevin scrye.com wrote:
Currently, it's 4.5.1.
So, if we release with that, and then 4.6 comes out and changes the
user experence, we would need to see about granting an exception to
push that version in F14.
Speaking for myself, etc.
This fedora kde
On Wed, Sep 22, 2010 at 10:05 AM, Bruno Wolff III wrote:
On Wed, Sep 22, 2010 at 12:35:01 +0200,
Tomas Mraz wrote:
- Avoid changing the user experence if at all possible. - this is too
strong condition. In some cases fixing a bug might inevitable change the
user experience and in some cases
On Tue, 28 Sep 2010 18:45:11 +0200
Jaroslav Reznik jrez...@redhat.com wrote:
Ok - that's one problem - we sucks in selective updates and
information for users.
Other could be - change release scheme:
1. very similar to current one - rawhide, Fn, Fn-1
* rawhide - really raw development
Kevin Fenzi wrote:
On Tue, 28 Sep 2010 09:17:23 +0200
Dodji Seketeli do...@redhat.com wrote:
Brandon Lozza bran...@pwnage.ca writes:
Most of us KDE users want deliberate visible changes to the user.
That's the point in having the latest version.
Sorry if this has been already
On Saturday, September 25, 2010 09:03:08 pm Kevin Fenzi wrote:
On Thu, 23 Sep 2010 16:58:39 +0200
Jaroslav Reznik jrez...@redhat.com wrote:
Not a very latest thing but more like - more useful thing. Because
some useful user experience changes could lead to better user
experience even
On Sat, 2010-09-25 at 15:13 +0200, Till Maas wrote:
On Thu, Sep 23, 2010 at 09:48:34AM -0400, Adam Jackson wrote:
Say you ship with 50 bugs in a package. As you update it through the
lifetime of a release, that number should decrease more or less
monotonically. The bugs that take
What does matter to Fedora is having an updates policy that is
designed to minimize disruption to users during a release is pointless
if a significant part of Fedora - KDE - is going to be allowed to
ignore the updates policy and deliberately introduce visible to the
user changes in the
Jaroslav Reznik (jrez...@redhat.com) said:
It's not some random day - it's when you actually accept an update! It's
not
easy to estimate impact of update - but banning completely is not a solution
neither.
We do not give nearly enough information in our updates for the user to
make any
On Sat, Sep 25, 2010 at 22:26, Brandon Lozza bran...@pwnage.ca wrote:
I can't tell people Fedora is the best if it's not carrying the latest
upstream KDE, its just not possible. I'm constantly recruiting new
users. I'm in regular contact with the team of people who run
Techrights.
... lots
On Sat, 25 Sep 2010 22:26:46 -0400
Brandon Lozza bran...@pwnage.ca wrote:
I can't tell people Fedora is the best if it's not carrying the latest
upstream KDE, its just not possible. I'm constantly recruiting new
users. I'm in regular contact with the team of people who run
Techrights.
I
On Mon, 27 Sep 2010 10:19:51 +0200
Jaroslav Reznik jrez...@redhat.com wrote:
It's not some random day - it's when you actually accept an update!
It's not easy to estimate impact of update - but banning completely
is not a solution neither.
Well, most people either:
a) apply all updates as
On Sat, Sep 25, 2010 at 10:02 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sat, 25 Sep 2010 15:53:49 -0400
Brandon Lozza bran...@pwnage.ca wrote:
It would be nice to list it somewhere as an exception, to avoid
panics :)
Well, I personally do not want to say:
Hey, anytime you like down the
On Sat, 25 Sep 2010 22:26:46 -0400, you wrote:
I can't tell people Fedora is the best if it's not carrying the latest
upstream KDE, its just not possible. I'm constantly recruiting new
users. I'm in regular contact with the team of people who run
Techrights.
If a new release of KDE comes out,
On Sun, Sep 26, 2010 at 2:30 PM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sat, 25 Sep 2010 22:26:46 -0400, you wrote:
I can't tell people Fedora is the best if it's not carrying the latest
upstream KDE, its just not possible. I'm constantly recruiting new
users. I'm in regular contact with
On Sun, 26 Sep 2010 13:41:38 +0200, you wrote:
On Sat, Sep 25, 2010 at 10:02 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sat, 25 Sep 2010 15:53:49 -0400
Brandon Lozza bran...@pwnage.ca wrote:
It would be nice to list it somewhere as an exception, to avoid
panics :)
Well, I personally do not
On Sun, Sep 26, 2010 at 3:21 PM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sun, 26 Sep 2010 13:41:38 +0200, you wrote:
On Sat, Sep 25, 2010 at 10:02 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sat, 25 Sep 2010 15:53:49 -0400
Brandon Lozza bran...@pwnage.ca wrote:
It would be nice to list
On Sun, Sep 26, 2010 at 9:21 AM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sun, 26 Sep 2010 13:41:38 +0200, you wrote:
On Sat, Sep 25, 2010 at 10:02 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sat, 25 Sep 2010 15:53:49 -0400
Brandon Lozza bran...@pwnage.ca wrote:
It would be nice to list
Rex Dieter wrote:
The kde-sig asked FESCo to consider up to 1 KDE version upgrade per
release, and this was generally well-received during the last FESCo
meeting, so no reason to panic.
That's good to hear. Then I think my strategy for the future will be to mostly
stay on the next to latest
On Sun, 26 Sep 2010 15:33:25 +0200, you wrote:
On Sun, Sep 26, 2010 at 3:21 PM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sun, 26 Sep 2010 13:41:38 +0200, you wrote:
On Sat, Sep 25, 2010 at 10:02 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sat, 25 Sep 2010 15:53:49 -0400
Brandon Lozza
Do what thou wilt
shall be the whole of the Law.
On Sun, Sep 26, 2010 at 10:04 PM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sun, 26 Sep 2010 15:33:25 +0200, you wrote:
On Sun, Sep 26, 2010 at 3:21 PM, Gerald Henriksen ghenr...@gmail.com wrote:
On Sun, 26 Sep 2010 13:41:38 +0200, you
On Thu, Sep 23, 2010 at 09:48:34AM -0400, Adam Jackson wrote:
Say you ship with 50 bugs in a package. As you update it through the
lifetime of a release, that number should decrease more or less
monotonically. The bugs that take longest to fix are presumably the
hardest ones to fix, and
On Sat, Sep 25, 2010 at 9:13 AM, Till Maas opensou...@till.name wrote:
On Thu, Sep 23, 2010 at 09:48:34AM -0400, Adam Jackson wrote:
Say you ship with 50 bugs in a package. As you update it through the
lifetime of a release, that number should decrease more or less
monotonically. The bugs
Brandon Lozza wrote:
It seems like the policy would kill the use of an upgraded KDE (4.5 to
4.6) because KDE almost always makes UI changes.
The kde-sig asked FESCo to consider up to 1 KDE version upgrade per release,
and this was generally well-received during the last FESCo meeting, so no
On Wed, 22 Sep 2010 20:14:45 +0100
Alex Hudson fed...@alexhudson.com wrote:
On Wed, 2010-09-22 at 12:35 -0600, Kevin Fenzi wrote:
Alex Hudson fed...@alexhudson.com wrote:
I think there's one thing missing: some discussion about the
guiding principles about where these rules came from.
On Wed, 22 Sep 2010 22:21:33 +0200
Till Maas opensou...@till.name wrote:
On Tue, Sep 21, 2010 at 03:47:04PM -0600, Kevin Fenzi wrote:
I'd like to ask for feedback and helping cleaning up an updates
policy draft page:
https://fedoraproject.org/wiki/User:Kevin/Updates_Policy_Draft
On Thu, 23 Sep 2010 16:58:39 +0200
Jaroslav Reznik jrez...@redhat.com wrote:
Not a very latest thing but more like - more useful thing. Because
some useful user experience changes could lead to better user
experience even changing slightly the old one. It's not easy to catch
this in policy. I
It would be nice to list it somewhere as an exception, to avoid panics :)
On Sat, Sep 25, 2010 at 12:04 PM, Rex Dieter rdie...@math.unl.edu wrote:
Brandon Lozza wrote:
It seems like the policy would kill the use of an upgraded KDE (4.5 to
4.6) because KDE almost always makes UI changes.
The
On Sat, 25 Sep 2010 15:53:49 -0400
Brandon Lozza bran...@pwnage.ca wrote:
It would be nice to list it somewhere as an exception, to avoid
panics :)
Well, I personally do not want to say:
Hey, anytime you like down the road, you get an exception to push a
new major version. Have fun.
We
Wasn't this exception allowed for KDE at Fesco? Considering that a
typical KDE upgrade contains bug fixes, security fixes as well as new
features and UI changes.
On Sat, Sep 25, 2010 at 4:02 PM, Kevin Fenzi ke...@scrye.com wrote:
On Sat, 25 Sep 2010 15:53:49 -0400
Brandon Lozza
I can't tell people Fedora is the best if it's not carrying the latest
upstream KDE, its just not possible. I'm constantly recruiting new
users. I'm in regular contact with the team of people who run
Techrights.
If a new release of KDE comes out, this is what happens currently
1) Kubuntu adds a
On Wed, Sep 22, 2010 at 04:45:30PM -0400, Adam Jackson wrote:
On Wed, 2010-09-22 at 22:21 +0200, Till Maas wrote:
This here sounds strange:
| The update rate for any given release should drop off over time,
| approaching zero near release end-of-life; since updates are primarily
|
On Wed, Sep 22, 2010 at 4:45 PM, Adam Jackson wrote:
On Wed, 2010-09-22 at 22:21 +0200, Till Maas wrote:
This here sounds strange:
| The update rate for any given release should drop off over time,
| approaching zero near release end-of-life; since updates are primarily
| bugfixes, fewer and
On Thu, 2010-09-23 at 03:42 -0400, Orcan Ogetbil wrote:
I think Kevin's proposal is written fairly with the given information.
Still, I believe that the stable update guide needs to be relaxed for
software that doesn't affect anything other than itself. There are
single library packages that
On 09/23/2010 06:18 AM, Thorsten Leemhuis wrote:
Right?
No, because with rawhide you get alpha and beta code. But updating
everything to the very latest thing all the time would mean: User get
what those that know the software best (upstream developers) suggest
their users to use(¹) -- that
On Thu, 2010-09-23 at 08:39 +0200, Till Maas wrote:
On Wed, Sep 22, 2010 at 04:45:30PM -0400, Adam Jackson wrote:
On Wed, 2010-09-22 at 22:21 +0200, Till Maas wrote:
This here sounds strange:
| The update rate for any given release should drop off over time,
| approaching zero near
On Thu, 2010-09-23 at 12:18 +0200, Thorsten Leemhuis wrote:
On 22.09.2010 22:45, Adam Jackson wrote:
Again: if we kept updating everything to the very latest thing all the
time, why even bother doing releases. Everyone would just run rawhide.
Right?
No, because with rawhide you get
On Wednesday, September 22, 2010 10:45:30 pm Adam Jackson wrote:
On Wed, 2010-09-22 at 22:21 +0200, Till Maas wrote:
This here sounds strange:
| The update rate for any given release should drop off over time,
| approaching zero near release end-of-life; since updates are primarily
|
Seems generally reasonable to me.
Is there a definition somewhere of what constitutes a critical path
update?
Eric
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Tue, Sep 21, 2010 at 11:01:04PM -0700, Eric Smith wrote:
Seems generally reasonable to me.
Is there a definition somewhere of what constitutes a critical path
update?
http://fedoraproject.org/wiki/Critical_path_packages#Where_can_I_find_the_critical_path.3F
--
Tomasz Torcz
On Wed, Sep 22, 2010 at 12:35 PM, Tomas Mraz tm...@redhat.com wrote:
On Tue, 2010-09-21 at 15:47 -0600, Kevin Fenzi wrote:
Greetings.
I'd like to ask for feedback and helping cleaning up an updates policy
draft page:
https://fedoraproject.org/wiki/User:Kevin/Updates_Policy_Draft
How can
On Wed, 2010-09-22 at 12:48 +0200, drago01 wrote:
On Wed, Sep 22, 2010 at 12:35 PM, Tomas Mraz tm...@redhat.com wrote:
On Tue, 2010-09-21 at 15:47 -0600, Kevin Fenzi wrote:
Greetings.
I'd like to ask for feedback and helping cleaning up an updates policy
draft page:
On Wed, Sep 22, 2010 at 12:35:01 +0200,
Tomas Mraz tm...@redhat.com wrote:
- Avoid changing the user experence if at all possible. - this is too
strong condition. In some cases fixing a bug might inevitable change the
user experience and in some cases for example the user experience might
On Wed, Sep 22, 2010 at 3:34 PM, Tomas Mraz tm...@redhat.com wrote:
This example is IMO wrong:
- WebKit requires an update to solve a security problem. This requires
updating Midori to a version with some minor menu layout changes. This
would be a judgement call based on how intrusive the
On Wed, 2010-09-22 at 16:09 +0200, drago01 wrote:
On Wed, Sep 22, 2010 at 3:34 PM, Tomas Mraz tm...@redhat.com wrote:
This example is IMO wrong:
- WebKit requires an update to solve a security problem. This requires
updating Midori to a version with some minor menu layout changes.
On Wed, Sep 22, 2010 at 17:01:02 +0200,
Tomas Mraz tm...@redhat.com wrote:
I say that the example of Webkit should be removed because if it is not
possible to backport the security patch and due to the version update
Midori has to be updated to a new version regardless of the changes of
user
On Wed, Sep 22, 2010 at 5:04 PM, Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 17:01:02 +0200,
Tomas Mraz tm...@redhat.com wrote:
I say that the example of Webkit should be removed because if it is not
possible to backport the security patch and due to the version update
On Wed, 2010-09-22 at 10:04 -0500, Bruno Wolff III wrote:
On Wed, Sep 22, 2010 at 17:01:02 +0200,
Tomas Mraz tm...@redhat.com wrote:
I say that the example of Webkit should be removed because if it is not
possible to backport the security patch and due to the version update
Midori has
On Wed, Sep 22, 2010 at 17:27:43 +0200,
drago01 drag...@gmail.com wrote:
On Wed, Sep 22, 2010 at 5:04 PM, Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 17:01:02 +0200,
Tomas Mraz tm...@redhat.com wrote:
I say that the example of Webkit should be removed because if it is
On Wed, Sep 22, 2010 at 17:51:01 +0200,
Tomas Mraz tm...@redhat.com wrote:
Of course, the issue might be very minor, but in that case it is not a
judgement call based on how intrusive thec changes are but judgement
call on whether the pros and cons of doing the update are significantly
in
On Wed, Sep 22, 2010 at 6:31 PM, Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 17:27:43 +0200,
drago01 drag...@gmail.com wrote:
On Wed, Sep 22, 2010 at 5:04 PM, Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 17:01:02 +0200,
Tomas Mraz tm...@redhat.com wrote:
On Wed, Sep 22, 2010 at 18:58:25 +0200,
drago01 drag...@gmail.com wrote:
In case of a security issue a random note somewhere don't do that is
not acceptable ... that's all I am saying here.
You are leaving users at risk by assuming that they will read that
notice (note: most wont).
I
On Wed, 22 Sep 2010 18:14:47 +0100
Alex Hudson fed...@alexhudson.com wrote:
Hey Kevin,
On Tue, 2010-09-21 at 15:47 -0600, Kevin Fenzi wrote:
How can we clarify the language or the layout of the page to be more
clear? Are there places that it could be more like the existing
package
On Wed, 22 Sep 2010 12:12:54 -0500
Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 18:58:25 +0200,
drago01 drag...@gmail.com wrote:
In case of a security issue a random note somewhere don't do that
is not acceptable ... that's all I am saying here.
You are leaving users
On Tue, 21 Sep 2010 21:06:42 -0400
Josh Boyer jwbo...@gmail.com wrote:
You've obviously spent a lot of time thinking about the exceptions. I
think that is good. I would, however, suggest you also include
examples of changes/updates that are not applicable for a stable
release.
Good idea.
On Tue, 21 Sep 2010 17:09:32 -0500
Bruno Wolff III br...@wolff.to wrote:
On Tue, Sep 21, 2010 at 15:47:04 -0600,
Kevin Fenzi ke...@scrye.com wrote:
Greetings.
I'd like to ask for feedback and helping cleaning up an updates
policy draft page:
Do you want feedback on the mailing
On Wed, Sep 22, 2010 at 12:35:32PM -0600, Kevin Fenzi wrote:
So, for example, we have these use cases for Fedora which involves
information working on the desktop, so the guiding principles for the
stable release ought to be about those users being generally happy and
having a desktop that
On Wed, Sep 22, 2010 at 12:35:38 -0600,
Kevin Fenzi ke...@scrye.com wrote:
So, that would be, BAD:
- Changing User interface (moving menu items or buttons around)
- Changing names of commands for command line.
- Changing behavior of command line options (ie, --foo does something
On Wed, Sep 22, 2010 at 12:35:55 -0600,
Kevin Fenzi ke...@scrye.com wrote:
On Tue, 21 Sep 2010 17:09:32 -0500
Bruno Wolff III br...@wolff.to wrote:
On Tue, Sep 21, 2010 at 15:47:04 -0600,
Kevin Fenzi ke...@scrye.com wrote:
Greetings.
I'd like to ask for feedback and helping
On Wed, Sep 22, 2010 at 8:35 PM, Kevin Fenzi ke...@scrye.com wrote:
On Wed, 22 Sep 2010 12:12:54 -0500
Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 18:58:25 +0200,
drago01 drag...@gmail.com wrote:
In case of a security issue a random note somewhere don't do that
is
On Wed, 22 Sep 2010 13:42:14 -0500
Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 12:35:38 -0600,
Kevin Fenzi ke...@scrye.com wrote:
So, that would be, BAD:
- Changing User interface (moving menu items or buttons around)
- Changing names of commands for command line.
On Wed, 22 Sep 2010 13:45:55 -0500
Bruno Wolff III br...@wolff.to wrote:
On Wed, Sep 22, 2010 at 12:35:55 -0600,
Kevin Fenzi ke...@scrye.com wrote:
On Tue, 21 Sep 2010 17:09:32 -0500
Bruno Wolff III br...@wolff.to wrote:
On Tue, Sep 21, 2010 at 15:47:04 -0600,
Kevin Fenzi
On Wed, Sep 22, 2010 at 13:05:23 -0600,
Kevin Fenzi ke...@scrye.com wrote:
ok. I Changed 'Beta' mentions in the Pre Beta section to Alpha or Beta
releases. Does that work?
That looks fine now. Thanks.
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, 2010-09-22 at 12:35 -0600, Kevin Fenzi wrote:
Alex Hudson fed...@alexhudson.com wrote:
I think there's one thing missing: some discussion about the guiding
principles about where these rules came from.
Well, there is the Boards vision that this came out of:
On Wed, Sep 22, 2010 at 20:56:07 +0200,
drago01 drag...@gmail.com wrote:
Might be true but a random notice on some website / mailinglist /
$whatever is NOT a fix. period.
If one decided to use a notification to mitigate a security issue, one would
put the notice where the affected people
On Wed, Sep 22, 2010 at 13:01:49 -0600,
Kevin Fenzi ke...@scrye.com wrote:
Right. Also, added to that is: Are the bug fixes worth shipping to
millions of people? ie, do they fix bugs that Fedora users would/have
encountered.
That's another gray area without much guidance currently. I
On Tue, Sep 21, 2010 at 03:47:04PM -0600, Kevin Fenzi wrote:
I'd like to ask for feedback and helping cleaning up an updates policy
draft page:
https://fedoraproject.org/wiki/User:Kevin/Updates_Policy_Draft
How can we clarify the language or the layout of the page to be more
clear? Are
On Wed, 2010-09-22 at 22:21 +0200, Till Maas wrote:
This here sounds strange:
| The update rate for any given release should drop off over time,
| approaching zero near release end-of-life; since updates are primarily
| bugfixes, fewer and fewer should be needed over time.
This essentially
Greetings.
I'd like to ask for feedback and helping cleaning up an updates policy
draft page:
https://fedoraproject.org/wiki/User:Kevin/Updates_Policy_Draft
How can we clarify the language or the layout of the page to be more
clear? Are there places that it could be more like the existing
On Tue, Sep 21, 2010 at 15:47:04 -0600,
Kevin Fenzi ke...@scrye.com wrote:
Greetings.
I'd like to ask for feedback and helping cleaning up an updates policy
draft page:
Do you want feedback on the mailing list or the Talk page pn the wiki?
--
devel mailing list
On Tue, 21 Sep 2010 17:09:32 -0500
Bruno Wolff III br...@wolff.to wrote:
On Tue, Sep 21, 2010 at 15:47:04 -0600,
Kevin Fenzi ke...@scrye.com wrote:
Greetings.
I'd like to ask for feedback and helping cleaning up an updates
policy draft page:
Do you want feedback on the mailing
On Tue, Sep 21, 2010 at 5:47 PM, Kevin Fenzi ke...@scrye.com wrote:
Greetings.
I'd like to ask for feedback and helping cleaning up an updates policy
draft page:
https://fedoraproject.org/wiki/User:Kevin/Updates_Policy_Draft
How can we clarify the language or the layout of the page to be
99 matches
Mail list logo