Furthermore..... 1. Why was the rule changed anyway? I anticipated Riena to be in Juno until I found out through this mail that I am not.
2. Why do projects get aggregated in the composite repo like Riena did in M3 if I am not signed up? A little confusing to me, but apparently I missed the point where somebody said, we changed the rule, make sure you sign up... Anyway I signed up Riena and we already provided content for M3...... christian Am 06.12.2011 um 00:44 schrieb Matthias Sohn: 2011/12/6 David M Williams <[email protected]<mailto:[email protected]>> First, remember M4 is "next week" and is short .... code-done window from Friday 12/9 to Wednesday 12/14 ... to be made available on 12/16. Please remember to respond quickly to "build breaks", even if before your official +n due date. Second, projects leads, remember to "sign up" for the Juno release by M4, on the Eclipse Foundation's Portal. For a list of who is signed up, see http://eclipse.org/juno/planning/SimultaneousReleaseOverview.php I was surprised that jgit and egit weren't contained in the Juno list, I remember for the Indigo release train projects which had participated in Helios were automatically signed up for Indigo. Apparently I missed that this policy changed. I signed up jgit and egit for Juno to fix this. I'll add them to the build soon. -- Matthias <ATT00001..c> ------------------------------------------------------------- compeople AG Untermainanlage 8 60329 Frankfurt/Main fon: +49 (0) 69 / 27 22 18 0 fax: +49 (0) 69 / 27 22 18 22 web: www.compeople.de<http://www.compeople.de/> Vorstand: J?rgen Wiesmaier Aufsichtsratsvorsitzender: Christian Glanz Sitz der Gesellschaft: Frankfurt/Main Handelsregister Frankfurt HRB 56759 USt-IdNr. DE207665352 -------------------------------------------------------------
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
