Time/PlaceThis meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
Agenda
NotesQuestion about FCREPO-238Question from Frank about FCREPO-238: How should we deal with old objects where the last modified date is incorrect (slightly before the modified date of the most recently modified datastream)? After discussing it a bit, it seemed like the right solution would be to have a utility that works against the REST API that people can run on their repository. This utility would do an export of each object, and if it needed correction, it would make a modification to to label of the object, setting it to the same value it had before. This would ensure the indexes get updated (SQL, RDF) and that the object's modified date does not occur before that of the most recently modified datastream inside it. ACTION: Frank: Check with eSciDoc developers to see if this kind of solution would resolve their issue. GSoC UpdateNot sure where Jiri was today. So, no discussion of GSoC work. 3.5 ReleaseChris: Still looking good for release? Any gotchas? Aaron: Look ok for release. Still having issues with spaces in paths in Windows. Also discovered (like Eddie did a while back) that the journaling tests depend on DNS servers being honest about the existence or non-existence of a domain. Switching to Google DNS fixed the issue. No other problems encountered. Chris: Ok, we'll still release on Thursday, then. (Updated the group on recent work on docs...see agenda links above)
Also, it was noted that we need a warning about the API response changes related to fixing issues. The JIRA issue is slated for 3.6, but most of the subtasks are in fact done for 3.5. ACTION: Chris: Put the above items in release notes. Include warnings re: api response change and related JIRA issues. Aaron: We also need to say that Tomcat 5 is no longer supported, but 6 and 7 are. ACTION: Chris: Put note about Tomcat version support in release notes. Aaron: What about issues with votes? Which did we miss? Chris: A few. JIRA has a report. See "Popular Issues". Unresolved issues sorted by vote count. I noticed that the Content-Length: and Content-Range: issue is in there. That still needs some updates in JIRA. ACTION: Chris: Fix the Content-Length/Range issue in JIRA so that the work that was actually done is reflected int he release notes and the work that wasn't is listed in an outstanding bug. Chris: Here's a basic outline of release day. Anything else we can think of?
Aaron: Sounds good. But I can't sign artifacts due hardware failure. Chris: Ok, I'll build, sign, and upload then. I'd like to get things done as early as possible Thursday. Shall we start at 9:00am Thursday on Skype? Aaron: Sounds good. Note re:Chris' availabilityChris: Will be out for two weeks. Will need someone else to facilitate the discussion for the next couple weeks. We can finally start talking more about 3.6 and 4.0 stuff. It will be fun. Aaron: And 3.5.1. Which is also fun. Chris: Yep. Bye all. <click> All: Bye <click> |