OpenMRS 2.2 Release Delayed

[Sri Maurya Kummamuru]

Hello All,

Our goal is to release OpenMRS biannually, each March and September. We apologize for not being able to meet our scheduled time of March, 2015 of OpenMRS 2.2 release.

As you all are aware we were recently set up a user acceptance testing(UAT) server  to let users test OpenMRS 2.2. Thanks to the community volunteers, we were able to uncover bugs that significantly broke existing module's functionality. 

All of the issues are being actively looked into by our community members. The major reason for these issues being the transition from 1.10.x for 2.x releases to 1.11.x for a 2.2 release. Though we were able to release all the planned modules. We were not able to fit in an extensive testing period.  

We found these issues in only 2 days of testing. Generally, we don't find major bugs in UAT, as all modules release bug fixes in the new release and every old functionality is already tested. This time we need to make sure all the modules are compatible with 1.11.x(1.11.0 was released earlier and planned to be included but,1.11.1 has been recently released with major bug fixes) and this cannot be made sure in a couple of days and needs some more rigorous testing. 

In order to deliver a more reliable product, we are extending our testing period indefinitely (we think it would be around 1 week but it can be more or less) and it depends on the community to decide how soon we can release OpenMRS 2.2. We need our community to dig into the UAT server and test out every function they are familiar with and see that it is functioning perfectly.

To make sure we have tested each module/functionality, we need your help:

• If you are a module owner/maintainer please check your module's functionality against 1.11.x setup in the UAT. If you encounter any issues please create a jira ticket and after it gets fixed please release a new version as soon as possible.
• If you are an OpenMRS community member familiar with OpenMRS or would like to get familiar with it. Please help us test the release and see if you encounter any issues in the UAT server.

We would like to track our testing progress through this globally editable google spreadsheet. Link: https://docs.google.com/a/openmrs.org/spreadsheets/d/16KjY5jjT94JkJ2rYvTwwMI_RfScbdyey1SX1OGDCJwg/edit?usp=sharing

 All you have to do is:

• look at the modules/functionality you are familiar with in the Spreadsheet, 
• test it out in the UAT 
• enter your OpenMRS ID in the corresponding cell. 
• If you find any issues you can reply to this talk post
   
   -https://talk.openmrs.org/t/openmrs-2-2-uat-issues-bugs/1536
   
   and we will try to resolve it. 

Based on the response we get, we will be picking a release date for OpenMRS 2.2. As always, this is a community effort and let's work towards releasing OpenMRS 2.2 as soon as possible.

Thank you.

Sri Maurya Kummamuru,

OpenMRS 2.2 release manager, 

On behalf of OpenMRS

[Darius Jazayeri]

@Maurya,

I think this is a great choice. Especially since we didn't have the same level of testing by implementations for OpenMRS 1.11 as we've had with prior releases, this is a good way to ensure that we are releasing a reliable product. (Note: the google spreadsheet isn't globally-editable. I needed to request permission.)

@Contributors to modules that are bundled with OpenMRS 2.2,

Most of you have probably not explicitly tested your modules against OpenMRS 1.11.x. Thanks to hard work by Maurya and the infrastructure team, your module is now running in a realistic UAT environment, against OpenMRS 1.11.1. I'd like to ask to please this week thoroughly test your module on the uat01 server, and find any bugs that were introduced due to openmrs-core 1.11.x. You are the ones who can best find these bugs, and it's important that we quickly understand the scope of what might still be broken.

Two examples that show specific things to look for: (1) the reporting module's UI was completely broken by our change to the default value of spring:htmlEscape. Just a one-line fix! (2) the EMR API module's concept searching was broken by the fact that ConceptWord was removed from the API. Rafal is working on this.

@Everyone,

The changes in OpenMRS Platform 1.11 broke quite a few things, and more than usual we need people to go back and test existing functionality that was working fine in OpenMRS 2.1 to make sure we don't regress in the 2.2 release. If you have the time, please help us test. This can be as easy as testing the happy path functionality described in the OpenMRS 2.2 instructions.

Help us get bugs identified quickly, so we can solidify the code, and get this release out the door in a state we can be proud of, without too much delay.

Thanks,

Darius

--
OpenMRS Developers: http://om.rs/dev
Post: d...@openmrs.org | Unsubscribe: dev+uns...@openmrs.org
Manage your OpenMRS subscriptions: http://om.rs/id
 
*** THIS GROUP IS MOVING to OpenMRS Talk effective 10 April 2015 at 19:00 UTC. Please visit https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508 for details and to make necessary changes.

[Sri Maurya Kummamuru]

Thank you for the Note Darius, I just made the change to be globally editable and also sent out an invitation for the group just in case.

[Rafal Korytkowski]

I have fixed https://issues.openmrs.org/browse/HTMLWIDGETS-21 and https://issues.openmrs.org/browse/EA-60. 

Is it good time to release fixed versions of htmlwidgets and emrapi to update uat01? Or are there any other issues that we need to address prior to that?

-Rafał

[Daniel Kayiwa]

Am not aware of any other issues. So i would say go ahead and release.

If we later on find anything new that needs to be fixed, we shall just hit the release from bamboo magic button. :)

