Alexander,
Indeed you need to ask for commit rights. E.g., I did that via
the following Bugzilla request:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=529851
So please open a Bugzilla like that one against
Community/Cross-Project.
In the interest of timeliness, I've approved the review on your
behalf (with my god-like powers).
Cheers,
Ed
On 19.04.2019 07:16, Alexander Fedorov
wrote:
Hello Ed,
This sounds promising, but I do not have +2 option to submit it.
I assume it requires a "committer" rights for
simrel/org.eclipse.simrel.build and I'm not sure that everyone has
it by default.
Regards,
AF
18.04.2019 23:47, Ed Merks пишет:
Alexander,
This is generally "self serve". You commit to Gerrit and if
the build verifies the changes don't cause aggregation
problems you give your own +2/+1 and then submit it.
Cheers,
Ed
On 18.04.2019 21:41, Alexander
Fedorov wrote:
Hello,
I do not have any feedback for https://git.eclipse.org/r/#/c/140202/
since April 8.
What should be done from my side to initiate some progress on
this?
Thanks,
AF
08.04.2019 21:15, Alexander
Fedorov пишет:
Yes, the Eclipse Passage is the new participant, and this
thread is an announcement of intent as stated below.
I created Gerrit https://git.eclipse.org/r/#/c/140202/
to add Eclipse Passage.
Thanks,
AF
08.04.2019 20:56, Wayne Beaton
пишет:
I've created a "simrel" record for 2019-06
and have added Eclipse Passage (I also added Eclipse
Project while I was there).
The opt-in deadline is M1 on April 19/2019. On (or
shortly after) that date, I'll populate the page with
the rest of the information for participating
projects.
If you are a new participant in the
simultaneous release, you are required to announce
your intent on this mailing list.
If you are a returning participant, the
"royal we" will determine your participation status
based on your aggrcon file. Specifically, if it exists
and is enabled on the M1 date, I'll assume that you're
in.
The process requires that all projects that are
"in" change their aggrcon file to indicate that
they're paying attention. Please do this if you can. I
will get my team to chase down the project teams who
have not updated their aggrcon between the start of
this cycle and the M1 date to verify their status.
Thanks,
Wayne
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
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
cross-project-issues-dev@xxxxxxxxxxx
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
cross-project-issues-dev@xxxxxxxxxxx
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
cross-project-issues-dev@xxxxxxxxxxx
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
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
|