NearBeach August 2025 Goals

The 0.31 Wrap Up

We are excited to announce we are finally in the wrap up stage. Over the next 2 months we'll be wrapping up any development for NearBeach 0.31, and moving into a support model. Sadly we are behind schedule by 1 month, which we hope to catch up over the next few weeks. This was caused by a longer than expected recovery time for the lead developer.

Plan of Attack

NearBeach currently has a number of reported bugs (see screenshot). We have started tagging any bugs that we'll fix in 0.32 branch with a 0.32 tag. Those bugs that have not been tagged will be fixed during the 0.31 wrap up. Side note - we are going to do several full site tests. These will add more bugs

We have gone through our kanban boards and flagged any tickets we want to complete with the 0.31 tag. These cards are currently blocking the 0.32 development and will need to be tackled.

Kanban Cards

• Card510 - API Unit Tests - 5 hours
• Card539 - Create Fixtures for GDPR Wizard - 3 hours
• Card518 - Implement "meta_data" field for all objects - 5 hours
• Card553 - NAS Project - Test all databases with NearBeach - 15 hours
• Card528 - Indexing NearBeach Database - 5 hours (research)
• Card526 - Implement Fuzzy testing - 5 hours (research)
• Card544 - FIX GitHub Actions: Swagger documentation fails because it does not include the django-rest-knox - 0.5 hour
• Card536 - Add links to "Swagger" documentation in readthedocs - 0.5 hour
• Card542 - Extend out the swagger description - 1 hour
• Card543 - Remove the "Support Submissions" option from Swagger index - 0.5 hour
• Card514 - Test linking requirement items to an object - 2 hour
• Card495 - Implement the ability to link Requirement Items - 2 hour
• Card487 - Add a filter to the "addObjectWizardModal" - 2 hour
• Card519 - Scheduler - Add ability to link object to kanban board - 5 hour

There are a few tasks flagged as "research", we will be reading the documentation and researching how we would like to deploy these features. After the research stage has been completed, we'll determine if it gets deployed in the 0.31 branch, or the 0.32 branch.