Thanks, Matthias, I have reopened this. On Wed, Mar 14, 2018 at 1:26 PM, Matthias Paul Scholz < [email protected]> wrote:
> I've noticed that Bug #514731 has been set to "Fixed" but I can't see any > code that has been checked in for the actual resolution of the bug, only > the test that reproduces it? > > 2018-03-13 12:15 GMT+01:00 Wim Jongman <[email protected]>: > >> Dear Committers, >> >> We are running towards the finals days of the release period. I am going >> to ask for a review in a few days. >> >> Please go over your bugs [1]. They should be fixed, closed or moved to >> the next milestone 2.1.0. >> >> Please add your work to the New and Noteworthy [2]. >> >> Cheers, >> >> Wim >> >> [1] https://projects.eclipse.org/projects/technology.nebula/rele >> ases/2.0.0/bugs >> [2] https://wiki.eclipse.org/Nebula/Releases/2.0.0/NaN >> >> _______________________________________________ >> nebula-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/nebula-dev >> > > > _______________________________________________ > nebula-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/nebula-dev >
_______________________________________________ nebula-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/nebula-dev
