Updates from July, 2013 Toggle Comment Threads | Keyboard Shortcuts

  • garyposter 3:44 pm on July 26, 2013 Permalink | Reply
    Tags:   

    Jeff: Never assert Y.one(‘.something’) is typeof object.

    null is of type Object and the test is no good. Use “Y.one(‘.something’) instanceof Y.Node” instead (or Y.isValue or even !! for simple assertions).

    We had one issue like this. Jeff will verify that we don’t have any others.

     
  • garyposter 3:40 pm on July 26, 2013 Permalink | Reply
    Tags:   

    handling user requests in IRC: first person to reply claims it; if there is any question, someone can explicitly claim a response; once you have claimed a response, always feel free to ask jujugui for someone to take over.

    bugs: as our first experiment, everyone will fix one bug every two weeks. We will have a lane that collects the bug fixes to be accountable.

     
  • garyposter 2:48 pm on July 26, 2013 Permalink | Reply
    Tags: ,   

    jujucharms.com update 

    Following up on yesterday’s announcement of Juju GUI 0.8.1, today we have a new release of jujucharms.com that includes those fixes.

    It also includes a number of redirects to be largely backwards compatible with existing links. For instance, links from pre-existing questions and from other sources should now work. Also, old links for charm authors and charm reviewers now redirect to the new location, away from http://jujucharms.com to http://manage.jujucharms.com. Examples include http://jujucharms.com/review-queue, http://jujucharms.com/interfaces, http://jujucharms.com/tools/proof-errors, http://jujucharms.com/recently-changed, and http://jujucharms.com/feed/charm-changes. Thank you to Curtis Hovey for arranging this fix!

    In the “two steps forward, one step back” department, unfortunately this release highlighted an issue in our caching directives to the browser . If you have visited jujucharms.com earlier this week, you will initially see some new, unattractive styling. This will naturally clear out of the browser cache in a day or so. To correct immediately, simply do a “hard reload” (shift-control-r) of the browser. We will deploy a fix as soon as possible.

    Thanks,

    Gary

     
  • garyposter 1:14 am on July 26, 2013 Permalink | Reply
    Tags: ,   

    Juju GUI 0.8.1 

    We released Juju GUI 0.8.1 this evening. It fixes a number of bugs.

    • Subordinate charms are now handled correctly in juju core.
    • Fixed bug causing settings page to not scroll.
    • Fixed bug causing the initial loading spinner to spin forever in Firefox with cookies or sessionStorage disabled.
    • Fixed another bug causing the initial loading spinner to spin forever intermittently, rarely.

    We plan to roll these out to jujucharms.com tomorrow morning, US.

    0.8.1 also includes some big progress on upcoming features (search autocomplete, new inspector) but these are hidden behind feature flags. We’ll describe those separately.

     
  • Madison Scott-Clary (Makyo) 2:19 am on July 23, 2013 Permalink | Reply
    Tags: , , OpenStack   

    Deploying OpenStack with Juju and the GUI 

    A small video tutorial on how to deploy OpenStack with Juju using the GUI

     
  • garyposter 7:13 pm on July 22, 2013 Permalink | Reply
    Tags: , ,   

    jujucharms.com and Juju GUI 0.8.0 

    I’m very happy to let you know that we have released the Juju GUI 0.8.0, and that it is powering http://jujucharms.com.

    The GUI itself has a lot of incremental improvements and bugfixes in this release, and the UI is even more beautiful and usable. See the bottom of the post for changelog highlights, and see our installation details if you want to know how to use the GUI in your own Juju environment.

    However, our biggest news to my mind is that we now have a jujucharms.com that really encourages discovery and exploration. You can find charms; read more details about them; and experiment live to see how they interact within a mock Juju environment. You can even (hidden feature, for now!) use shift-D to export your experiments into a human readable format, and use that to turn your experiments into a real running system in your own Juju environment (see the Juju Deployer).

    Charmers, never fear: the features you need from the old site are still around, with some improvements. See http://manage.jujucharms.com/.

    Also, the old GUI demo site, uistage.jujucharms.com, will be retired soon, and redirect to jujucharms.com. Meanwhile, if you want to follow along with our progress on a commit-by-commit basis, you are welcome to join us over at http://comingsoon.jujucharms.com/. You may have to clear your cache regularly on that site, if you keep coming back: we are working through this code quickly. 🙂

    And in that vein, the thing I’m most proud of is being a part of the team that is making this! Big thanks and congratulations to UX (esp. Alejandra Obregon and Luca Paulina), Curtis Hovey’s Orange squad, and the Juju UI team.

    Bugfixes and new features are already in trunk, with more exciting things coming. Thanks for reading.

    Gary

    0.8.0 changelog highlights:

    • Update charm browser styling.
    • Add provider test result data and links
    • Charm browser shows lifetime downloads and commit counts.
    • Update service block design.
    • Fix deployment issues encountered for some charms, e.g. Marco Ceppi’s discource charm.
    • Fix Juju deployer export.
    • More drag and drop deployment refinement and fixes.
    • Many other small bugfixes.
    • Incremental progress on service inspector behind the serviceInspector feature flag.
     
  • bradcrittenden 3:28 pm on July 22, 2013 Permalink | Reply
    Tags: , ,   

    Charm store moves, Juju GUI updated 

    Today the charm store moved to a new URL but the GUI had not been updated to reflect it. You may have seen a JSON parse URL when trying to deploy charms.

    This inconsistency has been resolved and the GUI (bzr revision 69) is now correct.

    Sorry for the inconvenience.

     
  • garyposter 4:10 pm on July 12, 2013 Permalink | Reply
    Tags:   

    Jeff: Weekly releases – new branching approach?

    In past projects we have a stable branch and a dev branch. We could release from stable, and fixes can be applied to old branches.

    Helps with QA of bugfixes.

    Gary, Benji, Matt, Ben: we can get a lot of the advantages on the fly from simply branching from a release tag when we have to.

    Gary, Ben: jujucharms.com might be different.

    Gary: when someone is making a release, only land bug fixes or things behind feature flags?

    Benji: Standard practice: We already tag our releases. Whenever you make a bugfix release, make a branch.

    All agree that this is sufficient for the biggest issue. Gary will add a card to discuss future jujucharms.com release plans/schedule.

     
  • garyposter 3:49 pm on July 12, 2013 Permalink | Reply
    Tags:   

    Jeff: Please always push your branch to LP at end of day and week so others can share/see

    Gary: good for cross-timezone cooperation as well as weekends

    • Ideally we land our branches end of day
    • Next, ideally we land our branches end of week
    • If not push at end of day/week so others can see/share/contribute
     
  • garyposter 3:46 pm on July 12, 2013 Permalink | Reply
    Tags:   

    Gary: Friday release failure (0.7 stuff) five whys

    Problem was that we were unable to make a fast release from trunk because of multiple qa issues in non-feature-flagged behavior.

    • Problems were not discovered sooner
    • Insufficient continuous QA procedure
    • The qa procedure in our review process is not sufficient
    • We don’t have a well defined or sufficient exploratory/aggressive QA step for branch reviews

    Possible solutions:

    • Weekly exploratory testing must happen
    • We require better in-depth exploratory testing of branches

    Another five-whys branch

    • Problems were not discovered sooner
    • Insufficient continuous QA procedure
    • landing things incrementally makes it difficult to identify when exploratory testing is appropriate

    Somewhat related issues

    • We released on Friday

    Proposal for solution:

    • weekly half hour to hour exploratory testing using both sandbox and improv (real environment nice to have).
    • bugs that block release are marked critical.
    • we release every other week.
    • Gary will not request another Friday release 😛
     
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