| Re: [elk-dev] A Plan |
Hi Camille, we haven't made any official decisions in that regard yet, but my plan would be to get an incubation release out before EclipseCon France. I'm not sure yet when we'll be able to leave the Incubation phase. First, I haven't read up on the prerequisites for doing so yet, and second, there's quite a bunch of things I'd like to get up and running before doing a 1.0 release (tests, a proper build setup, proper documentation, ...). Cheers, Christoph Daniel On 01/02/16 13:34, LETAVERNIER Camille wrote: > Hi Christoph Daniel, hi all, > > Do you have an idea what the timeframe could be for a 1.0 release of ELK? This timeframe is not critical for Papyrus itself, as we can (and plan to) provide the ELK Connector as an optional component (So we can afford a dependency on an incubation build), but some projects based on Papyrus would like to provide a deeper (non-optional) integration. However, Eclipse projects cannot depend on Incubation projects if they are not incubating themselves > > Do you think ELK could get a 1.0 release before June? Or will you provide a 0.10 (incubation) version before that? > > Thanks, > Camille > > -----Message d'origine----- > De : elk-dev-bounces@xxxxxxxxxxx [mailto:elk-dev-bounces@xxxxxxxxxxx] De la part de Christoph Daniel Schulze > Envoyé : mercredi 20 janvier 2016 11:12 > À : Eclipse Layout Kernel Developers <elk-dev@xxxxxxxxxxx> > Objet : [elk-dev] A Plan > > Hi everyone, > > we made plans for the next release of KIELER Pragmatics yesterday. The > plan has implications for how we will proceed with ELK, so here it is. > > We will release the next KIELER Pragmatics version on Feb 9th. Once that > is done, we're free to break our nightly Pragmatics build, so that's > when we'll start migrating all the changes over to ELK that have been > piling up since ELK was forked. Once that's complete, we can start > changing Pragmatics such that it depends on ELK. That would be an > excellent time for a first official ELK release, provided that the code > review is complete by then. > > After that's all done, I'll start implementing the new graph structure > we've talked about in our first ELK meetings. > > 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 >
Attachment:
signature.asc
Description: OpenPGP digital signature