| Re: [elk-dev] Release Preparations: A Call to Action! |
Right, #39 is merged and #15 was moved to the next release. Also, our automatic build now produces signed plug-ins. I guess we're ready to create the release branch and submit the IP log for the release. I'll do that tomorrow unless someone stops me. Cheers, Christoph Daniel On 30/05/16 11:33, Miro Spönemann wrote: > I think it would be good to merge #39 and finish #15 before the release (I’ll try that today). > > Miro > > >> On 30.05.2016, at 10:39, Christoph Daniel Schulze <cds@xxxxxxxxxxxxxxxxxxxxxx> wrote: >> >> Greetings ELK developers, >> >> following our recent discussions, I have begun release preparations. >> There is no final date yet, but here is the current state of the release >> documentation: >> >> https://projects.eclipse.org/projects/modeling.elk/releases/0.1 >> >> I have also added a milestone for the release to our ticket system and >> have assigned all closed tickets to that milestone. >> >> There are two things you should do now: >> >> 1. Check if there is anything you would like to have changed in the >> release documentation. >> >> 2. I need to generate an IP log, which in turn will probably require me >> to setup a release branch. Are there any changes still waiting to be >> merged that should go into the release branch? If not, I will simply >> create the branch in the upcoming days. >> >> Cheers, >> Christoph Daniel >> >> _______________________________________________ >> elk-dev mailing list >> elk-dev@xxxxxxxxxxx >> To change your delivery options, retrieve your password, or unsubscribe from this list, visit >> https://dev.eclipse.org/mailman/listinfo/elk-dev > > > _______________________________________________ > elk-dev mailing list > elk-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/elk-dev >
Attachment:
signature.asc
Description: OpenPGP digital signature