Great, thanks Fred!

-- 
Sam Davis
Senior Software Engineer, Tasktop
Committer, Eclipse Mylyn
http://tasktop.com


On Fri, May 10, 2019 at 3:55 AM Frederic Gurr <
[email protected]> wrote:

> Hi,
>
> After merging https://git.eclipse.org/r/#/c/141899/ I have rebased and
> merged https://git.eclipse.org/r/#/c/141920/.
>
> @Sam: I'm not aware of anyone deliberately removing your commit rights
> for simrel. Please open a Bugzilla issue to resolve this:
>
> https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Cross-Project
> .
>
> Regards,
>
> Fred
>
> On 10.05.19 01:30, Sam Davis wrote:
> > Thanks. I would appreciate it if someone can merge that review for me
> > once the build is fixed.
> >
> > --
> > Sam Davis
> > Senior Software Engineer, Tasktop
> > Committer, Eclipse Mylyn
> > http://tasktop.com
> >
> >
> > On Thu, May 9, 2019 at 4:29 PM Matthias Wienand
> > <[email protected] <mailto:[email protected]>> wrote:
> >
> >     Hi,
> >
> >     I removed the old milestones and updated the GEF contribution, so
> >     the error will be gone once that is merged. I should have waited for
> >     the merge before removing the site, though. Sorry for the
> inconvenience.
> >
> >     Best regards,
> >     Matthias
> >     --
> >
> >     Matthias Wienand
> >     B.Sc. Softwaretechnik
> >     Software Engineer
> >
> >     Telefon: +49 231 9860 202
> >     Telefax: +49 231 9860 211
> >     Mobil:   +49 152 26802283
> >
> >
> >     [email protected] <mailto:[email protected]>
> >     http://www.xing.com/profile/Matthias_Wienand2
> >     http://www.itemis.de
> >
> >
> >     itemis AG
> >
> >     Am Brambusch 15-24
> >     44536 Lünen
> >
> >     Rechtlicher Hinweis:
> >     Amtsgericht Dortmund, HRB 20621
> >     Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Abdelghani
> El-Kacimi
> >     Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus,
> >     Jennifer Fiorentino
> >
> >>     Am 10.05.2019 um 01:23 schrieb Sam Davis <[email protected]
> >>     <mailto:[email protected]>>:
> >>
> >>     Hi, Mylyn will participate, and I have pushed a review touching
> >>     the aggrconfile, however I seem to no longer be a committer on the
> >>     simrel project for some reason??? I cannot approve the review and
> >>     had to sign-off on it. Also the build fails with an apparently
> >>     unrelated error about GEF:
> >>
> >>     https://git.eclipse.org/r/#/c/141920/
> >>
> >>         *16:18:25* Loading all repositories
> >>         *16:18:26* Unable to load repository file:/home/data/httpd/
> download.eclipse.org/tools/gef/updates/milestones/5.0.400M2_gef-master_5261
> <
> http://download.eclipse.org/tools/gef/updates/milestones/5.0.400M2_gef-master_5261
> >
> >>         *16:18:27* Unable to load repository p2:file:/home/data/httpd/
> download.eclipse.org/tools/gef/updates/milestones/5.0.400M2_gef-master_5261
> <
> http://download.eclipse.org/tools/gef/updates/milestones/5.0.400M2_gef-master_5261
> >
> >>         *16:18:27* Build failed! Exception was
> org.eclipse.core.runtime.CoreException: Not all repositories could be
> loaded (see log for details)
> >>         *16:18:28* Not all repositories could be loaded (see log for
> details)
> >>
> >>
> >>     --
> >>     Sam Davis
> >>     Senior Software Engineer, Tasktop
> >>     Committer, Eclipse Mylyn
> >>     http://tasktop.com <http://tasktop.com/>
> >>
> >>
> >>     On Thu, May 9, 2019 at 12:24 PM Wayne Beaton
> >>     <[email protected]
> >>     <mailto:[email protected]>> wrote:
> >>
> >>         My apologies if I gave the impression that anybody is late.
> >>         The deadline is tomorrow.
> >>
> >>         Wayne
> >>
> >>         On Thu, May 9, 2019 at 1:35 PM Matthias Wienand
> >>         <[email protected]
> >>         <mailto:[email protected]>> wrote:
> >>
> >>             Hi Wayne,
> >>
> >>             I just updated GEF.aggrcon file. I had it on my list, but
> >>             did not get to it yesterday… Sorry for being so late.
> >>
> >>             Best regards,
> >>             Matthias
> >>             --
> >>
> >>             Matthias Wienand
> >>             B.Sc. Softwaretechnik
> >>             Software Engineer
> >>
> >>             Telefon: +49 231 9860 202
> >>             Telefax: +49 231 9860 211
> >>             Mobil:   +49 152 26802283
> >>
> >>
> >>             [email protected] <mailto:
> [email protected]>
> >>             http://www.xing.com/profile/Matthias_Wienand2
> >>             http://www.itemis.de <http://www.itemis.de/>
> >>
> >>
> >>             itemis AG
> >>
> >>             Am Brambusch 15-24
> >>             44536 Lünen
> >>
> >>             Rechtlicher Hinweis:
> >>             Amtsgericht Dortmund, HRB 20621
> >>             Vorstand: Jens Wagener (Vors.), Wolfgang
> >>             Neuhaus, Abdelghani El-Kacimi
> >>             Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.),
> >>             Michael Neuhaus, Jennifer Fiorentino
> >>
> >>>             Am 08.05.2019 um 22:04 schrieb Wayne Beaton
> >>>             <[email protected]
> >>>             <mailto:[email protected]>>:
> >>>
> >>>             Greetings Simultaneous Release 2019-06 participants.
> >>>
> >>>             Per our process, I have started to assemble the
> >>>             participants list for 2019-06
> >>>             <https://projects.eclipse.org/releases/2019-06>.
> >>>
> >>>             By way of reminder, the process requires
> >>>             <
> https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early
> >
> >>>             that project teams signal their participation by making a
> >>>             change to their aggrcon file in the simrel repository.
> >>>             For project teams that intend to drop out of the
> >>>             simultaneous release, the process requires that you
> >>>             inform the group and then remove your aggrcon file.
> >>>
> >>>                 For projects that did participate in the previous
> >>>                 simultaneous release, the project team's
> >>>                 representative must touch the project's aggrcon file
> >>>                 by the milestone 2 (M2) date of the release to
> >>>                 indicate that the project wishes to continue
> >>>                 participating and that they project team is paying
> >>>                 attention.
> >>>
> >>>
> >>>             AFAICT, 49 project teams have changed their aggrcon file
> >>>             since the start of this release cycle. I have captured my
> >>>             best guess at the version that each project is
> >>>             participating with. Please have a look and let me know
> >>>             what I've gotten wrong.
> >>>
> >>>             Note that if you are adding a new version of your content
> >>>             (major, minor, or service), you need to create a release
> >>>             record. Make sure that your release record has
> >>>             "2019-06-19" as the release date (I did notice that least
> >>>             one existing release record showed 2019-06-20 as the
> >>>             release date; please have a look and fix your record if
> >>>             this is you).
> >>>
> >>>             Please create the release record (or ensure that it has
> >>>             been created) before you tell me that I've listed the
> >>>             wrong version.
> >>>
> >>>             Version names must include some form of a semantic
> >>>             version. You can prefix or suffix version names as you'd
> >>>             like. The convention appears to be to not prefix or
> >>>             suffix, or to include the simultaneous release name as a
> >>>             suffix.
> >>>
> >>>             Note that the PMI doesn't handle numbers appearing before
> >>>             the semantic version very well, but I have a fix in the
> >>>             queue that should sort this out in time for the release.
> >>>
> >>>             I intend to do a pass over the simrel repository again on
> >>>             Friday, May 10 (M2) to bring the participation list up to
> >>>             date and will start the public shaming of those who have
> >>>             not followed the rules sometime thereafter.
> >>>
> >>>             Per the December 2018 update to the EDP, project teams
> >>>             are not required to engage in a release review if they've
> >>>             engaged in one in the year leading up to their release
> >>>             date. No review is required. No PMC approval is required.
> >>>             No IP log review is required. /Remember that whether or
> >>>             not you engage in a review, project teams are required to
> >>>             follow the Eclipse IP Due Diligence Process. Your
> >>>             releases must only include IP that has been either
> >>>             "license certified" or "approved" by the IP Team. /I will
> >>>             initiate a scan of the repository tonight to ensure that
> >>>             unvetted IP has not been inadvertently added.
> >>>
> >>>             Thanks for your attention.
> >>>
> >>>             Wayne
> >>>
> >>>             --
> >>>             Wayne Beaton
> >>>             Director of Open Source Projects | Eclipse Foundation, Inc.
> >>>             _______________________________________________
> >>>             cross-project-issues-dev mailing list
> >>>             [email protected]
> >>>             <mailto:[email protected]>
> >>>             To change your delivery options, retrieve your password,
> >>>             or unsubscribe from this list, visit
> >>>
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >>
> >>             _______________________________________________
> >>             cross-project-issues-dev mailing list
> >>             [email protected]
> >>             <mailto:[email protected]>
> >>             To change your delivery options, retrieve your password,
> >>             or unsubscribe from this list, visit
> >>
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >>
> >>
> >>
> >>         --
> >>         Wayne Beaton
> >>         Director of Open Source Projects | Eclipse Foundation, Inc.
> >>         _______________________________________________
> >>         cross-project-issues-dev mailing list
> >>         [email protected]
> >>         <mailto:[email protected]>
> >>         To change your delivery options, retrieve your password, or
> >>         unsubscribe from this list, visit
> >>
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >>
> >>     _______________________________________________
> >>     cross-project-issues-dev mailing list
> >>     [email protected]
> >>     <mailto:[email protected]>
> >>     To change your delivery options, retrieve your password, or
> >>     unsubscribe from this list, visit
> >>     https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> >     _______________________________________________
> >     cross-project-issues-dev mailing list
> >     [email protected]
> >     <mailto:[email protected]>
> >     To change your delivery options, retrieve your password, or
> >     unsubscribe from this list, visit
> >     https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> >
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > [email protected]
> > To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> > https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
>
> --
> Frederic Gurr
> Release Engineer | Eclipse Foundation Europe GmbH
>
> Annastr. 46, D-64673 Zwingenberg
> Handelsregister: Darmstadt HRB 92821
> Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
> _______________________________________________
> cross-project-issues-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to