I'm fine with this, so +1 from me.

G

On 12-07-19 09:46 AM, Tobias Wunden wrote:
> Hi,
> 
> it seems that 1.4 is taking up some speed again. However, trunk freeze was 
> initiated in February/March, and I suspect that some institutions have 
> developed things that would be ready to make it into the next release, which 
> is why I would like to propose an official merge window for 1.4 starting 
> Monday, July 23rd and ending on Friday, August 3rd.
> 
> The reason for this merge window is simple: I would like to increase the 
> attractiveness of 1.4 for adopters but mostly for developers, so there is a 
> vetted interest in moving 1.4 forward. I have talked to everyone present at 
> this week's developers meeting, and there are not a lot of merges that will 
> come in. However, it sounds that this additional merge phase would indeed 
> increase everyone's interest in 1.4.
> 
> To make sure that this merge window does not become a burden for Greg and 
> others, I also propose to impose the following requirements on a merge:
> 
> 1) The changeset needs to merge both with current trunk and 1.4
> 2) the changeset qualifies for "good code" (unit test, integration tests, 
> documentation)
> 3) The change is documented both on list and on the wiki 
> (http://opencast.jira.com/wiki/display/MH/Release+1.4)
> 
> Greg and myself, being the release managers of 1.4, will reserve the freedem 
> to reject patches that fail to fulfill either one of these requirements.
> 
> Thanks,
> Tobias
> _______________________________________________
> Matterhorn mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> 
> 
> To unsubscribe please email
> [email protected]
> _______________________________________________
> 


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to