[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Apr 2011 11:44:36 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=eclipsesource.com; s=eclipsesource; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=X/U+nWv5EARMeoQIgHrx2nN59ekqENaRb3yurjoq72vZb1m3n32NaD95TChE0SLseQ 5o7OAHlq0O3YJyZ51uhCf3ODd5F37GV4TqnsIgINYEzZAmLDVB6NTWPHOwx3y4U/KNrf 4DG8InrMmu3JlUlGr2QoHfG/L9ZRLwcoZ3FGI=
Forwarding this message for Tom who seems to be having mail problems...
We are heading into M7 next week. Please note that the first warmup build is happening Thursday (Tomorrow!). See http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html
p2 currently has over 100 bugs marked for 3.7. My assumption is that a vast majority of these bugs are not going to be looked at for 3.7. Who from the p2 team can go through these bugs and assign them appropriately? If any bug is assigned to you then please evaluate if it is going into 3.7 or not and assign the milestone (or drop it) as appropriate. Keep in mind that after M7 the rules for releasing bug fixes becomes more tight. Please see http://eclipse.org/equinox/planning/freeze_plan_3.7.php.