ubuntu-phone team mailing list archive

[Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>]

Hi Robert!

Now that's an unexpected Christmas present - you didn't mention anything
about it on yesterdays meeting! Good work :)

The task transition doesn't seem to be completely finished though, but I
guess I'll pick this up and try making everything cleaned up. For
instance, there are duplicates of tasks now which were in the Landing
Asks and already set in Landing Plan (like ubuntu-settings-components or
ubuntu-system-settings).

Also, Martin does have some good points - at least let's try including
all useful information in the bug description. Not sure about assigning
existing bugs to landing-plan, as I would personally prefer those to be
separate, only with links to useful information. This way it would be
easier for us to manage bugs and iterate through them using mostly
descriptions.
I will also add some of the links as the description of the project.

I'll also try to include some other information, such as what status
means what. Any bug that's Triaged means that it has been scheduled for
release in the nearest slot. In Progress means it's worked on, Fix
Committed - that it's pushed to the archive and Fix Released when it's
in the image. It would be nice it with the switch to Fix Released we
would - for now manually - add a comment to the bug in which image
number the component was released.

Generally, access rights to submit bugs in this project should be
restricted only to team managers and the landing team - so please follow
the same rules as before. If you want something landed, please poke your
manager to include a landing-plan bug for us to pick it up.

Thanks!

On 18.12.2013 00:42, Robert Park wrote:
> Hello all,
> 
> As was decided at the sprint in Oakland, the landing plan spreadsheet
> is very deficient and should be replaced with standard, existing
> tools.
> 
> So instead of complaining about the lack of progress in this area, I
> decided to JFDI:
> 
> https://bugs.launchpad.net/landing-plan
> 
> I did my best to copy the information from the existing landing plan
> into new bugs here.
> 
> So from now on, the workflow should look like this:
> 
> When you want to request a new release of your project, you file a
> bug[0] against landing-plan. Please include the name of the launchpad
> project you want released, and a short blurb about why (what bug it
> fixes, or what feature it implements).
> 
> Then, the landing team will review your request and then assign
> somebody to build, test, and publish your release.
> 
> You can use launchpad advanced searches to approximate the old
> "Landing Asks"[1] and "Landing Plan"[2] spreadsheets.
> 
> The landing team can then report our progress on the bugs, in a way
> that creates a much more readable history, eg, no more random
> spreadsheet cells that say "I am working on this" with no indication
> of who "I" refers to.
> 
> I was careful not to delete any information from the spreadsheet in
> case I made a mistake when I created so many new bugs, but from now on
> please use landing-plan bugs instead of that awful spreadsheet.
> 
> Thanks!
> 
> [0] https://bugs.launchpad.net/landing-plan/+filebug
> [1] http://goo.gl/ejmIZa
> [2] http://goo.gl/7XcHjt
> 


-- 
Łukasz 'sil2100' Zemczak
 lukasz.zemczak@xxxxxxxxxxxxx
 www.canonical.com