Tagging java-support, spring-extensions, java-parent-project-v3 ?

[Ian Young]

On 17 Sep 2013, at 05:14, Tom Zeller <tzeller at dragonacea.biz> wrote:

> Polling for any objections to tagging our MDA dependencies.

I have no objection to tagging the V3 parent project, java-support and spring-extensions at this point.  My downstream stuff is building fine right now and I reckon that no-one else is currently proposing locking anything to the tagged versions.

> I noticed some recent commits and wanted to make sure.

I'd look more at JIRA than at commits, if the builds are clean.

On the JIRA side, there's nothing critical for me.  JPAR-26 was something I noticed while updating my dependencies but I can work round it (and have).

JPAR-16 looks important, but it also looks as if it has been done already on the V3 side (not on the V2 side, but that's Java 6 so the Java 7 support aspect isn't relevant there).  It can probably just be marked as resolved.

> Obviously I should know the answer to my question, or know the process
> we should be following before a release, oh well.

If you can clarify where you think the documentation has gaps, we should fix that.

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4813 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20130917/5edd957d/attachment.bin