Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [xtext-dev] 2.11 release is approaching
Hi all,

when scheduling the release review I overlooked a message on the top of the website asking me to additionally send a mail to the emo.
I did that only today, but due to fixed release review dates the emo pushed the release date to February 1st. 
Sorry for that.

Regards,
Sven

2017-01-03 17:03 GMT+01:00 Miro Spönemann <miro.spoenemann@xxxxxxxxxx>:
I can take care of the Eclipse Help, created eclipse/xtext-eclipse#149 for that.

I removed some issues from the 2.11 milestone on GitHub since nobody seemed to work on them. In particular, I removed all xtext-idea issues: I don’t believe we’ll be able to bring the IDEA integration into a proper state within the next few weeks, so quite probably we’ll have to drop the 2.11 release for xtext-idea.

The remaining issues are listed here:


I propose that we all keep an eye on this list to make sure it’s empty when the release is done (either by fixing issues or by removing them from the release milestone). We should also check whether there are closed issues that should be assigned to the release milestone so we can easily generate a list of fixed bugs.

Cheers
  Miro


On 2 Jan 2017, at 15:39, Christian Dietrich <christian.dietrich@xxxxxxxxx> wrote:


Hi,

Who will update the eclipse help from the website maintenance branch?

Am 02.01.17 um 15:34 schrieb Sven Efftinge:
Hi & Happy New Year to everyone,

as the release date for 2.11 is approaching we need to do more testing
and slow down changing the code base.

I suggest to stop development of any features in our mature code base
and only do fixes that obviously improve the current status quo. That
means no fixes for minor problems, that could introduce major issues.

Starting one week before the release (i.e. January 17th) we should only
add changes for important blockers.

*Testing *

For testing we used to have a testing plan, where everyone is encouraged
to participate and cover as much of the testing as possible. By using a
plan we keep track of what has been tested and what not, avoiding
duplicated efforts and missing important scenarios.

https://github.com/eclipse/xtext/wiki/Xtext-2.11-Test-Plan

Please feel free to add test items as you wish and test stuff that is
not listed (adding it afterward would be good).

*Release Notes*
*
*
Based on Karsten's suggestion I added an initial draft for a release
notes document to a new branch (website-master) on the Xtext repository.

https://github.com/eclipse/xtext/tree/website-master

Cheers,
Sven
--
Dr. Miro Spönemann
Software engineer and consultant

TypeFox GmbH
Am Germaniahafen 1, 24143 Kiel


Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
Geschäftsführer: Sven Efftinge, Dr. Jan Köhnlein, Moritz Eysholdt


_______________________________________________
xtext-dev mailing list
xtext-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/xtext-dev



--
Sven Efftinge

TypeFox GmbH
Am Germaniahafen 1
24143 Kiel

Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385
Managing Directors: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein

Back to the top