Skip to content

Releases: iemsel/SandboxBackend

release 3

Choose a tag to compare

@iemsel iemsel released this 12 Jan 21:11

Userstories completed:

  • As a parent, I want a simple profile page.
  • As a developer, I want clear API documentation so that front-end integration is smooth.
  • As a developer, I want logging and monitoring so that I can debug issues.
  • As a developer, I want automated tests so that the system remains stable.
  • As a developer, I want environment parameters managed separately so that deployments are secure and configurable.
  • As a teacher, I want the backend to support creating new ideas so that I can store my lesson activities in the system.
  • As a teacher, I want to plan my idea so that I organize my schedule better.

Finsihed product release!

release 2

Choose a tag to compare

@iemsel iemsel released this 12 Jan 09:10
7220dcc

Userstories completed:

  • As a developer, I want separate microservices for ideas and users so that the system is scalable.
  • As a developer, I want each service to be independently deployable so that updates don’t break the system.
  • As a developer, I want a gateway service so that requests route correctly.
  • As a developer, I want database separation per microservice so that responsibilities are isolated.
  • As a developer, I want a database with sample idea entries so that I can test frontend features during early development.
  • As a teacher, I want to create a new idea so that I can store my own lesson concepts.
  • As a developer, I want the build process to trigger automatically on push so that integration happens continuously.
  • As a developer, I want to be notified when a build fails so that issues can be fixed quickly.

(This is the second release, the date of making this release does not fit correctly since we tried to create release with a single pull request before)

release 1

Choose a tag to compare

@iemsel iemsel released this 12 Jan 21:14

Userstories completed:

  • As a developer, I want a suitable development pipeline chosen for the application so that code delivery is reliable.
  • As a developer, I want a foundational backend setup so that new features can be added efficiently as the project grows.
  • As a team member, I want clear role division so that everyone understands their responsibilities during development.
  • As a developer, I want Dockerfiles for both frontend and backend so that the project can be deployed and run consistently across environments.

(date is not correct because we didnt know how to do releases yet, but this is what we had at end of sprint 1)