Code Freeze for Infusion repo for Infusion 2.0 - Preparing to Tag

Mon Nov 21 16:16:20 UTC 2016

It seems there is some more blocking work that needs to be committed to
Infusion. Initially FLUID-5943
<https://issues.fluidproject.org/browse/FLUID-5943> was expected to be a
documentation only task; however, review has revealed that the code
examples used in the documentation should be moved to an actual Infusion
Example in the Infusion code base. We’ll complete this task, and test it.
In the meantime we’ll be holding off further tag related work.

Thanks
Justin

On November 21, 2016 at 9:43:05 AM, Justin Obara (obara.justin at gmail.com)
wrote:

And that last blocker has been addressed, tested, and merged into master.
We’re ready to continue with our tag prep for the Infusion 2.0 release.

Thanks
Justin

On November 17, 2016 at 12:08:32 PM, Justin Obara (obara.justin at gmail.com)
wrote:

We’re going to take a pause from tag prep to address one more Blocker (
https://issues.fluidproject.org/browse/FLUID-6064 ). This will require a
little bit of retesting, but we don’t feel it will take too long.

Thanks
Justin

On November 16, 2016 at 11:23:28 AM, Justin Obara (obara.justin at gmail.com)
wrote:

We’ve completed the main testing phase for the Infusion 2.0 release. Thanks
to everyone who helped test and fix blockers. The next step will be to
update the Release and README files, and create a tag to test from. Once
this is done we’ll need to do some more testing of the release packages.

Thanks
Justin

On November 15, 2016 at 1:24:19 PM, Justin Obara (obara.justin at gmail.com)
wrote:

The most recent blocker for the build scripts has been fixed and merged
into master.

Thanks
Justin

On November 15, 2016 at 9:47:29 AM, Justin Obara (obara.justin at gmail.com)
wrote:

This morning a blocker was found in the build scripts. This shouldn’t
affect testing, and we’ll aim to have it addressed today.

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

Thanks
Justin

On November 14, 2016 at 12:43:09 PM, Justin Obara (obara.justin at gmail.com)
wrote:

All of the blockers have once again been addressed and full testing is once
again opened. I’ve reset the uploader tests. Please feel free to pick up
some testing tasks from
https://docs.google.com/document/d/1yFJotFr4_HJhNK-kwAxjE4gCozJYu48xIIjkA91gloU/edit?usp=sharing

Thanks
Justin

On November 9, 2016 at 4:14:11 PM, Justin Obara (obara.justin at gmail.com)
wrote:

We’ve uncovered a couple more blockers for the release. A small one for the
textfield slider in the prefs framework and another one for Uploader. Alan
has already filed a PR for the textfield slider issue, and it will be
merged shortly. I’d suggest holding off on any Uploader testing for the
time being though, as we’ll need to redo the testing for it.

Textfield Slider:

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

Uploader:

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

PRs:

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

Thanks
Justin

On November 8, 2016 at 10:39:23 AM, Justin Obara (obara.justin at gmail.com)
wrote:

We’ve merged in the last PRs addressing the remaining blockers. All testing
is open again. Please pick up some testing tasks.
https://docs.google.com/document/d/1yFJotFr4_HJhNK-kwAxjE4gCozJYu48xIIjkA91gloU/edit#

Thanks
Justin

On November 7, 2016 at 9:31:54 AM, Justin Obara (obara.justin at gmail.com)
wrote:

We have managed to address most of the blockers, and testing can now resume
on everything but the Uploader. I’m going to reset some of the tests tasks
as we’ll need to Redo the smoke, progress, and UIO / Prefs framework tests.

Unfortunately while testing out the Uploader PR, we uncovered another
Uploader blocker. I’ll be looking into this one today and hope to have
Uploader testing opened again shortly.

Uploader Blocker:

   - https://issues.fluidproject.org/browse/FLUID-6038
   - https://issues.fluidproject.org/browse/FLUID-6028

PRs:

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

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

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/20161121/73a297ff/attachment.htm>