Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Tickets resolved this week:
key
summary
type
created
updated
due
assignee
reporter
priority
status
resolution
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Tickets created this week:
key
summary
type
created
updated
due
assignee
reporter
priority
status
resolution
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Minutes
Announcements
Talked about Ruben Verborgh's blog about making a front-end developers =
experience using linked data easier. Might make a shift in the access=
ibility of linked data.
Andrew mentioned this making him rethink the JS we use in the front end=
of fedora.
Aaron Birkland talked about how they use plain old JSON in their Ember =
JS project at Johns Hopkins. It worked well, but is very specific to =
their use case given how Ember JS works. Aaron Coburn had been lookin=
g into designing a UI with a more general approach for linked data (maybe u=
sing React); not sure of where that went.
Follow up from last meeting regarding UMD fixing checks - made into an =
action.
5.0.1 Release=20
Both issues done and merged into master and 5.X
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
Talked about point release process =E2=80=93 for 5.0.1. &nbs=
p;Closest thing we have is: Policy - Release Candidates which covers point releases.=
Shorter period of testing. For a point release - it's an ackno=
wledgement that we know something is not right and we want to get a fix out=
quickly. These changes should not break any API. Each time we do a p=
oint release, we should have a discussion of scope of fixes, what is necess=
ary amount of testing required, versus a set process. Point rel=
eases warrant a conversation, which might result in standard testing, but n=
ot necessarily. =20
What do we want to do for this release? Aaron Birkland thinks a light weight cycle for this one, give=
n the tickets involved. Bethany Seeger =
;and Ben Pennell agree.<=
/li>
Simple test page should be fine for 5.0.1 - tests: building source code=
, running all the tests on three platforms, CTS test, and the tests in the =
PR for the two issues. Maybe a few of us could go through the page an=
d do sanity testing.
Create RC for 5.0.1? Yes, but how long would we have for public c=
omment on it? Danny Bernstein=
will create an RC for 5.0.1 today and we will test it for 1 week then =
release it.
Andrew Woods - would like to put CT=
S test results for 5.0.0 and then 5.0.1 results on the Fedora page. =
; Need to figure out how to highlight the differences between tests as well=
as how to interpret the test results. A top level page that makes it=
easy to navigate through results would be nice. More on this below.&=
nbsp;
4.7.X - need a separate conversation regarding release testing process =
on this branch
CTS test results organization on web page =E2=80=93 figuring out w=
here to put it, repository wise: https://github.=
com/awoods/hosted-ontologies. Andr=
ew Woodswill setup the github site infrastructure and pass on to <=
a class=3D"confluence-userlink user-mention" data-username=3D"dbernstein" h=
ref=3D"/display/~dbernstein" data-linked-resource-id=3D"13764383" data-link=
ed-resource-version=3D"2" data-linked-resource-type=3D"userinfo" data-base-=
url=3D"https://wiki.lyrasis.org">Danny Bernsteinand Bethany Seeger. And=
rew Woodswill transfer ownership of that repo to the fedora project.
Status of ecosystem tools:
Java Client Release - status: wh=
at is process? Ben Pennell&nb=
sp;unsure - the client is ready for a release and can be done now. Th=
e process has been that there isn't really a process. Since they are under =
'exts' and therefore community supported, they can release when they feel i=
t's ready.
fcrepo-camel - status: Aaron Birkland=
- there's a PR there. This PR make=
s it 5.0 ready. Ready for review=20
do we support 4.7 and 5.0? Yes, we probably should make sure that=
4.7 users can still use this (either via a branch or extra code to ensure =
it's backwards compatible).
It would be good to see how this PR behaves with 4.74 and camel tool bo=
x. Peter Eichmanm=
ight already be planning to test this. Ben Pennell can test it. The process of migrating API-X to i=
t and the camel tool box will highlight anything that's lacking and needs t=
o be changed.
Andrew Woods&n=
bsp; will start by putting up raw HTML results for CTS now, so community ca=
n have access to them.
Checking with Peter Eichmanregarding: UMD is storing checks and re=
sults for fixity checks inside Fedora, it would be good to capture this pro=
cess in the community documentation.
Danny Bernstein will reach out to Yin=
lin Chen to see about a fcrepo4-docker release with the 5.0 architectur=
e.