Re: Application of UIFEs

2012-10-14 Thread John Lea

On 05/10/12 12:11, Matthew East wrote:

On 5 October 2012 11:54, John Lea  wrote:

Forwarding to ubuntu-release,ubuntu-doc,and ubuntu-translators at Iain
Lane's suggestion.


 Original Message 
Subject: Application of UIFEs
Date: Fri, 05 Oct 2012 11:28:19 +0100
From: John Lea 
To: product-strat...@lists.canonical.com
CC: Sebastien Bacher , Didier Roche
, Jason Warner ,
iain.l...@canonical.com, kate.stew...@canonical.com, Cristian Parrino



Hi All,
Over the past week there have been a couple of cases where bug fixes
have been IMHO incorrectly marked as requiring UIFEs.
UIFEs are an important process step to make sure that string changes are
translated and that users reading documentation are not confused.
However visual bug fixes that do not involve string changes or bug fixes
will not cause any user confusion if the documentation is not updated
should not require a UIFE.

Please also take into account that documentation includes screenshots,
which are invalidated by changes to how the desktop or its components
look visually. We used to have two separate freezes, one involving
changes to strings, another involving changes to the user interface.
These have now been combined into a single "User Interface Freeze",
which applies to both types of change. I appreciate that not all
design changes will invalidate screenshots, but many of them have the
potential to, so this should be borne in mind as this discussion
proceeds.


Yes, I think it is exactly the question of what impact visual changes 
have on screenshots that needs clarification.


Do we fix the 'pixelated app icons in the App Lens' bug even if this 
would mean that the implementation would be slightly different from the 
screenshot in the documentation?


Would any users be confused by this difference?

If we have to choose between:

a) fixing a visual bug in the Ubuntu interface (which is seen by all our 
users every day)


b) not fixing the bug in the Ubuntu interface so that the documentation 
screenshots are 100% consistent with the implementation.


Which is the right choice?




This release has been absolutely horrendous from the point of view of
respecting freezes. Whatever solution is adopted, it is important that
there is not a general expectation that freezes are made to be broken
as there is a last minute rush to introduce fixes which could and
should have been raised much earlier.


Agreed about respecting freezes, but respecting freezes is a different 
discussion.


Even if new features get landed on time, there will always be bugs, so 
these questions would still be relevant.  Of course if the new features 
had landed earlier this cycle we would have had more time to fix bugs, 
but there will always be some bugs.





Matt



--
Ubuntu-release mailing list
Ubuntu-release@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-release


Fwd: Application of UIFEs

2012-10-14 Thread John Lea
Forwarding to ubuntu-release,ubuntu-doc,and ubuntu-translators at Iain 
Lane's suggestion.



 Original Message 
Subject:Application of UIFEs
Date:   Fri, 05 Oct 2012 11:28:19 +0100
From:   John Lea 
To: product-strat...@lists.canonical.com
CC: 	Sebastien Bacher , Didier Roche 
, Jason Warner , 
iain.l...@canonical.com, kate.stew...@canonical.com, Cristian Parrino 





Hi All,

Over the past week there have been a couple of cases where bug fixes
have been IMHO incorrectly marked as requiring UIFEs.

UIFEs are an important process step to make sure that string changes are
translated and that users reading documentation are not confused.
However visual bug fixes that do not involve string changes or bug fixes
will not cause any user confusion if the documentation is not updated
should not require a UIFE.

Two of the examples from last week are:

#1043808 - Preview activation doesn't have instant feedback

#1052513 - 'More suggestions' icons in App Lens are too large

In the case of the first bug, although adding a loading spinner is a
visual change, if the documentation is not updated users will not be
confused.  This change also has no translation impact.

In the case of the second bug, making the 'More Suggestions' app icons
in the App Lens the correct size and thus fixing the bad pixelation will
again not confuse users even if the documentation is not updated, and
also this bug fix has no translation impact.

Over zealous application of the UIFE rules increases the likelihood that
fixes to bugs like these will not land in Quantal.  I hope that we can
take a more pragmatic approach when considering which bugs do or do not
require a UIFE, and consider the total impact on all Ubuntu users of
landing or not landing a bug fix, and not just the documentation impact.

For example should we choose:

a) perfectly consistent documentation with badly pixelated app icons in
both the documentation and the App Lens for the Quantal cycle.

b) to fix this bug in the App Lens even though the documentation would
then become slightly inconsistent with the implementation?

A yardstick to help make this choice could be "will the user be confused
by this documentation inconsistency".

Of course the root cause of these problems is how late all the features
have been landing this cycle.   Ideally all the features that are
landing into a release should be complete by Feature Freeze; this would
then give us enough time to really reduce the number of bugs we are
seeing at this point in the cycle.  However this is a different (and
also very important) discussion.

cheers,
John








-- 
Ubuntu-release mailing list
Ubuntu-release@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-release