Page History

Review of newly-submitted issues

Link

Review of outstanding items for 3.2

- SPARQL Construct/Ask/Describe support (Team is focused on 3.2 - didn't get a chance to review these this time)

Developer Updates

Kai:Code formatter

• Merged FCREPO-406
• Q: Eclipse code formatter? Chris: Recommendation is to use it only to clean up whole files if they're in bad shape, as a starting point, but not on an ongoing basis as the formatter doesn't always do the right thing.

Aaron:

• Looking into MPTStore resolver
• This summer: Message-based OAIProvider

Andrew:

• Q from Chris/Kai:

...

• Clover status?
• A: did one manually. Couple tests coverage wasn't reported properly.  Works well in maven, ant a little more work.
• ACTION:

- clover report, did one

- most of it worked ok, but a couple test classes weren't covered properly

...

• will look at adding clover reports to fedora via ant

Bill:

• Merged FCREPO-463, FCREPO-301 (and related), and FCREPO-402

Chris

• Merged FCREPO-

...

• 101
• Got tests running again after Kai/Bill merges
• ACTION: tell ci tests to use "foo" as webapp context to catch regression probs (run ant build with -Dfedora.appServerContext=foo)
• XML Editing discussion:
  • Q: What editors do we use? A: Eclipse or vim
  • Q: Indents? A: definitely spaces
  • Vote: 2 or 4 spaces?  Unanimous: 2 spaces
  • Eddie notes

-

Kai

- foo webapp context

- change default context for testing

- run ant build file -Dfedora.context=

XML Editing:

Bill: uses text editor

Andrew: uses eclipse, would vote for not having tabs

Resolved Standard: all agree

xml indentation is two spaces.

...

• • : XML build preferences aren't applied to ant build file, so if you use Eclipse you'll need to change them there as well.

Before Freeze (Thursday)

Migration utility : Andrew

Akubra: official release

Sanity checks: All

Bill: Wadl for rest api (create html pages to display results from rest api queries, will need to get into xslts and change them like kai did)

...

(Chris)

Bill: Updating REST api xslts to take webapp context into account (currently, images broken)

Sanity checks: All

Testing Plan/Assignments

• Manually
  • Any new functionality that doesn't have coverage
    • alternative web context mapping
      • Test both java+flash clients with different context (Andrew)
      • also: multiple fedoras in one container (Eddie)
    • akubra integration
      • running rebuilder (Bill)
  • Identify and test non-covered commanline scripts (Kai)
  • New client manual tests: (All)
    • Search
    • Ingest/export
    • Modify datastream
    • Create object
    • Add datastream (each kind)
    • Purge datastream + object (no versioning)
    • Note: versioning is not exposed, but old versions aren't exposed.
  • Old client (All)
    • Supports all above
    • Create diff objects via templates
  • Migration from 2.x (make solid: goal is to stop supporting migration branch)
    • Testing on 2.x objects that ARE NOT dependent on UVA servers
      • Link to list of objects that are
    • FCREPO-395 (classpath issue) needs to be resolved for this
    • Chris: OSX
    • Aaron: Linux
    • Bill: Windows
    • Note: This will require spot-checking.
  • Upgrading from 3.1(Eddie)
    • Rebuild of Mulgara
  • OAIProvider sanity test (Chris)
  • GSearch sanity test (Bill)
  • Journaling: basic leader/follower test (Aaron)
  • DirIngest (Chris)
• Automated: AllOfflineTests, ConfigA, ConfigB, ConfigQ as appropriate
  • MPTStore+Postgres+Linux+non-fedora context: Eddie (java 1.6)
  • Mulgara+Windows+MySQL+Akubra: Bill
  • Mulgara+Linux+Derby+non-fedora context: Andrew (java 1.6, ConfigQ)
  • Oracle+Windows+Mulgara: Chris
  • OSX+Derby+Mulgara: Kai

Documentation Plan/Assignments

• New Functionality that isn't yet documented
  • Akubra (Chris) "Configuring Lowlevel storage"
  • Alternative webapp context (Kai new webapp context)
  • New admin ui (Bill, screenshots, cross-domain.xml info -- tell people to pull this from alongside .swf file)
• Existing functionality that's been updated
  • Changes to REST api (Bill)
  • Changes to rebuilder doc (Chris)
• Release notes (Chris)
  • Take things in from JIRA
  • Make 2.x support announcement with 3.2 release
  • If interest, allow community to support it
• Install and configuration guide
  • General review, make sure it's accurate for 3.2 (Andrew)
  • Updated for Derby already
  • Config Fedora for new webapp context (Kai new webapp context)
• Migration guide need to review
  • (Aaron)

Release Process

• Documented in Wiki Will put current docs in wiki (Bill) and go from there.
• One step: snapshot the docs 3.1
• Before linking in 3.2 release notes and change tags

Release Date

• Will likely push a couple days to account for 2 days of code freeze slippage. But let's see where we're at next Tuesday.