Releasing EMFText

[nbrouwers]

We use EMFText in several locations within our transformation chain. A automated build environment to build our product is currently being implemented. Would it be possible to create formal releases of EMFText once in a while? This will help us to significantly to keep our toolsmith environments and build environments in sync with each other. This is more cumbersome when 'only' nightly builds of EMFText are available.

Thanks!

[mirkoseifert]

Hi,

since the majority of the work that is currently going on with EMFText is bug fixing, we find it hard to decide when to release :)

We could do a monthly release or something similar, but this feels kind of arbitrary.

When you setup you build environment you can equally refer to a specific commit instead of the head, which allows you to have a stable basis for your builds. This way you can decide which version of EMFText you consider 'released'.

We do the same for our own products and tools that rely on EMFText.

Would that work for you?

[rolftheunissen]

The majority may be bug fixing, but if somebody new to EMFText enters the website it seems that version 1.4.1 is just out. So that sounds like the latest and greatest there is. Nobody starts using an nightly build when using the a new tool. So the first impression will be worse then with the newest version.

If you are not going to release, please make sure that you also add a date to the release of 1.4.1, so that u do not have the impression that this is the latest. But if u add that, it may seem that the project is dead, because it did not do any release in over 2 years.

Furthermore, other tool providers will not include your plugin if you do not do any release. For instance, 'https://yoxos.eclipsesource.com/places/node/org.emftext.sdk.feature.group'.

When u have a hard time deciding, eclipse has fixed release dates you could follow them.