IMPORTANT: GUI does not pass qa for release: will not support deployer file export on Monday for ecosystems competition

[Gary Poster]

GUI team, please read this to the end.

Antonio, Jorge, I'm sorry.  Unfortunately the GUI did not pass QA this
evening and it is not of a quality appropriate for a release.  We
encountered one issue, addressed it, and then found two more as the
evening wore on.  It's too much for Friday night.

In general, trying to make a release Friday is a bad idea, and we don't
like to do it.  I did not communicate that to you when I asked you
earlier in the week to give us QA feedback on the new deployer export
functionality, and I apologize for that as well.  We really wanted to
support your important ecosystems deadlines.

On Monday, you will need to communicate to users that the GUI is not yet
ready for the instructions.  If they have a pressing need, they can do
an export by deploying the gui and using "juju set
juju-gui-source=lp:juju-gui".  This will get them trunk, with the errors
I describe below, but a working export functionality that you all have
already tested.

We will work to have a release as soon as possible.  It should be no
later than Wednesday, and hopefully sooner.

As a reminder, I am out Monday, Thursday and Friday of next week.

GUI team, please treat the following three bugs as critical.  They
should be addressed before others, *and interrupting others if
necessary*, in order to get engineering resources.  Once they are
addressed, please arrange for someone to make a 0.7.0 release, again as
a critical task.  I have created kanban cards for all three issues in
the maintenance lane, and we already had a release card.

Thanks to Jeff for his excellent qa discovering these issues.  Also
thinks to him for his help in diagnosing the first one.

1) drag and drop does not work against improv or a live environment.  It
turns out that app/views/topology/importexport.js is only included in
sandbox mode because it is an experimental feature, but in order for
HTML drag and drop to work, you *must* have a drag and drop handler for
dragenter and dragover that prevents default behavior and stops
propagation.  Practically, I suggest moving the following out of
importexport.js and into another topology module (service.js?  Ben or
Matt, suggestions?):

        events: {
          scene: {
            '.zoom-plane': {
              dragenter: '_ignore',
              dragover: '_ignore',
            }
          }
        },

        /**
         * Ignore some of the drag events.
         * @method _ignore
         */
        _ignore: function(box, module) {
          var evt = d3.event;
          evt.preventDefault();
          evt.stopPropagation();
        }

2) Deploying service from drag and drop causes relation positioning
issues: https://bugs.launchpad.net/juju-gui/+bug/1195934 .  That bug has
two variations of instructions to dupe.

I was unable to dupe this unless at least one of the two services were
deployed using drag and drop.  Maybe I missed something though?

3) Deploy two services (any method), pan the canvas, and create a
relation with the popup menu.  The relation line's connections are
broken.  It sounds like Matt has a lead on this one.

Matt and Benji might be good people to tackle these together, though if
they are not around, please volunteer yourself.

Thanks

Gary