Agenda
- Release Readiness
- Individual Updates
- Roster - Provisional vs Core
- The 2.4.0.011 tag
**Status of Blockers: - Review fixes to be included in next tag (Ticket by ticket discussion)
- JIRA's not on this list that should be?
- Review of Demo Sakai.property https://source.sakaiproject.org/svn/reference/trunk/demo/sakai.properties
Meeting Notes
Notes Key
Roughly paraphrased by Steve. There was a lot of static about halfway through the call today.
????: I wasn't sure which SAK was being discussed.
???: Someone talking whose name I couldn't figure out.
Name?: I think it was 'Name' speaking, but not sure.
ACT: Someone said they were going to do this. Few 'official', "Yes I will do that"s today. Mostly just assuming we were going to include most of the Jira's.
Pre-meeting Camaraderie
There was an IP change on the polycom? Lance hooked Peter up with the new IP address.
Release Readiness Review:
Megan is concerned because there are over a 100 items to merge in. And there is only one more tag.
During 2.3 we didn't come close to this volume of fixes. This release is larger, but still.
Freeze was not very hard. We haven't been able to fully test a few tools. A bit nervous about committing to the 4th for a release.
JohnL: It only feels like things have really started to settle down in the last week or so.
Hannah: Feels Megan's concern.
Megan: Resources? How do we feel about it?
Hattie: H^H^ Some IE issues at the moment. Hoping to get them fixed. Need to test on IE6,IE7, Firefox etc. Think we can manage it.
Andrew: Would it helpful to do things more often (as in merges).
Megan: Could increase the number of QA Tags.
Linda: Need to do a full regression on each tag?
Peter?: Caution on the number of tags. Each one takes a significant amount of time. There is a significant number of fixes and work going into this release. How could testers and administrtors keep up? Each little merge request takes up time.
Megan: Need to focus on fix areas, walk the line, and still release on time. Will all the changes being sent in, it doesn't seem reasonable to release on the 4th. If we are going to go for the 4th, we need to cut a lot of things from today's list. A majority of the list were not blockers or critical. We can slip a few weeks, but not months like last summer. If there are reasonable things that need to address. There will always be more bugs and patches.
Lisa?: One or two important bugs that keep us from getting to an area.
Peter: Why are sending in minor changes so late in the release? If tools need work to become usable we made need to delay a few weeks. So many off by
John: Some important things for assignments.
Megan: What are we striving for? Awesome? Good Enough? Mediocre?
Peter: Need to draw lines.
Seth: Things are that absolutely broken need to go in. Previosuly, resources was broke a week before the release. We don't want to go through a huge maintenance release a week after the release to patch our system just so it works. If you run the demo and it doesn't work, we're screwed. If the OOTB version is broke that affects us greatly.
Megan: Lets go through our Jiras.
Fix Nominations:
Sorting by components.
Assignments 9588: requested from non-english speaker
Beth: Advocating i18n patches for a maintenance release, since there are others that haven't made it to 2.4
Cut!
9533: JohnL: Low in priority, leave it out.
Sean: Looks disgusting, velocity code in page html.
Discussion: Future: Small fixes, but should fixes for non-core be considered at this point in the discussion?
In!
9525, 9497: JohnL: If we don't fix it, the setting for an assigment won't transfer between sites. Fairly important. Not a blocker, you can reset it. Just annoying.
In!
9481: JohnL: Not blocker, just ugly to get an error page.
In!
9427: Blocker
In!
9367: JohnL: Could be a candidate to take out. Removes a control dealing with sorting. The bad effect, confusing, doesn't break anything.
Out
9362 Blocker
In
9316: JohnL: Pretty confusing for users
In
9018: JohnL: Pretty major blocker. Megan: This is a new feature. Introducing new functionality and things are not working.
In
8684, 8619: JohnL: Both need to be in. Students can't resubmit assignments.
In
8277: Fairly critical for reusing assignments.
In
Skipping over anything that's critical or blocker
9513: In
9432: Megan: Very confusing for users
In
8523: Documentation in
8881: Megan: Was supposed to be merged in prior. There was a snafu.
In
9564: Translation Strings for Samigo and 9190, 9188, 9187, 9186 removed hardcoded strings from JSP
Beth: Perhaps this should go in a maintenance branch, since there are code changes. There a few dozen issues that haven't been committed that are patches. Can go in later.
Megan: We haven't been cutting much. Actually, it doesn't look like we'll be able to cut much.
Peter: If we are not going to be cutting much, this may be an indicator about delaying 2 weeks, rather than announcing the delay the day before.
Poland: If we run into dependent things, we may not run into them.
Megan: Let's maybe just take all these.
Peter: One more tag with random fixes?
Megan: Tag14: blockers only! Tag 12: Critical. People need to categorize their priorities.
We are resorting the issues somehow, to get things on nightly. Lots of talk about Jira Filters and how it sorts by various columns.
Skipping some that are resolved.
9272: Megan: Include since we're doing big assignments testing anyways?
ACT: John will check it.
In
9542: Megan: Not sent to me? JohnL: Doesn't need to be included.
In
9478: Peter: If we are picking some stuff, bring it in. Lots of support calls on this one. Hannah?: Seems like an edge case.
Do we really know if it's only project sites? Dead air on the line. Suspense! Will 9478 get in!!
???: It is big for someone's major installations.
It's IN!
9587: Peter: These are probably good to go in. Don't touch anything and help a lot for the tool. (Content-review patches)
Megan is flying through Jiras. I think most of them are going in.
There is a lot of static on the line.
9452, 7255: Mailtool ones are going in.
8444: Andrew: Looks like a candidate for the conversion script. ACT: Poland will check it out.
8822: In
9422: Already in, updating fix version
9504: Megan: Anyone here to speak on the OSP ones? Chris Maurer is physically coming to room.
Talk about data Warehouses and noisy logging.
9355,8823 and PDA Portal stuff: Megan: These don't seem important since PDA Portal OOTB. Peter: We should put these in, they don't touch much.
You have to throw a property setting to turn it on.
????: Dunn: Small change in components.xml relative path usage. Doesn't necessarily need to go in.
9493: In
9600: In
7553: ???: How messy to include it? Because we want import to work in Samigo.
In
9085: Poland: Ian caught and logged some exceptions. Can go in.
9285: In
Megan: Any problem with including all these Section Info fixes?
In.
9311, 9054: In
Megan: Sending out email. Delaying the release. Nothing not critical in next release.
Other Business:
Roster Performance Problems. Suggested that we bump it back down to provisional. It's going back to provisional.
Open Blockers:
9310: Needs some more tweaks.
Jim: We do want it in, but there are some IE needs still.
Peter: Resolve this and create a new issue.
ACT: Poland is going to fix some properties.
7335: ???: Not sure about status. SOO will be back next week.
7408: Peter: Mostly fixed. Should get this in, and create a new issue if there are additional issues.
9123: Megan: Assigned to me. ACT: Megan will test it.
Some documentation issues for Clay and other folks.
9506: ACT: Poland: This should be done today before the tag.
9585: Folks are still hashing out solution on dev list.
Jim: Gaurav: has fixed a good portion.
Gaurav: Citations code no longer deploys ehcache.xml. But claimed as a dependency somewhere.
9442: Seth: I know Lance made the change, wondering why its not on the list. Megan: It should be on the next tag.
Megan: That's all for today's Jiras. We want a good release for end users. We can go over the properties list on next weeks call.
Seth: People should review the sakai.properties to make sure that we the correct settings.
ACT: Everyone: Check sakai.properties if you have properties in it!
Meeting adjourned. Very little post meeting camaraderie.