Big +1 for that ;-)

Chris


Am 06.03.19, 21:26 schrieb "Julian Feinauer" <j.feina...@pragmaticminds.de>:

    Hi Chris,
    
    No offense. I agree that we should not stress those lovely people more than 
necessary.
    So we keep our aim on 0.4 (with whatever accumulates till then) for now and 
start regular releases when graduated.
    
    Is this a plan?
    
    Julian
    
    Von meinem Mobiltelefon gesendet
    
    
    -------- Ursprüngliche Nachricht --------
    Betreff: Re: [DISCUSS] Release Strategy for future releases
    Von: Christofer Dutz
    An: dev@plc4x.apache.org
    Cc:
    
    Hi Julian,
    
    I would +1 this, but please have one thing in Mind ... every release we do 
requires us to check it (of course) ... but also we have to have people in the 
Incubator also validate these releases.
    Some people there are under heavy load and I would not like to increase 
this load too much.
    
    But how about starting with that as soon as we have left the incubator? I 
would really like that.
    
    Chris
    
    
    Am 06.03.19, 09:15 schrieb "Julian Feinauer" <j.feina...@pragmaticminds.de>:
    
        Hi all,
    
        perhaps some may find this email too early (as we are still in the 
process of doing a Release) but I want to ask / discuss about how we plan to do 
releases in the future.
        Up till now, they were were infrequent due to the early stage of the 
project but now I think we have stabilized well, we have stable APIs and mostly 
new features coming in.
        One problem we had most of the time was, that we had to work on “forked 
releases” because the last official release lacked (newer) features we needed.
        Thus, I suggest that we start to release more often or even on a 
regular schedule (like e.g. Calcite does it) to ship the new features soon.
        Also this could help us, to teach more people how to release / rm.
    
        As we are mostly shipping features, there’s nothing speaking against 
doing minor (i.e. compatible) releases which makes it really easy for users to 
update.
        Perhaps, we could aim for monthly releases (if we have things to 
release) and already start the setup for that. I am really eager to get the 
PLC4X-88 (Triggered Scraper) merged and then shipped!
        Next would then be 0.3.2 in early April.
    
        What do you think of that concrete and more general?
    
        Julian
    
        PS.: If we move forward with graduation the release process is also 
becoming a bit easier, as there’s only one vote necessary (and no longer the 
second vote from the IPMC)
    
    
    

Reply via email to