Unable to locate J=
ira server for this macro. It may be due to Application Link configuration.=
<your issue here>
Please squash a bug!
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 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 Nothing in particular
5.0.2 Off to the races! Yinlin=
has taken role of release manager.
Ecosystem release/develo=
pment policy review Yinlin had asked about the fcrepo4/docker project in the context of poli=
cies on merging PRs. There=E2=80=99s no official policy on the l=
abs repositories unlike the extensions or main repositories. Thi=
s is justifiable since there=E2=80=99s no guarantee of support for labs rep=
ositories=E2=80=99 code. But naturally, people can/should request revi=
ews of PRs as a best practice.
Status on current tools&=
nbsp; fcrepo-came=
l and fcrepo-camel-toolbox: the latter has some commits to master inte=
nded for release 4.7.3 that Peter=E2=80=99s using locally. He as=
ks what the RC policy should be there. Daniel recommends an eval=
uation period for the toolbox since it is widely used. A mainten=
ance branch should be created, an RC tag cut, and a RC announcement should =
be made, but there=E2=80=99s no need for a wiki page, etc. Jared suggests that the maintenance branch=
may be superfluous as there are unlikely to be additional PRs in the inter=
im. The evaluation period will be 1 week. There=E2=80=99s a problem building both camel and came=
l-toolbox with how they reference the parent pom. Danny Bernstein will explore updates to fcrepo-camel-tes=
ts to resolve PAX Exam issue.
Next steps for import/ex=
port 4->5 migration Daniel=E2=80=99s feeling is that we=E2=80=99re not far away from bein=
g able to do this migration. Two parallel tacks can be pursued.&=
nbsp; We can focus on round-tripping 5.x data (exporting version, expo=
rting webacs, and importing versions). Also, create a new tool t=
hat would transform a 4.7 export to a 5 export. It seems reasonable that we=E2=80=99ll make pe=
ople upgrade to an appropriate version of 4.x before attempting the migrati=
on to 5. Consensus is that=
this approach is sound. Documentation will indicate the versions for =
the export and the import, and wiring in a migration tool at that point wil=
l be straightforward. Aaro=
n points out that migrating the webacs could be the tricky part, since if t=
here are containment relations between them, these will need to go away, an=
d if there are out-links from any resources to the webacs that are not of t=
he =E2=80=9Cthis is my webac=E2=80=9D variety, these will need to be elimin=
ated.
5.1.0 Item 6.a.v is of questionable value=
as it=E2=80=99s for a rather customized case =E2=80=93 it=E2=80=99 failing=
tests, but if the PR authors can fix that, it will all be good.
Peter =
Eichman will take charge of the fcrepo-camel/fcrepo-camel-toolbox=
release process.
Jared Whiklo=
will rebase the PR for Unable to locate Jira server for this macro. It may be due to =
Application Link configuration. and make sure Andrew Woods's and Peter Eichman's concerns are addressed.
Peter =
Eichman : will complete review of Unable to locate Jira server for this macro=
. It may be due to Application Link configuration. when =
Jared Whiklo is finished with the a=
bove.