You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
- Interest in being able to handle content already in S3/Swift content
- DURACLOUD-1316
- Interest:
- Andy - definite interest, but it'll be challenging to ensure everything works.
- How do we prevent overwrites (or simultaneous writes)?
- Perhaps some type of locking mechanism?
- Could have a toggle that only allows writes via either S3 or DuraCloud API
- S3 does provide a way to send SNS notifications when content lands. Could use this to add a message to the SQS monitored by the Mill
- Fedora has a similar need to allow direct writes to OCFL then notifying Fedora
- Would need a way to ensure we get checksums properly and that the manifest/audit logs
- Top priorities
- Andy: 1258 is important, Mill using quite an old version. 1257 is essentially done.
- Danny: 1290 (docker/terraform), setting us up for long-term maintenance
- Nick: Snapshot totals (most questions), 1150, 1279, 1301
- Bill: Snapshot totals
- Plans for this week
- Andy: 1257, 1258, 1290
- Nick: 1069, 1268
- Danny: 1290
- Bill: 1292, 1278
- Github Actions
- In DuraCloud, we only merge to master on release
- The push to sonatype can push it all the way through
- Most projects tend to use tags
- Should we consider changing our branch structure? Have master being the leading edge?
- One option: develop → main and master → release
- It's helpful to have a branch where we're able to merge everything in and do testing
- Rename master to main?
- Develop: The integration point for development
- Master/Main: Merges from develop after testing (usually a release)
- Indicates who will be taking minutes