Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RES: [cross-project-issues-dev] Question about Build ID's

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

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.


-----Mensagem original-----
De: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Em nome de David M
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'.
(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
pdt for their perceived "stop ship" problems. 
Hmm, I notice dsdm-tm has updated their .build file too! :) 

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

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?

Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top