AFAIK, there will be no OCL 1.3 M7 build. Since the previous committer
team resigned (having prepared and published the M6 build), there hasn't
been any development that I know of. I don't think the new committer
team is installed, yet, though I know that Adolfo has some work that he
is waiting to commit to address the Galileo common requirement for
Capabilities. I understand from the Modeling PMC that the new team will
be activated, soon.

In the mean-time, M6 effectively is the M7 build.

HTH,

Christian

On Sun, 2009-05-10 at 17:55 +0200, Philipp Kutter wrote:

> Hi.
> Does anyone know when MDT OCL 1.3M7 will be available?
>
> Is it advisable to use the M6 release with all the surrounding M7
> releases, or should we wait?
>
> Regards,
> Philipp

--=-+Xw/TVHcLiVmCjP3z2f3
Content-Type: text/html; charset="utf-8"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Philipp,<BR>
<BR>
AFAIK, there will be no OCL 1.3 M7 build.&nbsp; Since the previous committer team resigned (having prepared and published the M6 build), there hasn't been any development that I know of.&nbsp; I don't think the new committer team is installed, yet, though I know that Adolfo has some work that he is waiting to commit to address the Galileo common requirement for Capabilities.&nbsp; I understand from the Modeling PMC that the new team will be activated, soon.<BR>
<BR>
In the mean-time, M6 effectively is the M7 build.<BR>
<BR>
HTH,<BR>
<BR>
Christian<BR>
<BR>
<BR>
On Sun, 2009-05-10 at 17:55 +0200, Philipp Kutter wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Hi.
Does anyone know when MDT OCL 1.3M7 will be available?

Is it advisable to use the M6 release with all the surrounding M7
releases, or should we wait?

Would a M7 release not mean a release compiled against the M7 releases
of all used packages, and thus be completely independent of the question
whether there was something newly developed or not?

If, what I write above is correct:
As I have now an Eclipse comitter in my company (Quentin Glineur, he
started to work 1.Mai), could he checkout the sources, and compile the
M7 release for you?

Please let us know, if we can help with this.

Regards, Philipp

Christian W. Damus wrote:
> Hi, Philipp,
>
> AFAIK, there will be no OCL 1.3 M7 build. Since the previous committer
> team resigned (having prepared and published the M6 build), there hasn't
> been any development that I know of. I don't think the new committer
> team is installed, yet, though I know that Adolfo has some work that he
> is waiting to commit to address the Galileo common requirement for
> Capabilities. I understand from the Modeling PMC that the new team will
> be activated, soon.
>
> In the mean-time, M6 effectively is the M7 build.
>
> HTH,
>
> Christian
>
>
> On Sun, 2009-05-10 at 17:55 +0200, Philipp Kutter wrote:
>> Hi.
>> Does anyone know when MDT OCL 1.3M7 will be available?
>>
>> Is it advisable to use the M6 release with all the surrounding M7
>> releases, or should we wait?
>>
>> Regards,
>> Philipp]]>Philipp W. Kutter2009-05-12T13:03:08-00:00Re: Availability of MDT OCL 1.3M7https://www.eclipse.org/forums/index.php/mv/msg/22026/70743/#msg_70743
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi, Philipp,

Not having login access to Eclipse.org, there would be nothing that I
can do to help. I agree that it is best to at least compile and run
JUnits on the latest milestone (M7 in this case) of dependencies, but
since M6 was the API freeze, and the dependencies in question have very
good track records of stability, I wouldn't be concerned.

In any case, I'm confident that the PMC will have the new committer team
in place in time to produce the RC builds in the ramp-down to the
Galileo release. This component is too important to fall through the
cracks. :-)

Cheers,

Christian

On Tue, 2009-05-12 at 15:03 +0200, Philipp Kutter wrote:

> Hi, Christian.
> (I repeat my question on the corresponding EMF components here for
> correctness)
>
> Would a M7 release not mean a release compiled against the M7 releases
> of all used packages, and thus be completely independent of the question
> whether there was something newly developed or not?
>
> If, what I write above is correct:
> As I have now an Eclipse comitter in my company (Quentin Glineur, he
> started to work 1.Mai), could he checkout the sources, and compile the
> M7 release for you?
>
> Please let us know, if we can help with this.
>
> Regards, Philipp
>
> Christian W. Damus wrote:
> > Hi, Philipp,
> >
> > AFAIK, there will be no OCL 1.3 M7 build. Since the previous committer
> > team resigned (having prepared and published the M6 build), there hasn't
> > been any development that I know of. I don't think the new committer
> > team is installed, yet, though I know that Adolfo has some work that he
> > is waiting to commit to address the Galileo common requirement for
> > Capabilities. I understand from the Modeling PMC that the new team will
> > be activated, soon.
> >
> > In the mean-time, M6 effectively is the M7 build.
> >
> > HTH,
> >
> > Christian
> >
> >
> > On Sun, 2009-05-10 at 17:55 +0200, Philipp Kutter wrote:
> >> Hi.
> >> Does anyone know when MDT OCL 1.3M7 will be available?
> >>
> >> Is it advisable to use the M6 release with all the surrounding M7
> >> releases, or should we wait?
> >>
> >> Regards,
> >> Philipp

