Code Freeze for Infusion repo for Infusion 2.0 release testing, testing help requested

Justin Obara obara.justin at
Tue Nov 1 20:21:44 UTC 2016

We just merged the last PR that addresses Infusion 2.0 blockers. We’re
ready to test Infusion again for the 2.0 release.

Despite the PRs touching many files, the changes were generally minor and
tended to focus on styling and markup. In general this means that we don’t
have to redo much of the testing; however, I have reset all of the smoke

If you are able to help with testing, please feel free to grab testing


On October 28, 2016 at 9:44:30 AM, Justin Obara (obara.justin at

The blockers mentioned yesterday have all been addressed, however the
validation sprint uncovered some more issues that have resulted in the
following blocking issues:


We aim to have address these as quickly as possible so that testing for the
release can resume.


On October 27, 2016 at 11:09:30 AM, Justin Obara (obara.justin at

During yesterdays testing we encountered a few blockers.

We’ll be merging pull requests to address these blockers.

We are also going through all of the demos and examples to run the
validation step and do smoke testing to catch any other blocking issues.


On October 25, 2016 at 1:03:14 PM, Justin Obara (obara.justin at

Hi everyone,

We’re getting closer to an Infusion 2.0 release. We’ve merged in all of the
code changes and PRs for Infusion 2.0 and are ready to start testing. Until
an Infusion 2.0 tag is cut, the Infusion github repo
<> should be considered frozen.
The only changes that will be permitted are for the following:

   - fixes for blockers found during testing
   - Updates to the README and Release notes
   - Tagging the release

As with all of our releases, there are quite a few testing tasks to be
completed across our supported browsers. We’ll need to go through all of
these tests and ensure that no blocking issues are found, before we can
release. Our goal is to tag a release by the end of this week ( Friday, 28
Oct 16 ), but it’s unlikely we’ll be able to achieve this time frame
without help from our community. I have setup a google doc to help track
which tasks are being worked on and what has been completed.

Thank you for all of the help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fluid-work mailing list