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

[Justin Obara]

We’re making progress on addressing the blockers mentioned last time. We
have addressed 3 of the 6 blockers, and the rest have PRs that are making
their way through review. However I’ve just come across another blocking
issue with the Progress component. This means that we’ll be holding on
testing for anything related to Progress as well.

Progress Blocker:

   - https://issues.fluidproject.org/browse/FLUID-6032



PRs:

   -
   https://github.com/fluid-project/infusion/pulls?q=is%3Aopen+is%3Apr+milestone%3A%22Infusion+2.0+Release%22



Thanks
Justin


On November 2, 2016 at 4:39:03 PM, Justin Obara (obara.justin at gmail.com)
wrote:

The good news is that testing is successfully catching issues, the bad news
is that we’ve uncovered some more blockers for the Infusion release. These
are all related to the Uploader and to the Prefs Framework. We should pause
testing on anything related to the Uploader and Prefs Framework, but can
continue with testing the rest of Infusion.

Uploader Blockers:

   - https://issues.fluidproject.org/browse/FLUID-6025
   - https://issues.fluidproject.org/browse/FLUID-6027
   - https://issues.fluidproject.org/browse/FLUID-6028

Prefs Framework related Blockers:

   - https://issues.fluidproject.org/browse/FLUID-6017
   - https://issues.fluidproject.org/browse/FLUID-6018
   - https://issues.fluidproject.org/browse/FLUID-6020

Thanks
Justin



On November 1, 2016 at 4:21:44 PM, Justin Obara (obara.justin at gmail.com)
wrote:

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
tests.

If you are able to help with testing, please feel free to grab testing
tasks:
https://docs.google.com/document/d/1yFJotFr4_HJhNK-kwAxjE4gCozJYu48xIIjkA91gloU/edit?usp=sharing

Thanks
Justin


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

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

   - https://issues.fluidproject.org/browse/FLUID-6008
   - https://issues.fluidproject.org/browse/FLUID-6011

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

Thanks
Justin




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

During yesterdays testing we encountered a few blockers.

https://issues.fluidproject.org/browse/FLUID-5993
https://issues.fluidproject.org/browse/FLUID-5994
https://issues.fluidproject.org/browse/FLUID-6000

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.

Thanks
Justin

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



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
<https://github.com/fluid-project/infusion> 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.

https://docs.google.com/document/d/1yFJotFr4_HJhNK-kwAxjE4gCozJYu48xIIjkA91gloU/edit?usp=sharing

Thank you for all of the help.
Justin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20161104/e2e273f7/attachment.htm>