We agreed to change how we triage bugs and manage milestones to make
it easier to focus on our current and next priorities.
We will maintain a list of 75 high bug, a single page listing on Lp.
We will manage 4 milestones:
Current stable point (1.18.3):
Deploying wordpress to the local provider on trusty deploys the precise
version of wordpress (the only version available), which hits this bug
during the install hook:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969299
The key line is this error from the install hook's code:
failed to
Nate,
last I heard about the wordpress charm it was under an active rewrite to
python to leverage charm-helpers. Not the best answer in the universe, but
a new cut is on the horizon. have you opened a bug against the existing
wordpress charm in it's current form so someone can pick up that banner
No, but I will. Wanted to make sure I wasn't missing some easy solution, or
if there was already something reported somewhere. My launchpad-search-fu
is not the best. I'll report it.
On Thu, May 8, 2014 at 3:17 PM, Charles Butler charles.but...@canonical.com
wrote:
Nate,
last I heard
FYI: https://bugs.launchpad.net/charms/+source/wordpress/+bug/1317644
On Thu, May 8, 2014 at 3:20 PM, Charles Butler charles.but...@canonical.com
wrote:
Much Appreciated!
On Thu, May 8, 2014 at 3:19 PM, Nate Finch nate.fi...@canonical.comwrote:
No, but I will. Wanted to make sure I
So I think a couple of the key flows are
1) next-stable is intended to be a list of bugs that get burned down, so to
move a bug into next-stable, you should really take a different bug out
2) the 75 high bugs are intended as a pool that we will try to stay aware
of. So as we move bugs out of here
