Version Update from v0.8.0 to v0.9.0

[leekahung]

PR Details

Version update here will be from v0.8.0 to v0.9.0 for the Master branch. Will create a new v0.9.0 Release after we got this merged into Master.

Major updates since last version includes:

• Adding logo to navbar/ favicon #348
• Rewrite clients with react query #362
• Revamp status notifications #331
• Private profile info and fixing profile bug #379
• Refactor container creation #384
• Create User Registration Page #378
• Delete old notification system #392
• Putting SetAclPermissions into Modal #388
• Create message read status (#400)
• Message preview update #390

Bug fixes:

• Profile fails to load client info correctly due to incorrect parameters #387
• Bug fix for contacts page #394
• Profile bug for non-existent webIds #402
• PASS logo production bug #407

Other fixes:

• Minor clean-up to root files #380
• Refactor styling from stylecss into themejs #383
• Only parse valid contacts #395
• Clean-up Profile Components #401
• Clean up Development v9 #409
• Update to PR template for GitHub #424

[xscottxbrownx]

I'd prefer we merge in Andy's latest work on message preview too. Brandon's work on sharing modals too.

If we could get both of those in, the app will start looking pretty clean for an MVP.

[leekahung]

I'd prefer we merge in Andy's latest work on message preview too. Brandon's work on sharing modals too.

If we could get both of those in, the app will start looking pretty clean for an MVP.

Yeah, that's the plan. Keeping this a draft for the time being.

[leekahung]

Pulled in a few of the other minor PRs into this update. Opening this up for review.

[leekahung]

For this version update, PR #411 will be the last update to keep this from growing any further. Think we'll have existing PRs in the current pipeline moved to the next update.

[andycwilliams]

Don't forget to include #390 in the list of updates.

Also, not sure whether it would be done in version update PRs but I just wanted to mention that the list of contributors in the readme is out of date. We have quite a few new people who ought to be included. I'm not sure whether that would necessitate its own PR.

[leekahung]

Don't forget to include #390 in the list of updates.

I'll have it updated in the PR description.

Also, not sure whether it would be done in version update PRs but I just wanted to mention that the list of contributors in the readme is out of date. We have quite a few new people who ought to be included. I'm not sure whether that would necessitate its own PR.

Think we can update this in the next update with a PR.

[leekahung]

Hey @timbot1789 , @xscottxbrownx and I had recently found one of the merge checks failing in the PR to Master. The strange part is that we can't seem to locate the offending file in either Development or Master branches. Is there a way to handle this or we could just disregard it?

[leekahung]

Alright, gonna try and merge PR #424 (which is mostly administrative changes) into branch to see if the CI check gets fixed.

[leekahung]

Hey @timbot1789 , @xscottxbrownx and I had recently found one of the merge checks failing in the PR to Master. The strange part is that we can't seem to locate the offending file in either Development or Master branches. Is there a way to handle this or we could just disregard it?

Never mind. Think we got this fixed!

[leekahung]

Alright, think we could get this version update made now. Anything else we need to fix/amend we could do it in subsequent Issues/PRs.