+1 , Go Mike !

Regards,
Vishwas

> On May 23, 2020, at 4:37 AM, Michael Vorburger <[email protected]> wrote:
> 
> Hello everyone, 
> 
> I'm currently having lots of fun toying around with JIRA (watch 
> FINERACT-1000...), and one thing I'd like us to do more frequently in this 
> project is to "celebrate our successes". 
> 
> How would everyone feel about a regular weekly email blast with all issues 
> resolved within the last week? Too much, spam - or useful to the community? 
> 
> Below is an example for the past 7 days... 4 contributors together have 
> resolved 21 issues in the last week - not too bad, right? ;-)
> 
> Best,
> M.
> 
> 
> ---------- Forwarded message ---------
> From: <[email protected]>
> Date: Sat, May 23, 2020 at 1:30 PM
> Subject: [jira] Subscription: Fineract Resolved Last Week
> To: <[email protected]>
> 
> 
>  
>  
> Issue Subscription
> Filter:       Fineract Resolved Last Week (21 issues) 
> Subscriber:   vorburger
> T     Patch Info      Key     Summary Assignee        Reporter        P       
> Status  Resolution      Created Updated Due     Development
>               FINERACT-938    
> Document (or drop) use of Xerces2 (without requiring NekoHTML)
> Michael Vorburger     Michael Vorburger       <noname>        RESOLVED        
> Fixed   07/May/20       22/May/20               
>               FINERACT-940    
> The package javax.xml.parsers is accessible from more than one module: 
> <unnamed>, java.xml (Eclipse only?)
> Michael Vorburger     Michael Vorburger       <noname>        RESOLVED        
> Fixed   08/May/20       22/May/20               
>               FINERACT-993    
> Ignore StorageTest IT test
> Michael Vorburger     Yemdjih Kaze Nasser     <noname>        RESOLVED        
> Fixed   22/May/20       22/May/20               
>               FINERACT-994    
> Do not try to deploy to fineract.dev on forked branches
> Michael Vorburger     Yemdjih Kaze Nasser     <noname>        RESOLVED        
> Fixed   22/May/20       22/May/20               
>               FINERACT-970    
> Automatically continuously integrate and deploy ("CI/CD") Fineract develop 
> branch to fineract.dev
> Michael Vorburger     Michael Vorburger       <noname>        RESOLVED        
> Fixed   10/May/20       22/May/20               
>               FINERACT-956    
> Logging missing / broken (since Spring Boot and/or Java 11 upgrade)
> Michael Vorburger     Michael Vorburger               RESOLVED        Fixed   
> 09/May/20       21/May/20               
>               FINERACT-952    
> Remove un-used "Send messages to Email gateway" Job
> Michael Vorburger     Michael Vorburger       <noname>        RESOLVED        
> Fixed   08/May/20       21/May/20               
>               FINERACT-858    
> Errors (JobExecutionException) in Cron Jobs loose exception root cause details
> Michael Vorburger     Michael Vorburger       <noname>        RESOLVED        
> Fixed   08/Mar/20       21/May/20               
>               FINERACT-983    
> /actuator/info is empty in container
> Michael Vorburger     Michael Vorburger       <noname>        RESOLVED        
> Fixed   16/May/20       19/May/20               
>               FINERACT-979    
> Flyway cannot apply migrations because default schema history table name in 
> new Flyway version now is flyway_schema_history instead of schema_version
> Michael Vorburger     Michael Vorburger               RESOLVED        Fixed   
> 15/May/20       16/May/20               
>               FINERACT-989    
> SpotBugs problems (no longer) show up in build failures
> Michael Vorburger     Michael Vorburger       <noname>        CLOSED  
> Duplicate       21/May/20       21/May/20               
>               FINERACT-978    
> java.lang.reflect.InvocationTargetException at 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) Caused 
> by: java.lang.IllegalStateException: Logback configuration error detected:
> Michael Vorburger     Michael Vorburger       <noname>        RESOLVED        
> Duplicate       15/May/20       21/May/20               
>               FINERACT-975    
> /tmp needs to be writeable in container
> Michael Vorburger     Michael Vorburger       <noname>        CLOSED  
> Duplicate       14/May/20       20/May/20               
>               FINERACT-909    
> Remove Tomcat Welcome Default App from Fineract Container 
> Michael Vorburger     Michael Vorburger       <noname>        CLOSED  
> Duplicate       21/Apr/20       19/May/20               
>               FINERACT-911    
> Alternative way(s) to set Git revision on CI systems which do shallow git 
> clone
> Michael Vorburger     Michael Vorburger       <noname>        CLOSED  Won't 
> Do        26/Apr/20       17/May/20               
>               FINERACT-953    
> Upgrade ical4j from ancient version 1.0.7 to current 3.0.18
> Natasha Natarajan     Michael Vorburger       <noname>        RESOLVED        
> Fixed   09/May/20       22/May/20               
>               FINERACT-991    
> Upgrade RAT plug-in from 0.3.1 to 0.6.0
> Petri Tuomola Petri Tuomola   <noname>        RESOLVED        Fixed   
> 21/May/20       22/May/20               
>               FINERACT-830    
> Use distroless base image instead of bitnami/tomcat in container
> Petri Tuomola Michael Vorburger       <noname>        RESOLVED        Fixed   
> 14/Jan/20       21/May/20               
>               FINERACT-897    
> Make Fineract compatible with both MySQL5.7 and MySQL 8
> Yemdjih Kaze Nasser   Michael Vorburger       <noname>        RESOLVED        
> Fixed   18/Apr/20       22/May/20               
>               FINERACT-986    
> Update spotbugs to v4.2.0
> Yemdjih Kaze Nasser   Yemdjih Kaze Nasser     <noname>        RESOLVED        
> Resolved        20/May/20       21/May/20               
>               FINERACT-964    
> Bump json-path from 0.9.1 to 2.4.0
> Yemdjih Kaze Nasser   Michael Vorburger       <noname>        RESOLVED        
> Fixed   10/May/20       20/May/20               
> You may edit this subscription here.
>  
> This message was sent by Atlassian Jira (v8.3.4#803005-sha1:1f96e09)  
>  
> <noname>

Reply via email to