Recently the development team decided to introduce some agility into the development process.
With that in mind two-week sprints have been started – the first sprint though was for one week.
Sprint 1 just closed. We thought it would be good to share the details of what transpired with the users.
Sprint 1: Sep 20, 2019–Sep 27, 2019
8 issues fixed:
- No writing rights for Calendar on Google agenda (calendar)
- Whole day events from outlook not opened correctly (calendar)
- Button not very beautiful in etar (calendar)
- Crash with accept or decline an invitation (calendar)
Unable to edit & sync contacts : Address book (Gmail) Authentication failed(Account Manager)
-Only one out of several calendars from one Google account could be selected (Account Manager)
-Mail app can’t handle live/outlook/hotmail accounts (mail)
- Bliss Launcher crash when opening web shortcut (launcher)
5 issues closed because non-reproducible:
- Get calender to sync with Google calender. (calendar)
- Syncing errors when Account manager tries to sync Contacts or calendar
- Crash when accessing an account (mail)
- /e/ 0.2 : Mail : NullPointerException : Attempt to invoke interface m…(mail)
- Cannot add an orange.fr account (mail)
- Autodiscover/autoconfig no longer working (mail)
From what we defined at the beginning, only 2 issues remain:
- No invitation sent to attendees calendar : we finally discovered today what is the cause of the issue. We will need more time to fix it. Hopefully for the next Sprint
- Email (google) account fails to sync (mail) : not fixed, but if the Google account is added from AccountManager, it works perfectly. Report the fix to the next Sprint
The bugs which got fixed will be tested by a team of volunteers testers from the users .
If you remember sometime back we had shared details of a plan to create a testing team of users who would get a build with these fixes to test out. We have got some users who volunteered to help with the testing. At present we are keeping the numbers small and will increase as we firm up the process.
If the test team clears the build then that build will be released to the wider user group as part of the dev builds.
If the test team does not clear the build then it is back to the developers.
We should be sharing the test build with our testing team by today EOD – 2 Oct 2019.
We are working on a plan to integrate enhancements and bug fixes in these sprints.
Stay tuned for further updates.