Re: [escet-dev] Additional release soon?

["Beek, Bert van" <D.A.v.Beek@xxxxxx>]

Hi all,

I would be very happy indeed with an additional milestone release v0.2-M1. Having another milestone release when issue #30 (https://gitlab.eclipse.org/eclipse/escet/escet/-/issues/30) is resolved would also be greatly appreciated.

Bert

> On 17 May 2021, at 10:17, Hofkamp, Albert <A.T.Hofkamp@xxxxxx> wrote:
> 
> Making a release is fine by me. Don't think anyone is opposed to it.
> From: escet-dev <escet-dev-bounces@xxxxxxxxxxx> on behalf of Dennis Hendriks <dh_tue@xxxxxxxxxxx>
> Sent: Monday, May 17, 2021 09:55
> To: escet developer discussions <escet-dev@xxxxxxxxxxx>
> Subject: Re: [escet-dev] Additional release soon?
>  
> Hi,
> 
> Indeed that is always possible. They are essentially our version of nightly builds. However, note that the version you use can disappear at any moment, as new builds are done.
> 
> I think this is independent of milestone releases, which we are also required to create at least per release. I still propose to create one this week. I can do it, it is not too much work.
> 
> Dennis
> 
> Van: escet-dev <escet-dev-bounces@xxxxxxxxxxx> namens Hofkamp, Albert <A.T.Hofkamp@xxxxxx>
> Verzonden: maandag 17 mei 2021 09:41
> Aan: escet developer discussions <escet-dev@xxxxxxxxxxx>
> Onderwerp: Re: [escet-dev] Additional release soon?
>  
> Hi,
> 
> Can't you just use a development build instead of an official release? https://ci.eclipse.org/escet/job/ESCET%20build/job/develop/lastStableBuild/
> 
> A version is built and tested after each merge into develop with CI. It's the same thing as a release, except for lack of version numbers. You also shouldn't expect stability, as it's 'develop', but the difference is very small in practice.
> 
> Albert
> From: escet-dev <escet-dev-bounces@xxxxxxxxxxx> on behalf of Dennis Hendriks <dh_tue@xxxxxxxxxxx>
> Sent: Saturday, May 15, 2021 11:43
> To: escet developer discussions <escet-dev@xxxxxxxxxxx>
> Subject: Re: [escet-dev] Additional release soon?
>  
> Hi Bert,
> 
> Given your question yesterday about the bug in the CIF PLC generator, I was already waiting for this question :)
> 
> An official release has some overhead associated with it, such as updating version numbers, release record, etc. As such, an extra official release would not be my preference.
> 
> However, we have to make at least one milestone release before every official release (another reason we can't do an official release yet). Now may be a good time to release v0.2-M1. Besides the naming an thus expectations on quality/testing, there should be no practical differences for end users. They can download it and use it just like an official release. The website would then however be at https://eclipse.org/escet/v0.2-M1/ rather than https://eclipse.org/escet/, as it is not yet the v0.2 release.
> 
> We could release v0.1-M1 as soon as possible (e.g. the coming week), and make another milestone release in a few weeks, before the official release end of June.
> 
> What do you think?
> 
> Dennis
> 
> Van: escet-dev <escet-dev-bounces@xxxxxxxxxxx> namens Beek, Bert van <D.A.v.Beek@xxxxxx>
> Verzonden: zaterdag 15 mei 2021 09:47
> Aan: escet developer discussions <escet-dev@xxxxxxxxxxx>
> Onderwerp: [escet-dev] Additional release soon?
>  
> Hi Dennis,
> 
> Would it be possible to have an additional release soon, much before end of June? Especially since so many bugs have already been fixed. It would be nice to still have resolved issue #30 (https://gitlab.eclipse.org/eclipse/escet/escet/-/issues/30), because in the current release for Windows, after having installed the JDK and Eclipse ESCET, you also need to manually set the path to the JDK in eclipse.ini.
> 
> Bert
> _______________________________________________
> escet-dev mailing list
> escet-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/escet-dev