*** THIS GROUP WILL BE MOVED to OpenMRS Talk effective 10 April 2015 at 19:00 UTC. Please visit https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508 for details and to make necessary changes.

To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@openmrs.org.

--

If we keep uppermost in our minds the unkind and unjust acts of others, we shall find it impossible to love them as Christ has loved us; but if our thoughts dwell upon the wondrous love and pity of Christ for us, the same spirit will flow out to others.

[Rafal Korytkowski]

Okay, I've released htmlwidgets and emrapi. uat01 can be updated to use them (I can't do it).

-Rafał

[Burke Mamlin]

Maurya,

What are the blockers for releasing OpenMRS 2.2?  Here are the things I know about:

• Outstanding tickets – do we have a list or dashboard for tracking these?
• We discussed some outstanding tickets on Monday's design call (notes here).  It looks like half are waiting to be closed and the other half are still waiting for a decision.
• Darius suggested there may be additional tickets blocking 2.2.
• We need to test features and modules (so far ~4 of 37 tested).
• We need to get the OpenMRS 2.2 Release Notes ready.
• Pick a new release date.

I'm hoping we can get 2.2 released in early April (next week or, worst case, the following week). Do we need to make the next week a 2.2-a-thon (all hands on deck)?

Cheers,

-Burke

[Sri Maurya Kummamuru]

Burke,

As an update:

•  outstanding tickets: https://issues.openmrs.org/issues/?filter=14152
  
• Testing to be done - This might need all hands on deck next week
• Release Notes - I will work on this today.
• Pick a new release data - This will depend on the response on testing

[Sri Maurya Kummamuru]

Hello Rafal,

I apologize for the delay, I just updated the UAT to use the new build. Just as a confirmation all of those modules are released in the snapshot version for testing right?

--Thanks,

Sri Maurya Kummamuru

On Wed, Apr 1, 2015 at 7:55 AM, Rafal Korytkowski <ra...@openmrs.org> wrote:

[Rafal Korytkowski]

Maurya, I released htmlwidgets 1.6.8 and emrapi 1.6. I also made sure referenceapplication-distro uses them.

-Rafał

[Sri Maurya Kummamuru]

Hello All,

Only 6 out of 36 modules have been tested out by Module Owners/Maintainers. Please if you are a module Owner/maintainer, Can you test the modules functionality in the user acceptance testing Server.

--Regards,

Maurya

[Sri Maurya Kummamuru]

As mentioned in the earlier mail, there are still 30 Modules not tested by their module owners in the UAT Server, These are the modules that are yet to be tester by the module owners as per this spreadsheet :

providermanagement

calculation

serialization.xstream

reportingRest

atlas

appframework

htmlwidgets

reporting

htmlformentry19ext

htmlformentryui

namephonetics

idgen

metadatadeploy

htmlformentry

formentryapp

uiframework

uilibrary

appui

coreapps

emrapi

uicommons

event

allergyapi

allergyui

registrationcore

registrationapp

referenceapplication

referencedemodata

referencemetadata

chartsearch

Even if you are familiar with these modules please go ahead and test it out in the UAT Server.

--Thank you

[Sri Maurya Kummamuru]

Hello All,

Thanks to the All hands on Deck Event, we were able to test a lot of functionality but only a handful of people were able to test them, we would like to ask the community to help us test OpenMRS 2.2 in the User Acceptance Testing Server -  uat01.openmrs.org:8080/openmrs.

And update it in the Google Spreadsheet - https://docs.google.com/spreadsheets/d/16KjY5jjT94JkJ2rYvTwwMI_RfScbdyey1SX1OGDCJwg/edit?usp=sharing

--Thanks and Regards,

Sri Maurya Kummamuru,

OpenMRS 2.2 Release Manager

[Burke Mamlin]

Thanks Maurya.  Could you help us get to a final list of everything remaining to do before releasing OpenMRS 2.2?

I currently see 12 items on the Google spreadsheet:

• Darius is working on 2 module tests
• 4 module tests that seem pretty complicated/obscure
• 4 feature tests that could be done by anybody (e.g., someone in implementers group)
• 2 errors.  Daniel is assigned to the ticket for one and the other doesn't have a ticket.

I see 9 tickets:

• Daniel assigned to 3, but our 30-March design notes specify Wyclif is working on RA-237.
• Darius assigned to 2
• Rafał assigned to 1
• Wyclif assigned to 2, but our 30-March design notes say you, as Release Manager, are to decide the fate or RA-237.
• 1 unassigned

