Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Xtext M4 ?

Yes, I think that would make sense for the given infrastructure. To be clear, what I was suggesting was not to necessarily actually *use* the meta-data for nightly and interim sites but simply to *track* them in addition to the milestone sites so that consumers could know with certainty what evolving target they're supposed to be building against. I've been in a situation where I thought I was building to the current repos for a dependency (my project has a very large number of such), but I'd actually been building against a non-maintained 'interim' site that only included stuff from the Helios release. I didn't figure that out until RC1 when my older dependency no longer worked.

A significant advantage of that is that we could eventually build part of the project meta-data for the web sites from the aggregator so that any consumers would be pointed to the blessed version of each build site. It seems that almost every project has multiple old update sites out there and it is often an exercise in googling and trial and error to find the correct up to date site.

-Miles (aka 'the universal consumer')

On Dec 14, 2011, at 11:44 AM, Dennis Hübner wrote:

I think it's also a good idea to point b3 aggregator to projects nightly update site after a milestone is released.
So dependent projects can earlier react to probably breaking changes.


2011/12/14 Miles Parker <milesparker@xxxxxxxxx>

I had thought last year that this was what aggregator was for, that is
that we could use the update sites indicated in the aggregator, but I
discovered that I was wrong. Perhaps we should legislate having that be in
sync, or add a separate set for Interim and Nightlies?It sure would be nice
to find out what version of dependencies we should be using without having
to consult typically out of date project web sites.

On Dec 14, 2011, at 10:53 AM, John Arthorne wrote:

The general form of this question would be good input for Wayne and his
project page organization. Currently projects declare with a flag that they
are participating in the simultaneous release, but there is no record that
I am aware of indicating which release they will contribute. For projects
whose own schedule matches the cadence of the release train this is fairly
obvious. But for other projects with more frequent releases I don't think
this information is available. To pick a random example, this morning I was
asking what release of Jetty would be in Juno and the answer wasn't so
clear. Maybe the juno "participation" flag should be metadata on a release
rather than just a generic flag on the project? For downstream projects and
consumers I expect this information would be really helpful.


 *Adolfo Sanchez Barbudo <adolfosbh@xxxxxxxxxxxxxxxx>*
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

12/14/2011 10:20 AM
 Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

[cross-project-issues-dev] Xtext M4 ?

Hello Folks

I'm wondering if Xtext guys are going to create any kind of milestone for

Looking at their milestones repository[1] I only see an old 2.1.0M2.

I don't find any clue in the project plan [2] neither .

Any reason about why there is no an updated milestones repository would be
appreciated. Take into account that our milestones builds are based on
milestones repositories for those projects we depend on, so keeping the
usual (probably planned) milestones releases are important for us.

[1] **<>
[2] *

P.S: I've not checked other itemis projects (xpand, mwe), but I guess we
will have the same problem with them.

Best Regards,
cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

cross-project-issues-dev mailing list


cross-project-issues-dev mailing list

Dennis Hübner


Mobil:   0151 173 96 707

itemis AG
Am Germaniahafen 1
24143 Kiel

Rechtlicher Hinweis:
Amtsgericht Dortmund, HRB 20621
Vorstand: Wolfgang Neuhaus, Jens Wagener, Dr. Georg Pietrek
Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus 
cross-project-issues-dev mailing list

Back to the top