Hi everyone, ... just wanted to send out a reminder that time is running out for the next release 1.4.0. We have one day left and at least 27 open or in progress tickets on Jira.
Could you please check tickets assigned to you and close/resolve them if they are done. If you don't have enough permissions to do that then please let me know. Please also check Ed's notes: https://docs.google.com/spreadsheets/d/1X3aXUM2lzjX5-2vc-nHgmU7KeI6rQ5Sj31qh-8-9dRw/edit?usp=sharing Thanks again to everyone for jumping in and helping out. Cheers, Aleks On Thu, Aug 13, 2020 at 8:55 PM Ed Cable <[email protected]> wrote: > Hi all, > > To assist in the process I tried to do a quick review of the open PRs and > send a reminder to those who have pending actions or have been requested to > provide a review. > > I tried to catalog which should still be on target for 1.4 release and > which are targeted for 1.5 or are low enough priority that shipping in 1.5 > is fine as well. > > My quick notes are in this sheet: > > > https://docs.google.com/spreadsheets/d/1X3aXUM2lzjX5-2vc-nHgmU7KeI6rQ5Sj31qh-8-9dRw/edit?usp=sharing > > On Wed, Aug 12, 2020 at 2:55 AM Aleksandar Vidakovic < > [email protected]> wrote: > >> Hi, >> >> ... just a reminder to everyone: release 1.4.0 starts in one week. We >> have currently 30 issues related to version 1.4.0 that are still open/in >> progress. >> >> If you have anything urgent that should be included in the next release >> then please create a Jira ticket, label it with version 1.4 and create a PR. >> >> Thanks again for your help. >> >> Cheers, >> >> Aleks >> >> On Mon, Aug 10, 2020 at 11:20 PM Aleksandar Vidakovic < >> [email protected]> wrote: >> >>> @Michael Vorburger <[email protected]> >>> Would you have some time this week for a quick call? Just ensure that >>> I'm not missing any of the work you put into this before... I can make >>> myself available pretty much any time this week... >>> >>> Thanks for your help and looking forward to meeting you... >>> >>> Cheers, >>> >>> Aleks >>> >>> On Mon, Aug 10, 2020 at 9:36 PM Ed Cable <[email protected]> wrote: >>> >>>> @Michael Vorburger <[email protected]> and @Aleksandar Vidakovic >>>> <[email protected]> I was a little confused as to the >>>> purpose of the umbrella issue for tracking activity ( >>>> https://issues.apache.org/jira/browse/FINERACT-873) We are still using >>>> the fix version of 1.4 and release notes to actually track what's going >>>> into the release, correct? >>>> >>>> While these of course need to be updated, the release notes I posted >>>> back in November (when I started the process according to how we currently >>>> had it codified) is here: https://s.apache.org/xivc8 >>>> >>>> Just so it wasn't falling through the cracks, Michael - did you expect >>>> Aleks to be taking the lead on updating fix versions of tickets to reflect >>>> if they're in 1.4 or a future release? >>>> >>>> >>>> https://issues.apache.org/jira/browse/FINERACT-1109?jql=project%20%3D%20FINERACT%20AND%20fixVersion%20%3D%201.4.0 >>>> >>>> Thanks, >>>> >>>> Ed >>>> >>>> >>>> >>>> On Fri, Aug 7, 2020 at 6:17 AM Aleksandar Vidakovic < >>>> [email protected]> wrote: >>>> >>>>> Perfect, thanks a ton. >>>>> >>>>> On Fri, Aug 7, 2020 at 3:01 PM Percy Enoabane <[email protected]> >>>>> wrote: >>>>> >>>>>> Will create the Jira issues and link them to FINERACT-826. >>>>>> >>>>>> On Fri, Aug 7, 2020 at 10:29 AM Aleksandar Vidakovic < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Percy, >>>>>>> >>>>>>> ... yes, everything that is related to FINERACT-826 should then be >>>>>>> moved to v1.5.0. I've updated your Jira task to reflect the correct >>>>>>> version >>>>>>> number (moved from v1.4.0 to v1.5.0). >>>>>>> >>>>>>> Could you let me know which Jira issues/PRs are related to >>>>>>> FINERACT-826? Then we can mark and organize them accordingly (to save >>>>>>> some >>>>>>> time for the next release cycle). >>>>>>> >>>>>>> Thanks again for the heads-up and your help. >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> Aleks >>>>>>> >>>>>>> On Fri, Aug 7, 2020 at 10:23 AM Percy Enoabane < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Aleks, >>>>>>>> >>>>>>>> There is some work <https://github.com/apache/fineract/pull/1179> >>>>>>>> in progress targeted for v1.5.0(to avoid any "risk" upcoming 1.4.0). >>>>>>>> Subsequent work on PRs that depend on this to be merged in the develop >>>>>>>> branch should only come after the v1.4.0 branch is created? >>>>>>>> >>>>>>>> Percy >>>>>>>> >>>>>>>> On Wed, Aug 5, 2020 at 2:19 PM Aleksandar Vidakovic < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi everyone, >>>>>>>>> >>>>>>>>> Based on our "How to Release Apache Fineract" process documented >>>>>>>>> at https://cwiki.apache.org/confluence/x/DRwIB : >>>>>>>>> >>>>>>>>> I will create a v1.4.0 branch off develop in our git repository at >>>>>>>>> https://github.com/apache/fineract on Thursday, August 20, 2020. >>>>>>>>> >>>>>>>>> The release tracking umbrella issue for tracking all activity in >>>>>>>>> JIRA is https://issues.apache.org/jira/browse/FINERACT-873 for >>>>>>>>> this Fineract v1.4.0. >>>>>>>>> >>>>>>>>> If you have any work in progress that you like to see included in >>>>>>>>> this release, please add "blocking" links to the release JIRA issue. >>>>>>>>> >>>>>>>>> I am the release manager for this release. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Aleks >>>>>>>>> >>>>>>>> >>>> >>>> -- >>>> *Ed Cable* >>>> President/CEO, Mifos Initiative >>>> [email protected] | Skype: edcable | Mobile: +1.484.477.8649 >>>> >>>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org >>>> <http://facebook.com/mifos> <http://www.twitter.com/mifos> >>>> >>>> > > -- > *Ed Cable* > President/CEO, Mifos Initiative > [email protected] | Skype: edcable | Mobile: +1.484.477.8649 > > *Collectively Creating a World of 3 Billion Maries | *http://mifos.org > <http://facebook.com/mifos> <http://www.twitter.com/mifos> > >