So, from what I can see, to get OpenMRS 2.2 release we need:

• Assign 4 module tests to individuals capable of testing them.
• Ask devs & implementers volunteers to test 4 documented features (i.e., read the section of the documentation and verify that functionality is working on uat01).
• Create a ticket for the testing error without one.
• Assign someone to RA-629.
• Check in with Daniel, Darius, Rafał, and Wyclif to ensure they are working on their assigned tickets and to verify ETAs for completion.

Am I on target?  Anything missing from this list – e.g., all modules are ready to go and we're ready to step through the rest of the release process once these things are done?

Cheers,

-Burke

*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 UTC. Please visit https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508 for details and to make necessary changes.

[Wyclif Luyima]

Hi,

Do we really have to get RA-629 in 2.2?

Wyclif

*** FINAL WARNING: This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 UTC. Please visit https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508 for details and to make necessary changes.

--

Wyclif Luyima
Regenstrief Institute Inc.

Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose.

If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.

[Sri Maurya Kummamuru]

Thank you Burke for summarizing them. There are a few updates to the list :

11 items on the Google spreadsheet:

• Darius is working on 2 module tests
• 4 module tests that seem pretty complicated/obscure
• 4 feature tests that could be done by anybody (e.g., someone in implementers group)
• 2 errors.  Daniel is assigned to the ticket for one and the other doesn't have a ticket.

• 2 Issues found I changed their status to error : 1. IDGen module is creating issues while creating a patient through short patient form in Legacy UI,
                                                                     2. The most recent Vitals/Encounter in patient dashboard needs to be able to display encounters that are not from HTML Forms (e.g. xforms).
• As mentioned in other thread many modules are not yet tested by the module owners. I am not confident about releasing until they are tested by them. But, this is delaying the process.
• 5 issues were found in the workflow that needs to be investigated, I've marked their status as error.

 9 tickets:

• 6 tickets are to be Tested
• RA-629 , needs a developer.

• Daniel assigned to 3, but our 30-March design notes specify Wyclif is working on RA-237.
• Darius assigned to 2
• Rafał assigned to 1

• Wyclif assigned to 2, but our 30-March design notes , I had to decide the fate of RA-228's one ticket i.e RA-588 - I bumped it to OpenMRS 2.3.

So, In summary:

• Ask Module Owners to test their Modules.
• Handle the Issues that were identified in the UAT Server  mentioned in Google spreadsheet.

• Assign 4 module tests to individuals capable of testing them.
• Ask devs & implementers volunteers to test 4 documented features (i.e., read the section of the documentation and verify that functionality is working on uat01).
• Create a ticket for the testing error without one.
• Assign someone to RA-629.

• Check in with Daniel, Darius, Rafał, and Wyclif to ensure they are working/Testing on their assigned tickets and to verify ETAs for completion.

@Wyclif, RA-629 should be included as According to @Darius's Comment on the Ticket, it would be great to have the Appointments show up in the Patient's UI as we are launching Appointment Scheduling with this release.

--Regards,

Sri Maurya Kummamuru

[Wyclif Luyima]

Okay, i will pick up RA-629

Wyclif

[Sri Maurya Kummamuru]

After User Acceptance testing, there are a total of 11 outstanding issues. out of which:

• RA-630 and RA-237 are assigned to Daniel Kayiwa and are Waiting for Testing, Daniel, Can you confirm if these have been thoroughly Tested?
• RA-228 is Waiting for Testing and RA-629 is in development, both of them are Assigned to Wyclif Luyima, Wyclif can you confirm if RA-228 has been thoroughly tested? and When can RA-629 be completed?
• RA-618 is waiting for testing and is assigned to Rafal Korytkowski, can you confirm if this has been tested?
• There are 6 Issues yet to be resolved, if any one has some spare time, can anyone pick up any of the tickets and complete them?

Modules have been thoroughly tested Excepting the ones mentioned below:

• Event Module - Wyclif Luyima, is this module tested in the UAT server?
  
• ID Gen Module - Michael Seaton, Can you test this module in the UAT server?
• HTML Form Entry - Mark Goodrich, Can you test this module in the UAT server and confirm if it is working perfectly(exporting the form, looking at the form schema etc)?

--Thanks and Regards,

Sri Maurya Kummamuru,

OpenMRS 2.2 Release Manager

[Michael Seaton]

Hi Maurya,

I may be able to test idgen later on this week, but if others are available that would be helpful.  We have already found one major issue that needs to be worked on - so we should get that underway.

Mike

[Mark Goodrich]

I gave a quick test of the Html Forms on the UAT server, and they seem to be working, but I didn't test anything too much in depth...

Mark

On 04/09/2015 02:46 AM, Sri Maurya Kummamuru wrote: