[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] A respin of galileo update site will occur (soon)

Normally, I'd say "no" and would prefer you not, since every possible 
change is another opportunity for failure, as the TPTP is now learning. 

I will "respin" another staging directory soon, given there's been 5 
changes (two to categories) I think collectively they justify it. 

Next year remind me ... we need something like "PMC Review" for Galileo 
site and EPP ... apparently not all individual PMC's have a rampdown 
process enforced. 

Thanks, 






From:
"Paula Gustavo-WGP010" <wgp010@xxxxxxxxxxxx>
To:
"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
Date:
06/18/2009 11:14 AM
Subject:
RES: RES: [cross-project-issues-dev] Question about Build ID's
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx



Our current build file points to RC4. We did only a minor change on it. 
Our features that had a reference to an old update side so we generated a 
new build and saved in another location (this was the one that we thought 
about publishing next week).
 
Do you think there is still time to include this today? Everything is 
build, I just need to copy the content to the update site and update the 
.build files.  IF there is no time it is not big issue to just keep RC4
 
J
gep
 

De: cross-project-issues-dev-bounces@xxxxxxxxxxx [
mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Em nome de David M 
Williams
Enviada em: quinta-feira, 18 de junho de 2009 12:01
Para: Cross project issues
Assunto: Re: RES: [cross-project-issues-dev] Question about Build ID's
 
The last day was yesterday ... or, today, it appears from all the requests 
being made! 

Sorry it is not clear, but the idea is ... at least my understanding ... 
is that your build file right now, for final build, just points to your 
final content, even if that content is in a "temporary" site, such as 
"milestones". Hence, what we create is final content, and is just stored 
in /staging temporarily. 

So, after that, say Monday, as you "move" things to your final site, say 
/updates you should change your .build file to point to that final, 
permanent /updates directory but there would be no change in content (no 
change in features or feature versions), so no need to rebuild Galileo. 

Let me know if I am misunderstanding, or if there are additional 
questions. 

I'll try to improve 'final daze' document to capture some of this. 



"Paula Gustavo-WGP010" ---06/18/2009 10:12:18 AM---Hi david, Just to 
clarify.


From:

"Paula Gustavo-WGP010" <wgp010@xxxxxxxxxxxx>

To:

"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>

Date:

06/18/2009 10:12 AM

Subject:

RES: [cross-project-issues-dev] Question about Build ID's

Sent by:

cross-project-issues-dev-bounces@xxxxxxxxxxx




Hi david,

Just to clarify. 
When is the last moment to update my .biuld contribution file. Is it
today or on Monday 22th? It is not clear to me based on the final_daze
wiki.

Currently we have everything set on mtj, but I understood that I had to
wait until Monday 22th to place my update jars on out release URL and
after that update my build contributions.

:)
gep

-----Mensagem original-----
De: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Em nome de David M
Williams
Enviada em: quinta-feira, 18 de junho de 2009 10:39
Para: Cross project issues
Assunto: Re: [cross-project-issues-dev] Question about Build ID's

> ... in my understanding, 
> /releases/galileo and .../staging are the same at the moment,
> so what about doing a clean build of .../staging when PDT and
> Teneo are done with their things?

No. /releases/galileo won't be updated until 'final daze'. 
http://wiki.eclipse.org/Galileo/Final_Daze
(not that it is all that explicit in that document, I just take every 
opportunity to reference it in the hopes that increases it chances of 
being read ... but I've mentioned it in other cross-project posts ... 
obviously buried ... only /releases/staging has all the latest stuff). 

I'm still waiting for someone to support the idea of re-spining teneo
and 
pdt for their perceived "stop ship" problems. 
Hmm, I notice dsdm-tm has updated their .build file too! :) 






From:
"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
To:
"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
Date:
06/18/2009 06:32 AM
Subject:
[cross-project-issues-dev] Question about Build ID's
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx



Hi all,

I'm not sure how many other projects do this, but the TM project
embeds its build ID's into the feature description text shown in
the about dialog (via about.mappings).

Now it can happen that a build's contents does not change at all,
but the build ID changes; in the TM case, our 3.1 release is the
same as our RC4, but the build ID is "3.1" rather than "3.1RC4".

I'm wondering how the Galileo Builder treats this. Given that our
plugin and feature ID's have not changed, would the Galileo builder
take our "old" plugins with the "3.1RC4" build ID embedded from
some cache? For some plugins / features, the build ID might even
be MUCH older. 

Or does it fetch fresh data from our update site on every run,
thus ensuring that the latest build ID, "3.1" is embedded?

The stuff on /releases/galileo which I just checked contains a 
mixture of "RC3" and "RC4" build ID's. I'm wondering whether there
is a chance to rectify this... in my understanding, 
/releases/galileo and .../staging are the same at the moment,
so what about doing a clean build of .../staging when PDT and
Teneo are done with their things?


Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
_______________________________________________
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
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev