Hello community, I am delighted to have been appointed as the Platform 2.3 release manager and happy to announce the already commenced process leading to the release. You don’t want to miss out being part of the contribution to this process, so feel free to volunteer in any of the areas below
Developer
Point of contact
Testing
Documentation
Advise
There are a couple of issues that need to be fixed including those associated with the bundled modules. These need to be resolved as early as possible so there is enough time for testing before the final release. I’m therefore inviting the community to contribute to this achievement.
Do you want to roll through the dev stages? From the road map are some nice starters to contribute to.
Thanks to the @devs who are already making this a reality.
@ruhanga I will try to not forget, but if I do please don’t hesitate to remind me to document the wiki about the support for alternate authentication schemes.
Thanks for the heads up @gcliff . You can watch for more upcoming issues to fix and updates on progress @here and don’t hesitate to take on any other task you are comfortable with.
Thank you @c.antwi, I am designing a schedule for the meetings around the release process that will take place atleast every once a week. Since this has’t been part of the recent past experiences of release managers, I will update our events calendar with effect from next week to reflect these meetings so community input can be leveraged as much as possible towards the final release.
@mozzy, there is going to be a design call today at 9:00pm EAT to discuss Platform performance improvements. You are welcome to join. Please also note that release process discussions have a time slot during the Office Hours on Wednesday 3:00pm - 5:00pm EAT (12pm - 2pm UTC). You are welcome as well to join every week at that time.
Thank you very much @c.antwi. Sorry for the delayed response.
This is the summary of the current release process activities currently.
1. Activities for the past week have been around figuring potential library versions to be upgraded to for the different libraries that Platform depends on. Here is a google sheet with potential libraries to upgrade. The Apache velocity engine library is already being worked on.
2. No blockers currently
3. Determine what library upgrades get precedence.
4. This weeks activities include having tasks curated to upgrade the chosen libraries.
@ruhanga though you can do this yourself, but as the release manager, you could simply mobilise community resources to do those things. That way, the whole burden does not fall on you.
@ruhanga Could you provide us with a Release schedule indicating which module/ feature is being working on when? We have about 6 weeks till the completion of the release cycle, meaning that all works should be completed at the latest 24th May 2019.
