Updates from September, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • garyposter 4:03 pm on September 27, 2013 Permalink | Reply
    Tags:   

    Bugs vs Kanban 

    Problem statement: Our bug tracker does not track our work well.

    Response: Yes, we think this is OK.

    Proposed policy:

    We make kanban cards for actions that should happen soonish, honoring the limits we’ve placed on non-feature card count so that we keep the kanban moderately gardened.

    As always, we may file bugs for cards if we want more room to discuss, or if we want to upload artifacts, or if we want to use it as a broadcast mechanism.

    We do file bugs for issues that we want to acknowledge but are not scheduling to address.

    Bugs are a way to communicate to us.

    All new bugs should be triaged in order to encourage good customer relations.  We need to address this.

    If team members file a bug, they should immediately triage it or arrange for it to be triaged.

    There are only three bug prorities we use: critical (hair is on fire! immediate action!), high (we have scheduled it and/or are tracking it on the kanban board), and low (we acknowledge it but have not scheduled it).

    We don’t care about milestones, or associating bugs with milestones.  Our release notes are where we communicate progress to deeply inserested customers.

    Next steps:

    We should come up with a mechanism to make sure that new bugs are triaged.

    We need to bring this up with Rick.

     
  • garyposter 9:49 pm on September 18, 2013 Permalink | Reply
    Tags: ,   

    Juju GUI 0.10.0: A big release 

    We’re very happy to announce the release of Juju GUI 0.10.0.  It has a big change that we are very excited about: the new service inspector.

    InspectorThe inspector lets you look at services and units while still keeping an eye on the bigger context.  It also gives you a more dynamic view than ever before on a changing environment.  Changes to services and units are visible immediately in the inspector.  If you are editing  a value, the inspector can even help you identify conflicts between your choices and a concurrent change from the environment.  You can quickly view the details of the service’s charm, or a unit’s status.  And it is designed to let us bring you even more features in the future.

    If you’d like to take a quick look now, https://jujucharms.com/ can give you a preview.  Once you are ready to use it in your own environment, follow the simple deployment instructions and give it a try.

    We hope you enjoy the new release.  More great things are coming soon.

     
  • garyposter 3:49 pm on September 13, 2013 Permalink | Reply
    Tags:   

    Jeff: Call toArray() on lazy model lists when they are in an object you call deepEqual on.

     
  • garyposter 3:39 pm on September 13, 2013 Permalink | Reply
    Tags:   

    How can we make releases easier?

    Jeff: Like node and juju, odd releases are unstable.
    Gary: we already have a devel release series.
    Gary: We have some pretty good release automation. qa cost is the problem.

    Result: Gary will set up daily exploratory qa rotation. Using juju core is recommended, and using IE 10 is recommended. Goal is to send an email with at least one new bug. We will evaluate effectiveness in San Fran meeting.

     
c
Compose new post
j
Next post/Next comment
k
Previous post/Previous comment
r
Reply
e
Edit
o
Show/Hide comments
t
Go to top
l
Go to login
h
Show/Hide help
shift + esc
Cancel