If we're to follow the process to the letter, you should ask your
PMC (Tools) to petition the Eclipse Planning Council to decide on
the respin.
Since time is short and we need to get this started sooner rather
than later, I've short circuited the process a bit and have made
the petition to the PC on behalf of the Tools PMC.
Wayne
On 10/03/17 04:11 AM, Kaloyan Raev
wrote:
OK. Thanks, Markus!
I'll try writing to the cross-project-issues-dev list.
Kaloyan
On 03/10/2017 11:05 AM, Markus Knauer
wrote:
Hi Kaloyan,
that sounds worse... in that case you need to (officially)
request a respin, or to be more precise, the Planning
Council representative of your top-level project needs to
move that forward. It wouldn't be the first time that we
have a respin, but with every respin it is a decision
between fixing something and the risk of introducing
another problem.
After such a respin we can certainly rebuild the
packages.
Regards,
Markus
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation |