Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tools-pmc] PMC Approval for GEF 4.1.0 (Neon.1)

Thanks David. I have added a comment to the release record that points out that all API extensions are motivated by bugfixing reasons and that the  API is full backwards compatible.

Best Regards,
Alexander

Am 16.08.2016 um 21:07 schrieb David M Williams <david_williams@xxxxxxxxxx>:

Thanks for the reminder. I think it would be better to mention the reason for the 'minor' change "some API changes required for bug fixes -- but no breaking API changes" (and, yes, just as well mention "what changed" either here, list the bugs, or maybe you have "migration notes").

That is my suggestion to make it better. But, I also will not hold up your release based on that, so
+1 from me.

Thanks,




From:        Alexander Nyßen <nyssen@xxxxxxxxx>
To:        Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>,
Date:        08/16/2016 11:24 AM
Subject:        Re: [tools-pmc] PMC Approval for GEF 4.1.0 (Neon.1)
Sent by:        tools-pmc-bounces@xxxxxxxxxxx




Hi David,

just to be clear here, do I need to take further action or can it be approved without?

Regards
Alexander

Am 15.08.2016 um 16:13 schrieb Alexander Nyßen <nyssen@xxxxxxxxx>:

Hi David,

while its technically a minor, the motivation of this release clearly is to provide bugfixes, that’s the reason I pointed it out. The following bugzillas have affected the API: 497224, 498045, 495968, 496777. They do not really introduce new features but are more or less required to properly fix issues. The only actual feature that was added is 477980, which this did not affect public API. Do you think it adds value to point these out explicitly?

Regards,
Alexander


Am 15.08.2016 um 15:55 schrieb David M Williams <david_williams@xxxxxxxxxx>:

This sounds fine to me, but ....

It seems contradictory to say "...
bugfix release that contains minor (1.1.0) or micro (1.0.1) revisions ... "

That is, normally a "bugfix release" would only increment service fields, and not even need a release review.


My guess is you have added some new feature or added some new API that requires that 1.1.0 bump, and if that is the case, I think you should be a little more explicit about what has  changed (and/or point to bugs where they are described).


Make sense?


P.S. I hope the info wasn't there and I just missed it. :/






From:        
Alexander Nyßen <nyssen@xxxxxxxxx>
To:        
Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>,
Date:        
08/15/2016 06:35 AM
Subject:        
[tools-pmc] PMC Approval for GEF 4.1.0 (Neon.1)
Sent by:        
tools-pmc-bounces@xxxxxxxxxxx




Dear PMC members,

please approve the Graphical Editing Framework (GEF) 4.1.0 release that is scheduled to coincidate with Eclipse Neon.1.

The release review material can be found at
https://projects.eclipse.org/projects/tools.gef/releases/4.1.0-neon.1.

The IP log has been submitted for review (see
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11829).

Best Regards,
Alexander
--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743


http://www.itemis.de
alexander.nyssen@xxxxxxxxx

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino


[attachment "signature.asc" deleted by David M Williams/Raleigh/IBM]
_______________________________________________
tools-pmc mailing list

tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/tools-pmc

_______________________________________________
tools-pmc mailing list

tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/tools-pmc

--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

http://www.itemis.de
alexander.nyssen@xxxxxxxxx

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino




--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

http://www.itemis.de
alexander.nyssen@xxxxxxxxx

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino


[attachment "signature.asc" deleted by David M Williams/Raleigh/IBM] _______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tools-pmc

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

--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

http://www.itemis.de 
alexander.nyssen@xxxxxxxxx 

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino



Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail


Back to the top