I need a little more information.

https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#State_intent_early_.28M4.29

FWIW, I made it is a requirement to formally announce your intent to participate because we have had too many cases in the past where we've automatically just rolled over from one year to the next and the project teams forgot to engage, resulting in last minute scrambles.

I wish that I had the bandwidth to just automatically include those projects who are obviously paying attention (e.g. CDT), but I don't.

I can probably figure out the release based on the project metadata, but it's way easier for me if you tell me which release you're including. I also need to know the offset. Again, I can figure this out, but it takes at least some (albeit trivial) effort that adds up. Besides, the offset information is something that other participants care about, so it's nice to let people know in the public forum.

An explicit declaration of participation each year helps me and everybody else know that the project is still engaged.

HTH,

Wayne

On 04/12/14 12:34 PM, Jeff Johnston wrote:
I didn't know we still had to declare intent.  I thought it was implied by our 
enablement in b3aggrcon file.

Anyway, Linux Tools will be participating in Mars.

-- Jeff J.

----- Original Message -----
From: "David M Williams" <[email protected]>
To: [email protected]
Sent: Wednesday, December 3, 2014 9:05:58 PM
Subject: [cross-project-issues-dev] Are *you* ready for M4?

I wanted to remind everyone that M4 is not that far off.

In part, because this is the milestone we switch to a "one week window". M4 +0 is 12/12 and +3 is 
12/17. For that reason, it is good to make an early "warm-up" contributions that is near final, 
even if your final contribution is later made on your "latest possible" +n day.

Plus, three projects still have disabled features or repositories:
mft.b3aggrcon - org.eclipse.simrel.build (2 matches)
mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build
soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build

PLUS ... have you declared your intent? Or, lack of intent? (I know one or two have) but, 
according to the "who is participating" web page, at

https://projects.eclipse.org/releases/mars

there are 21 projects that have "dropped out" of Mars! (That list is about half way down the left-most 
column.) I am pretty sure some of them do not intend to drop out (such as CDT! WTP! Xpand!? Mylyn! ... ) and I am 
moderately sure some of those have declared intent on this list, so I am wondering if there is a problem with your 
"release record" ... or something? In any case, please work with Wayne if something is amiss or missed. And, 
it is helpful and polite that if you have been a long term participant, and now decided to no longer participate, to 
say so explicitly ... to us on this list, not to mention your adopters via your dev-lists, etc. I mention this now, 
since at some point, those who show up on the "will not participate list" will have their files removed from 
the aggregator and the repository, for the simple reason of giving a realistic view of "what is coming" to 
users, adopters, and other projects.

Greatest thanks to all,


_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.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://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon 2015 <http://www.eclipsecon.org/na2015>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to