samvera/ldp

Request for LDP Point Release

carrickr opened this issue · 9 comments

carrickr commented

We currently have Avalon 6.0 tracking #72 for the e-tags fix. Can we request a point release for our production app so we don't have to track a specific git commit?

Thanks.

jcoyne commented

@carrickr sounds good to me.

carrickr commented

@jcoyne This is done, i assume this a prelude to having me cut the release? I may need help with notes here.

carrickr commented

Stab at release notes for LDP 0.6.2 (this is based on all changes since 0.3 since that was the last time we had release notes):

  • looser restrictions for RDF::Graphs, now requires only enumerable rather than graphable
  • selective logging and performance metrics for http requests
  • 409 errors now return LDP::conflict
  • encode RDF in UTF-8 prior to turtle parsing
  • spaces no longer required between types
  • byebug now supported for debugging in all environments
  • tests for Derby LDP
  • RDF::Vocab::LDP used instead of LDP::URI
  • LDP::Response now includes paging logic
  • 307 temporary redirect requests are followed
  • use If-Unmodified-since instead of If-Match to avoid strong vs weak etag conflicts
jcoyne commented

@carrickr that sounds more like a 0.7.0 release than a 0.6 point release

jcoyne commented

@carrickr how are you getting all those things out of 3 commits? v0.6.1...HEAD

carrickr commented

@jcoyne I was going from 0.3 since we last had release notes for that. Releases have been cut since then, but no notes, at least on the releases page.

I'm fine with calling a 0.7.0 though. I was going with 0.6.2 since as you mentioned only three commits since 0.6.1.

jcoyne commented

@carrickr 0.6.2 seems fine now. But I would only make release notes for the commits since the last release or it will confuse people.

carrickr commented

@jcoyne

notes would then just be:

  • 307 temporary redirect requests are followed
  • use If-Unmodified-since instead of If-Match to avoid strong vs weak etag conflicts