On Mon, Apr 8, 2013 at 12:45 PM, John Lea wrote:
> Currently the shell engineering related to the legacy nux/compiz version of
> Unity is handled inside https://launchpad.net/unity and the shall
> engineering related to the QML/MIR 'Unity Next' shell happens inside
> https://launchpad.net/manhatta
Hi Omer,
Currently the shell engineering related to the legacy nux/compiz version
of Unity is handled inside https://launchpad.net/unity and the shall
engineering related to the QML/MIR 'Unity Next' shell happens inside
https://launchpad.net/manhattan so at the moment there isn't any
crossove
So what becomes of the existing Unity bugs that we have in launchpad? From
what i know the launchpad project for Unity is going to be the same i.e.
launchpad.net/unity so new bug tracking will become difficult to handle.
Should we discuss something on that ?
On Mon, Apr 8, 2013 at 6:28 PM, John L
Hi All,
In order to track the design status of bugs across the Unity Next
project, we are looking to introduce a design bug tracking process that
is very similar to the workflow used very successfully in the 12.04 cycle.
The details of this new process are written up in a google doc, see
htt
4 matches
Mail list logo