Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Explore possibility of a Xerces 3.2 release

Description

Placeholder for exploring possibility of a new Xerces release off the trunk. Need to identify where/when they branched and how much has diverged and might need testing.

Ideally I would just do smaller changes to 3.1 and re-branch there but I'm constrained by TIIC and lack of control over the project unless I fork.

The advantage of a 3.2 aside from a few improvements I can make with an ABI bump is the ability to change the libname on Linux, bypassing the broken version of 3.1 stuck on RH7. Arguably I should probably consider a custom build/package anyway just in case anybody ever ships a version of 3.2.

Environment

None

Activity

Show:

Scott Cantor August 25, 2017 at 5:57 PM

With release imminent, closing this out and I'll open a new task for the Xerces and Santuario release work.

Scott Cantor August 23, 2017 at 5:26 PM

I posted a new build as RC2 and just called for a vote ending next Monday, so release will hopefully be done next week.

Rod Widdowson August 23, 2017 at 3:58 PM

... and with the rebuilt iis7 plugin, end to end looks good.

So I'd say that from our point of view Xerces 3_2 looks good.

Scott Cantor August 23, 2017 at 3:57 PM

Thanks. A couple of minor bug reports came in that I think can be safely fixed, so once that's done I'll spin a new build and probably call for vote.

Rod Widdowson August 23, 2017 at 3:47 PM

Testing a complete stack (VC10) on top of Xerces 3_2 (built from HEAD in svn) looks initially good.

I need to rebuild my IIS7 plugin before I can get any further, but (after the mandatiry dll compat issues becasue I had't revised the versions on everything) shibd started up and ate the UK Fed metadata.

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Original estimate

Created April 21, 2017 at 9:57 PM
Updated August 25, 2017 at 5:57 PM
Resolved August 25, 2017 at 5:57 PM