Here's a +1 minus the 'explicit' language some have requested ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
[FFE] New Unity stack
To manage notifications about this bug go to:
So there we are.
Can you outline how this is planned to land please? Which packages will
have to be uploaded, NEWed, MIRed and seeded?
Can I help this go more smoothly?
** Changed in: unity-lens-shopping (Ubuntu)
Status: Won't Fix = Triaged
** Changed in: gwibber (Ubuntu)
Status:
@Iain: see the description, I took great care in the previous days to
try to answer that in advance, do you see information missing?
I've updated with today's list and progresses.
** Description changed:
A new version of Unity, libunity APIs, the default and new 100 scopes,
with a target
One thing to note is that if a FFE is granted for this change, the FFE
will need to include covering the inevitable bugs that will be spotted
and need to be fixed after this feature lands. Design has not yet been
able to do any end to end testing of this feature, and after we start
testing it is
** Also affects: unity-lens-music (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gwibber (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity-lens-photos (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unity-lens-shopping
The release team has already said no. It only gets in now on a sabdfl
exception if one is provided.
** Changed in: gwibber (Ubuntu)
Status: New = Won't Fix
** Changed in: unity-lens-music (Ubuntu)
Status: New = Won't Fix
** Changed in: unity-lens-photos (Ubuntu)
Status:
@ScottK: I'm just updating the list with impacted components to have all
infos on it. No need to be rude.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
[FFE] New Unity stack
To
Since when is setting correct bug status rude? I thought I was helping?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
[FFE] New Unity stack
To manage notifications about this bug
My remark was more on your comment than the bug status change The
release team has already said no.. Like if adding components was not
needed.
But anyway, no need to bikeshed on this I guess :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ah. That was done first as a reply to the previous comment and LP
lumped it in with the later status changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
[FFE] New Unity stack
To
Scott, I have pinged Mark to weigh in. He is however travelling and it
might be a while (Mo?) for his +1, jfyi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
[FFE] New Unity stack
** Description changed:
A new version of Unity, libunity APIs, the default and new 100 scopes,
with a target date of March 25th for landing in Raring.
For reference, the new smart scope service and corresponding Unity
changes was discussed here:
** Description changed:
A new version of Unity, libunity APIs, the default and new 100 scopes,
with a target date of March 25th for landing in Raring.
For reference, the new smart scope service and corresponding Unity
changes was discussed here:
I have the same question as ScottK We ran into this same issue when
we approved a Feature Free Exception last release which landed the
Amazon feature. Are we going to make exceptions to our development
process every cycle?
--
You received this bug notification because you are a member of
Today is March 13th. Feature Freeze was March 7th. User Interface Freeze
is March 21st. A target date of March 25th is unacceptable. Wasn't the
daily build capability introduced this cycle for all raring components
supposed to help with this?
A major problem with landing dramatic UI changes at or
re #2 #3:
it's a sabdfl request and we are working on the server/client
integration atm. There was some ambiguity around the rolling release
cadence and we were mislead to think that we would deliver into 13.04+n
(n6;). The plan state in the initial comment takes addresses quality
concerns,
re #4: is there a way to provide you with screenshots upfront or help
the situation in another way
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
[FFE] New Unity stack
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libunity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-lens-applications (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-lens-files (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
If this is to be sabdfl'ed, the process is to have Mark explicitly say
so as a comment here. Until then, don't consider this as approved in any
way.
As I said on IRC, I really don't like the idea of this landing so late,
especially as we've clearly said at UDS and in past FFe for Unity that
we
** Changed in: libunity (Ubuntu)
Status: Confirmed = New
** Changed in: unity-lens-applications (Ubuntu)
Status: Confirmed = New
** Changed in: unity-lens-files (Ubuntu)
Status: Confirmed = New
** Changed in: unity (Ubuntu)
Status: Confirmed = New
--
You received
** Description changed:
A new version of Unity, libunity APIs, the default and new 100 scopes,
with a target date of March 25th for landing in Raring.
For reference, the new smart scope service and corresponding Unity
changes was discussed here:
** Description changed:
A new version of Unity, libunity APIs, the default and new 100 scopes,
with a target date of March 25th for landing in Raring.
For reference, the new smart scope service and corresponding Unity
changes was discussed here:
** Description changed:
A new version of Unity, libunity APIs, the default and new 100 scopes,
with a target date of March 25th for landing in Raring.
For reference, the new smart scope service and corresponding Unity
changes was discussed here:
I think this is exactly the kind of update we agreed we would not
approve when we moved feature freeze later in the cycle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154229
Title:
[FFE] New
Agreed. I thought that was well understood. FF was moved back to allow
everything big to land before it.
** Changed in: unity (Ubuntu)
Status: New = Won't Fix
** Changed in: libunity (Ubuntu)
Status: New = Won't Fix
** Changed in: unity-lens-applications (Ubuntu)
Status:
Jeremy, the justification for UIFreeze has always been providing a
stable target for documentation authors and translators, it is NOT
because we believe there will be inevitable UI issues that require
further freeze-breaking fixes. If the change is justifiable in terms of
Feature Freeze, the
Steve,
Although you are correct, I think it's reasonable to extrapolate from previous
experience and expect that the U/I in this next stack won't be final and so
screen shots would have to be redone at an indeterminate later point. To the
best of my recollection that's been pretty
** Description changed:
- A new version of Unity, libunity APIs, the default and new 100 scopes.
+ A new version of Unity, libunity APIs, the default and new 100 scopes,
+ with a target date of March 25th for landing in Raring.
For reference, the new smart scope service and corresponding
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
32 matches
Mail list logo