--=-5qkSKmTZvE3KgO6YoCFx
Content-Type: text/html; charset="utf-8"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Philipp,<BR>
<BR>
Not having login access to Eclipse.org, there would be nothing that I can do to help.&nbsp; I agree that it is best to at least compile and run JUnits on the latest milestone (M7 in this case) of dependencies, but since M6 was the API freeze, and the dependencies in question have very good track records of stability, I wouldn't be concerned.<BR>
<BR>
In any case, I'm confident that the PMC will have the new committer team in place in time to produce the RC builds in the ramp-down to the Galileo release.&nbsp; This component is too important to fall through the cracks.&nbsp; :-)<BR>
<BR>
Cheers,<BR>
<BR>
Christian<BR>
<BR>
On Tue, 2009-05-12 at 15:03 +0200, Philipp Kutter wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Hi, Christian.
(I repeat my question on the corresponding EMF components here for
correctness)

Would a M7 release not mean a release compiled against the M7 releases
of all used packages, and thus be completely independent of the question
whether there was something newly developed or not?

If, what I write above is correct:
As I have now an Eclipse comitter in my company (Quentin Glineur, he
started to work 1.Mai), could he checkout the sources, and compile the
M7 release for you?

Please let us know, if we can help with this.

Regards, Philipp

Christian W. Damus wrote:
&gt; Hi, Philipp,
&gt;
&gt; AFAIK, there will be no OCL 1.3 M7 build. Since the previous committer
&gt; team resigned (having prepared and published the M6 build), there hasn't
&gt; been any development that I know of. I don't think the new committer
&gt; team is installed, yet, though I know that Adolfo has some work that he
&gt; is waiting to commit to address the Galileo common requirement for
&gt; Capabilities. I understand from the Modeling PMC that the new team will
&gt; be activated, soon.
&gt;
&gt; In the mean-time, M6 effectively is the M7 build.
&gt;
&gt; HTH,
&gt;
&gt; Christian
&gt;
&gt;
&gt; On Sun, 2009-05-10 at 17:55 +0200, Philipp Kutter wrote:
&gt;&gt; Hi.
&gt;&gt; Does anyone know when MDT OCL 1.3M7 will be available?
&gt;&gt;
&gt;&gt; Is it advisable to use the M6 release with all the surrounding M7
&gt;&gt; releases, or should we wait?
&gt;&gt;
&gt;&gt; Regards,
&gt;&gt; Philipp
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>

--=-5qkSKmTZvE3KgO6YoCFx--]]>Christian W. Damus2009-05-13T13:09:29-00:00Re: Availability of MDT OCL 1.3M7https://www.eclipse.org/forums/index.php/mv/msg/22026/70843/#msg_70843
> Not having login access to Eclipse.org, there would be nothing that I
> can do to help. I agree that it is best to at least compile and run
> JUnits on the latest milestone (M7 in this case) of dependencies, but
> since M6 was the API freeze, and the dependencies in question have very
> good track records of stability, I wouldn't be concerned.
In the meantime I tried with M6, and everything seems to work fine!

> In any case, I'm confident that the PMC will have the new committer team
> in place in time to produce the RC builds in the ramp-down to the
> Galileo release. This component is too important to fall through the
> cracks. :-)
I hope so, as we are in the process of moving from an IT company to a
business modeling company, and if we need to maintain it on our own,
this would break our plans.

Indeed, it appears that someone has been too eager in reclaiming server
space since I published the 1.3 M6 build. Probably, you can still find
it in the MDT milestones p2 repos (update site). However, it probably
is worth a bug report to Modeling Releng component to restore the
downloads (as I think that ZIPs are still a supported distribution
vehicle).

Your builds can still access the M6 zip because the build system caches
it locally (as it does all of the dependencies that it downloads). So,
check the /home/www-data/build/downloads/ directory or wherever it is
that the build system caches its dependencies (I have forgotten the
location). You'll find the OCL zip in there.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Laurent,<BR>
<BR>
Indeed, it appears that someone has been too eager in reclaiming server space since I published the 1.3 M6 build.&nbsp; Probably, you can still find it in the MDT milestones p2 repos (update site).&nbsp; However, it probably is worth a bug report to Modeling Releng component to restore the downloads (as I think that ZIPs are still a supported distribution vehicle).<BR>
<BR>
Your builds can still access the M6 zip because the build system caches it locally (as it does all of the dependencies that it downloads).&nbsp; So, check the /home/www-data/build/downloads/ directory or wherever it is that the build system caches its dependencies (I have forgotten the location).&nbsp; You'll find the OCL zip in there.<BR>
<BR>
Cheers,<BR>
<BR>
Christian<BR>
<BR>
<BR>
On Tue, 2009-05-19 at 16:18 +0200, laurent Goubet wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Hi Folks,

I might be a little behind things but ... M7 hasn't been built, RC1
probably won't be either ... and I can't for the life of me find _any_
build of the 1.3 stream on the download area.

Thanks for the bug report, I didn't take enough time myself to raise it
as I was in quite a rush and wanted to confirm things beforehand :). I
won't have any way to access the builds until monday though ... I'll try
and catch up with what's been done for RC1 when I return.