Re: [elk-dev] Release Plans

[Christoph Daniel Schulze <cds@xxxxxxxxxxxxxxxxxxxxxx>]

Nice, I've started getting a few bugs fixed for the release and plan on
getting the release started tomorrow or Friday. :)

Cheers,
 Chris

On 20.02.19 20:02, Ulf Rüegg wrote:
> A bit late but I agree with Miro: 0.5.0.
> 
> Ulf
> 
> Am Mo., 11. Feb. 2019 um 14:10 Uhr schrieb Christoph Daniel Schulze
> <cds@xxxxxxxxxxxxxxxxxxxxxx <mailto:cds@xxxxxxxxxxxxxxxxxxxxxx>>:
> 
>     Hi,
> 
>     I'm still fixing bugs and I have an exam to prepare, so I won't be able
>     to get everything ready on such short notice. Getting the release review
>     approved on March 6th is the best I can do. But yeah, personally I'm
>     leaning towards 0.5.0 as well (I called that a major release because for
>     incubating projects it kind of is ;) ).
> 
>     Cheers,
>     Chris
> 
>     On 11.02.19 14:07, Miro Spönemann wrote:
>     > Hi,
>     >
>     > the new self-loop router (#359) and the new rectangle packer
>     (#383) are
>     > quite substantial changes, so I’d propose a minor release (0.5.0). If
>     > you schedule a release review now, we should still be on time to
>     let it
>     > conclude on Feb 27th, which gives us roughly two weeks until the final
>     > release.
>     >
>     > Cheers
>     >   Miro
>     >
>     >
>     >> On 11. Feb 2019, at 10:38, Christoph Daniel Schulze
>     >> <cds@xxxxxxxxxxxxxxxxxxxxxx <mailto:cds@xxxxxxxxxxxxxxxxxxxxxx>
>     <mailto:cds@xxxxxxxxxxxxxxxxxxxxxx
>     <mailto:cds@xxxxxxxxxxxxxxxxxxxxxx>>> wrote:
>     >>
>     >> Dear ELK developers,
>     >>
>     >> the world keeps revolving and demands a new release of our rather
>     >> impressive little software package. My suggestion would be this:
>     >>
>     >> - I take a look at Miro's pull request today.
>     >>
>     >> - I fix an important bug with ports today.
>     >>
>     >> - The release plans commence.
>     >>
>     >> The big question is whether to push out major release 0.5.0 or minor
>     >> release 0.4.2. What we do may need to come down to time
>     constraints: if
>     >> our clients require the release in February, a major release is
>     out of
>     >> the question. Otherwise it's purely a matter of how important we feel
>     >> the changes were, and if they are likely to break existing code.
>     >>
>     >> Any opinions on the matter?
>     >>
>     >> Cheers,
>     >> Chris
>     >>
>     >> _______________________________________________
>     >> elk-dev mailing list
>     >> elk-dev@xxxxxxxxxxx <mailto:elk-dev@xxxxxxxxxxx>
>     <mailto:elk-dev@xxxxxxxxxxx <mailto:elk-dev@xxxxxxxxxxx>>
>     >> To change your delivery options, retrieve your password, or
>     >> unsubscribe from this list, visit
>     >> https://www.eclipse.org/mailman/listinfo/elk-dev
>     >
>     > --
>     > Dr. Miro Spönemann
>     > Software engineer and consultant
>     >
>     > TypeFox GmbH
>     > Am Germaniahafen 1, 24143 Kiel
>     >
>     > https://typefox.io
>     > Tel.: +49 151 42679459
>     >
>     > Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
>     > Geschäftsführer: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein
>     >
>     >
>     > _______________________________________________
>     > elk-dev mailing list
>     > elk-dev@xxxxxxxxxxx <mailto:elk-dev@xxxxxxxxxxx>
>     > To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     > https://www.eclipse.org/mailman/listinfo/elk-dev
>     >
> 
>     _______________________________________________
>     elk-dev mailing list
>     elk-dev@xxxxxxxxxxx <mailto:elk-dev@xxxxxxxxxxx>
>     To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     https://www.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://www.eclipse.org/mailman/listinfo/elk-dev
>

Attachment: signature.asc
Description: OpenPGP digital signature