-
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into feature/202311_kml_import
- Loading branch information
Showing
64 changed files
with
201 additions
and
82 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
113 changes: 113 additions & 0 deletions
113
...mentation/blog/20231229-reflecting-on-a-year-of-progress-a-look-back-at-2023.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,113 @@ | ||
--- | ||
slug: reflecting-on-a-year-of-progress-a-look-back-at-2023 | ||
title: Reflecting on a Year of Progress; A Look Back at 2023 | ||
authors: dion | ||
tags: [photo mangement, year in review] | ||
date: 2023-12-29 | ||
image: https://media.qdraw.nl/log/de-7-dingen-die-ik-miste-bij-het-beheren-van-mijn-foto-collectie/1000/02_starsky_v052_kl1k.jpg | ||
--- | ||
|
||
# Reflecting on a Year of Progress; A Look Back at 2023 | ||
|
||
As we bid farewell to the year 2023, it's essential to reflect on the strides made in the ever-evolving landscape | ||
of technology. This year has been marked by continuous improvement, innovation, | ||
and a relentless commitment to enhancing the user experience. | ||
In this blog post, we'll delve into the notable updates and advancements | ||
encapsulated in the various releases of version 0.5.x of our software. | ||
|
||
## Version 0.5.13 - Front-end Accessibility and Code Refinement | ||
|
||
The December release, version 0.5.13, showcased a concentrated effort on enhancing front-end accessibility. | ||
Notable changes included focusing on the previous and next functions in detailView, | ||
transitioning from div to button elements for improved accessibility, and updating the front-end to newer versions. | ||
Additionally, code style issues were addressed to ensure a smoother developer experience. | ||
|
||
## Version 0.5.12 - Keep up with the Latest Framework Version | ||
|
||
November witnessed a major backend upgrade as the system transitioned to .NET 6, | ||
specifically SDK 6.0.416 and later to 6.0.417. | ||
This upgrade aimed to leverage the latest features and improvements in the .NET framework. Simultaneously, | ||
front-end accessibility and code quality were refined, and documentation was updated to align | ||
with the latest framework version. | ||
|
||
## Version 0.5.11 - A Blend of Upgrades and Front-end Overhaul | ||
|
||
October brought about a series of updates, including the migration from Create React App to Vite in the front-end, | ||
an upgrade of npm packages, and the transition to the latest version of Electron for desktop applications. | ||
The backend continued its journey with the adoption of .NET 6, focusing on stability and performance. | ||
|
||
## Version 0.5.10 - Keeping Pace with Technological Advancements | ||
|
||
July witnessed yet another backend upgrade to .NET 6, | ||
emphasizing compatibility with the latest SDK and runtime versions. | ||
This release also included frontend and backend improvements, such as upgraded npm packages, | ||
Sonarqube settings refinement, and addressing various code smells. | ||
|
||
## Version 0.5.9 - Tackling Bugs and Enhancing Documentation | ||
|
||
May saw a concentrated effort on bug fixes and documentation updates. | ||
The backend resolved issues related to duplicate entries, updated dependencies, | ||
and refined documentation for better clarity. | ||
|
||
## Version 0.5.8 - Streamlining Performance and User Experience | ||
|
||
April brought a slew of backend fixes addressing issues ranging from file update times to code bugs. | ||
The frontend also witnessed upgrades, and the entire system was migrated to the latest version of .NET 6, | ||
focusing on performance and stability. | ||
|
||
## Version 0.5.7 - Striving for Perfection and Stability | ||
|
||
March marked a significant step towards stability with numerous bug fixes, code smell improvements, | ||
and upgrades across the board. The backend also introduced a stable release to the GitHub container registry, enhancing deployment processes. | ||
|
||
## Version 0.5.6 - Unveiling System Trash and User Interface Refinements | ||
|
||
In March, the introduction of an internal service for system trash and a myriad of frontend and backend changes | ||
showcased a commitment to refining the user experience. Known issues were transparently communicated, and the focus was on feature toggles and system trash functionality. | ||
|
||
## Version 0.5.5 - Prioritizing Security and System Upgrades | ||
|
||
February prioritized security with the addition of regex timeouts to prevent Denial of Service attacks. | ||
The backend underwent significant upgrades, transitioning to .NET 6 SDK 6.0.406, while documentation and client dependencies were also updated. | ||
|
||
## Version 0.5.4 - Metrics, Security, and Code Refinement | ||
|
||
January marked a milestone with the introduction of application insights metrics, security enhancements, | ||
and code refinements. The backend introduced features such as thumbnail query deletion for nonexistent items and a systematic approach to handling errors. | ||
|
||
## Version 0.5.3 - A Holistic System Upgrade | ||
|
||
The initial release of the year focused on security, system upgrades, and improving telemetry. | ||
Noteworthy changes included enhanced thumbnail list updates and a dedicated service for periodic thumbnail creation. | ||
|
||
|
||
## Upcoming Features | ||
|
||
### Thumbnail creation for all images should work better | ||
|
||
The future holds a commitment to even more captivating visual experiences. | ||
Our roadmap includes advancements in rendering technologies, | ||
ensuring that thumbnails and images are not just displayed but tell a story. | ||
|
||
### Spatial Intelligence Unleashed | ||
|
||
Building on the integration of KML for geo functionalities, | ||
the future unfolds with a broader vision of spatial intelligence. | ||
We envision seamless integrations with diverse geographical data formats. | ||
|
||
### Holistic Observability with OpenTelemetry | ||
|
||
In the pursuit of a more flexible and comprehensive approach to application monitoring, | ||
we have initiated the phased transition from App Insights to OpenTelemetry. | ||
OpenTelemetry offers a vendor-agnostic, open-source framework for observability, | ||
enabling better insights into application performance. | ||
This transition not only aligns with industry best practices but also empowers | ||
users with a broader range of telemetry options and integrations. | ||
|
||
## Conclusion | ||
|
||
In conclusion, 2023 has been a year of relentless pursuit of excellence, | ||
with each software iteration building upon the last. As we step into the future, | ||
we remain committed to delivering cutting-edge solutions, prioritizing user experience, | ||
and embracing technological advancements. Here's to a year of progress, and we eagerly anticipate | ||
what lies ahead in the dynamic landscape of software development. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
{ | ||
"info": { | ||
"title": "Starsky", | ||
"version": "0.5.13.0", | ||
"version": "0.5.14.0", | ||
"extensions": {} | ||
}, | ||
"servers": [ | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
{ | ||
"name": "build-tools", | ||
"version": "0.5.13", | ||
"version": "0.5.14", | ||
"description": "", | ||
"main": "", | ||
"scripts": { | ||
|
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
{ | ||
"name": "mail", | ||
"version": "0.5.13", | ||
"version": "0.5.14", | ||
"description": "", | ||
"main": "mail.js", | ||
"scripts": { | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
{ | ||
"name": "mock", | ||
"version": "0.5.13", | ||
"version": "0.5.14", | ||
"description": "", | ||
"main": "mock.js", | ||
"scripts": { | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.