Today I did a follow-up to Tim's review of the ForgeRock charms for
OpenAM and OpenDJ [1]. I noted two items that need to be improved:
required config options causing error state instead of simply
blocking, and better handling of the requirement of a full domain name
as opposed to an IP address.
Hi,
Any news? It's been a month now, and I see other applications from the
same time frame went through.
What's wrong?
- Chris
On Tue, Sep 30, 2014 at 8:47 PM, Charles Butler
charles.but...@canonical.com wrote:
Greetings Chris,
as you have sealed a solid 2 +1's from the ~charmers team we
On Mon, Oct 27, 2014 at 9:05 PM, Jesse Meek jesse.m...@canonical.com wrote:
Is possible and preferable to show the most recent diff by default?
If you mean instead of showing the reviews page by default,
ReviewBoard doesn't support that out of the box. Certainly we could
customize RB to do so,
On Mon, Oct 27, 2014 at 9:26 PM, John Meinel j...@arbash-meinel.com wrote:
What are the tables we're wanting to filter? (charm storage because of its
size?)
The presence DB and a new one for backups. We actually do want to
back up the blobstore DB (charms/tools).
Certainly 3 and 4 aren't
We have a few windows dependencies that are not (and in some cases can not
be) imported for the linux build. Luckily, the windows dependencies are a
strict super set of the linux dependencies, so we can still use godeps to
create dependencies.tsv, just by setting GOOS first, thusly (from the root
can we please just have make dependencies.tsv do the right thing so we
don't have to remember which set of flags and env vars we need to use this
time?
I'm also not 100% sure that we'll have even downloaded all the windows
dependencies if they are a strict superset given that you are running go