| Thanks Arjan for your great tasks overview!
Yes, the priority now is GF integration:
It would be great if you start working on it asap.
Thanks, Dmitry
Thanks Wayne,
most importantly however is knowing if there are any pending tasks?
Since I'm just jumping in I wanted to know if there's anything that is immediately required? For instance I noted that the module name was not updated to jakarta.*
Which one are you referring to? Looking at the pom.xml it looks everything has been set already to Jakarta.
See here:
I was wrongly looking at the automatic module name.
Is a release required? is the Hip (I believe is the automated integration test) build setup?
A release is required indeed (GF references javax.annotation-api). It's not HIP but JIPP ;) It already has been requested and setup.
Great!
Awesome!
Left to do is updating the poms in GF 5.1 with the new maven coordinates and running the TCK.
Perfect! I'll try to orient myself!
Thanks a lot for this information Arjan :)
Sincerely, - Ray
Kind regards, Arjan
Sorry for the delay.
The Project Leads are the primary liaison between the project team and the Eclipse Management Organization.
As the first tier in the Project Leadership Chain, they share responsibility for ensuring that the project committers are properly implementing the EDP, EFSP (when appropriate), and the Eclipse IP Policy.
I don't have a specific list. The general requirement is that they are responsible for ensuring that the project is being a good open source project as defined by the EDP. They generally take responsibility for keeping project metadata up-to-date, ensure that somebody is actually taking care of builds, coordinate planning, etc.
HTH,
Wayne
Wayne, Is there a list of responsibilities fall only to the Lead, or actions that only a Lead can take? The Handbook really only suggests characteristics for a lead. What are the specific responsibilities that only a Lead can (or must) perform?
-- Ed
On 11/20/2018 9:17 AM, Wayne Beaton wrote:
Greetings PMC.
As discussed on our call today, the Eclipse Project for Common Annotations ( ee4j.ca) is without a Project Lead, which effectively makes the project dysfunctional. Given this state, the PMC decided that we will exercise our responsibility to ensure the proper functioning of the project by appointing Raymond Auge into this role.
Note that this is an exception to the process that we're exercising only because it is required to successfully bootstrap the project.
Thanks,
Wayne
-- Wayne Beaton Director of Open Source Projects | Eclipse Foundation, Inc
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--
Wayne Beaton Director of Open Source Projects | Eclipse Foundation, Inc.
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--
|
