| Re: [cross-project-issues-dev] Status and outlook near end of M4 +3 |
I believe it's because you really don't want to "track with parent". That option means that the project isn't participating independently, but rather is participating as part of its parent project. Web Tools, for example, does this. I get one IP log, and one release review document for Web Tools and all of it's participating subprojects; also only Web Tools gets counted in the official project count we publish.
Whether or not it makes sense to "track with parent" is generally left to your discretion. But, since SOA doesn't participate directly in the simultaneous release, it really doesn't make sense for BPEL.
Make sense?
Wayne
On 12/15/2011 09:01 AM, Bob Brodt wrote:But...I had already done that (open the release tracker, set the offset and a bunch of other fields, and clicked the "track with parent" link) yesterday._______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Any idea why soa.bpel wasn't showing up?
Okay, I sorted it out.
Flipping the bit--it turns out--isn't enough.
After flipping the bit, projects will have to open the "Simultaneous Release Tracker" component and set any of the values. I recommend setting the offset.
If your project is releasing as part of the parent project, click the "track with parent" link.
We're working on making this better.
Wayne
On 12/14/2011 10:07 PM, Wayne Beaton wrote:It looks like it should work. I am investigating.
Wayne
On 12/14/2011 07:18 PM, Bob Brodt wrote:Argh, one more try:
Yes, I have read this wiki...but I'm still confused. Here's the portal page showing the "flipping of the simultaneousrelease bit" for soa.bpel:
Yes, I have read this wiki...but I'm still confused. Here's the portal page showing the "flipping of the simultaneousrelease bit" for soa.bpel:
Are there any other bits that need flipping or am I looking at the wrong bit or what?
the release train requirements are listed herehttp://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements
2011/12/15 Bob Brodt <bbrodt@xxxxxxxxxx>
ok....I thought I had already "flipped the bit". Not sure what else I need to do other than setting the "simultaneousrelease" metadata to "1" for juno (soa.bpel project) and filling in the simultaneous release tracker. What am I missing?
AFAICT, BPEL has not yet flipped the bit for Juno. Can you please do that?
The calendar and other resources are accessible from the wiki http://wiki.eclipse.org/Juno
Thanks,
Wayne
On 12/14/2011 06:13 PM, Bob Brodt wrote:Yes, I'm not here <raises hand> I don't think BPEL will be in the aggregation build by tonight. When is M5? ________________________ Robert ("Bob") Brodt Senior Software Engineer JBoss by Red Hat ----- Original Message -----Roll call ... I think the last aggregation build got all the latest changes/additions for M4, but please speak up now if your contribution isn't there yet. I promoted the latest results to /releases/staging so you can check/test there, if all is as expected. If anyone needs to contribute by 7 PM Eastern, I'd think that'd be containable ... after that, I'd begin to ask if better to wait to M5, or other more specific questions. Oh, and you don't really need to answer "roll call" unless there's problems ... like my teachers used to say "if anyone is not here, will you please speak up?" :) _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Matthias
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
