Ugh - where's my head these days. We should be running QA off a frozen version which means that I should have tagged infusion already. We are going to have to run QA again. If you are ok with the Reorderer bugs in the the Decapod release, I'll tag now and rerun QA. If not, we'll wait for the merge, then I'll tag and then we can run QA. It's probably best to tag now since the changes in the merge are going to be major. Sound ok?

Michelle


On 30-Mar-10, at 10:25 AM, Jonathan Hung wrote:

Michelle,

How does this affect the tagging and releasing of Decapod?

Decapod isn't majorly broken with this bug, so should we still cut a Decapod 0.3 tag? (assuming rest of testing passes).

- Jonathan.

---
Jonathan Hung / [email protected]
Fluid Project - ATRC at University of Toronto
Tel: (416) 946-3002


On Tue, Mar 30, 2010 at 10:08 AM, Justin Obara <[email protected]> wrote: That is pretty unfortunate. If it is something that we won't be able to fix soon, we may want to cut a tag of infusion before merging the jQuery upgrade into trunk. Engage could be linked to this tagged version of infusion.

Any thoughts on this? I suppose if we go this route, we wouldn't be releasing an 0.3 version of Engage until we release a 1.3 of Infusion.

- Justin


On 2010-03-30, at 9:57 AM, Yura Zenevich wrote:

I have tested new versions of jQuery and jQuert UI yesterday with Engage and it doesn't seem to work with our version of env.js anymore. So it might require extra caution when updating Infusion trunk so Engage trunk doesn't brake.

Yura

On Tue, Mar 30, 2010 at 9:50 AM, Michelle D'Souza <[email protected] > wrote: Justin is merging a branch with a jquery upgrade and changes to the reorderer today. It might be worth waiting until after the merge to test this again.



http://issues.fluidproject.org/browse/FLUID-3391

6. Reordering images with keyboard doesn't respond to initial actions; need to attempt twice before it's successful. To replicate: take three pictures, select second image, press ctrl-up--image is highlighted in reorder mode but does not move; keep holding ctrl and press up again, and it will actually move up.

7. After reordering with keyboard, image still appears to be in reordering mode (visually, not functionally). To replicate: take a picture, select image, press ctrl-up, let go; selected image is appears to be in reorder mode.

Re: 6 and 7

This is strange because it wasn't always like this. In earlier versions of Decapod keyboard reordering worked as expected. This could be a problem with the Fluid Reorderer.

(Just checked the Fluid build server. It seems it's happening there as well. Will file an appropriate bug if one doesn't already exist).


Thanks again for the testing help!

- Jon.

--
You received this message because you are subscribed to the Google Groups "Decapod" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected] . For more options, visit this group at http://groups.google.com/group/decapod?hl=en .

------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre


_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work


_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work


_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work



------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre

_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to