Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] contributing to indigo sr1

Le 05/08/2011 14:57, Igor Fedorenko a écrit :
Are there any guidelines about what repositories projects should use for
their contributions to a release train, i.e. release, milestone, etc?

AFAIK, i don't remind any guidelines.

As far as I understand, participating projects are not expected to make
final repositories available before simultaneous release is declared.


This seems to imply that only transient (milestone?) repositories should
be used, unless there is a trick to add release repo to the aggregator
without making it publicly available.

what i do is to use milestone repo for aggregation, and after release, change the aggregator to point to release.

some others uses 3 repos for their contribution ( integration, milestones, release ) and b3 will pick up the latest version.


On 11-08-05 4:48 PM, Stéphane Bouchet wrote:

see inline comments :

Le 05/08/2011 13:48, Thomas Hallgren a écrit :
Hi Igor,

Here are some answers related to the b3 aggregator.

On 2011-08-05 13:24, Igor Fedorenko wrote:
I am trying to make m2e contribution to indigo sr1 build and have
of questions.

Following instructions in [1], I started with new eclipse 3.7 sdk
installation, installed b3 aggregator and checked out project. When I open indigo.b3aggr using the
Aggregator Model Editor I am told that model needs to be converted to a
new format. After conversion, there are some massive changes to the
model file and I also get lots of error markers about various
repositories not being available. Is this expected or something is
with my environment and/or setup?

I guess you installed the aggregator from our 3.7 site. The Indigo
release train was created, and should be maintained, by the 3.6 release
of the aggregator. In 3.7, we are adding new concepts to the model (the
ValidationSet) and use a new schema version for the XML. The aggregator
detects this and converts your model automatically. The aggrcon files
remain the same though. The schema change only relates to the main
b3aggr file.

That said, there should not be any problems whatsoever verifying your
Indigo contribution with a 3.7 version of the aggregator. I have also
noticed that several of the contributions are invalid with respect to
the repository that they appoint. I guess several projects have removed
their contributing repositories after the release. If that's the case,
then it's probably high time to restore them now in time for the SR1

You can safely disable all missing repos, and only focus on your
contribution. With SR1, webmasters will disable all repos that are
unavailable. But this is project leads or releng to bu sure to provide
correct contents for indigo.

Thomas Hallgren
cross-project-issues-dev mailing list

cross-project-issues-dev mailing list
cross-project-issues-dev mailing list

fn;quoted-printable:St=C3=A9phane Bouchet
adr;quoted-printable:BP 20773;;7 Boulevard Amp=C3=A8re;CARQUEFOU;;44481;France

Back to the top