Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sprint 2 Review #427

Closed
Wyqer opened this issue Jun 3, 2018 · 0 comments
Closed

Sprint 2 Review #427

Wyqer opened this issue Jun 3, 2018 · 0 comments
Labels
dev-blog Blog article about development progress
Milestone

Comments

@Wyqer
Copy link
Member

Wyqer commented Jun 3, 2018

General Information about sprint reviews
As we will release a working iteration of the new framework after every sprint, everyone is invited to help with testing the sprint results.
The only thing to remember is that you should only report bugs in this issue, which are caused by the contents of this sprint (which are listed below). So it is vital to look at the content description to see what was actually added. Only by reading this you know what we've really intended to implement and defined as done.
I guess you understand that reporting things which weren't even planned to be part of the sprint won't help in any way.
This releases (which are also marked as Pre-release) aren't meant to be played as replacement for the current framework. It is for testing purpose or a kind of first look at features/changes which will be part of the 0.97 release in some months.

Summary of this sprint
With this sprint we've mostly done some basic preparations for the future implementation of features. We've got an own event system to get rid of many endless loops and prepared some things for the UI defines. The basic structure for the action manager for players is also already finished and we'll see how good we can work with these features concerning the future implementations.
Basically we haven't much which can be directly seen or discovered by the players in the game, as it's all kind of "backend" stuff. This is also caused by the reason that I was suffering a very harsh cold during the sprint timeframe. Especially in the first week I wasn't able to do anything at all. I guess you can expect to see more stuff which you can use in the mission after the next sprint.

Content of this sprint

Epic Description
No Epic this time
Task Description PR
#404 Bugunt for Sprint 1 no direct PR
#413 Custom Event system #420
#414 Action manager #420
unfinished Unfinished part of the UI defines overhaul #424

Released sprint result
https://github.com/KillahPotatoes/KP-Liberation/releases/tag/v0.97S2

Bugs found so far

Related Task Description Reported by
Nothing found so far

Sprint History

Sprint Quick Summary Details
1 Basic CTI functionality: Intro, Spawn, FOB deploy, capture sector, win campaign #404
@Wyqer Wyqer added the Backlog label Jun 3, 2018
@Wyqer Wyqer added this to the Sprint 3 milestone Jun 3, 2018
@Wyqer Wyqer added Done and removed Backlog labels Jun 11, 2018
@Wyqer Wyqer closed this as completed Jun 11, 2018
@Wyqer Wyqer mentioned this issue Jul 3, 2018
@Wyqer Wyqer mentioned this issue Aug 6, 2018
@veteran29 veteran29 added the dev-blog Blog article about development progress label Aug 6, 2018
@Wyqer Wyqer mentioned this issue Sep 10, 2018
@Wyqer Wyqer mentioned this issue Oct 8, 2018
@Wyqer Wyqer mentioned this issue Nov 5, 2018
@Wyqer Wyqer mentioned this issue Nov 29, 2018
@Wyqer Wyqer mentioned this issue Jan 1, 2019
@Wyqer Wyqer mentioned this issue Feb 25, 2019
@Wyqer Wyqer mentioned this issue Apr 8, 2019
@Wyqer Wyqer mentioned this issue May 5, 2019
@Wyqer Wyqer mentioned this issue Jun 30, 2019
@Wyqer Wyqer mentioned this issue Sep 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev-blog Blog article about development progress
Projects
None yet
Development

No branches or pull requests

2 participants