Re: [cross-project-issues-dev] Projects participating in 2019-06

[Tsvetkov, Krum]

Hi Wayne,

The version of Memory Analyzer should be 1.9.1 (this is what we contributed to 
M3, and the release record is also created).

Regards,
Krum

From:  on behalf of Wayne Beaton 

Reply-To: Cross issues 
Date: Monday, 3. June 2019 at 20:35
To: Cross issues 
Subject: [cross-project-issues-dev] Projects participating in 2019-06

I've updated the project 
participation list to reflect 
what I believe that I see in the aggregate repository. Please let me know if 
I've gotten something wrong.

ACTF is not in the repository and I don't know why. Their aggrcon file looks 
fine. Have I missed something important?

Note that RC1 is on June 7/2019. If you're pushing new versions/features, 
please update your contribution before this date.

A handful of projects did not signal their intent to participate using the 
described method (nor did they respond to my attempts to use this channel to 
connect). I intend to recommend to the Planning Council that they prune out 
those projects that are clearly not contributing to the process.

Wayne
--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Memory Analyzer Participation in SimRel 2018-09

[Tsvetkov, Krum]

Hi,

Memory Analyzer will participate in the 2018-09 SimRel with a bugfix release 
1.8.1 at offset +3:
https://projects.eclipse.org/projects/tools.mat/releases/1.8.1

Regards,
Krum
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Memory Analyzer Declaring Eclipse Photon participation

[Tsvetkov, Krum]

Hello,

Memory Analyzer is also planning to participate in the Photon simultaneous 
release with version 1.8.0 
(https://projects.eclipse.org/projects/tools.mat/releases/1.8.0) and offset +3 
(unchanged).
Apologies for the very late note.

Regards,
Krum

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Validating Aggregator fails because of legacy update site -> MAT

[Tsvetkov, Krum]

HI all,

Apologies if my update of MAT yesterday caused trouble for the rest. As we 
contribute relatively seldom, I just kept doing what used to work in the past.
Do I understand it correctly what “legacy update sites” means – for me this is 
the old-style structure with a site.xml and no p2 metadata – is this so?
The structure of the site I contributed yesterday 
(http://download.eclipse.org/mat/oxygen/RC1/update-site/) looks like this:

 binary/
 features/
 plugins/
 artifacts.jar
 artifacts.xml.xz
 content.jar
 content.xml.xz
 p2.index

We build it with tycho using packaging eclipse-repository. I compared with some 
of the other contributions, and it seems to be the same structure. Am I missing 
something?

Regards,
Krum


On 23.05.17, 21:47, "cross-project-issues-dev-boun...@eclipse.org on behalf of 
David Williams"  wrote:

On 05/23/2017 01:47 PM, Alexander Nyßen wrote:
> Hi all,
>
> when validating the Oxygen aggregator on my machine, the validation 
> fails because of an unsupported legacy update site. It seems this was 
> introduced by updating MAT. If I disable MAT and Andmore (which 
> depends on it), the validation succeeds on my local machine.
>
I will also add, in case not obvious, that "legacy update sites" are 
explicitly dis-allowed in the Sim. Rel. aggregation. The aggregator 
itself should still allow it, if someone was building their own site and 
set the property "Allow Legacy Sites" to "true".

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Memory Analyzer participation in Oxygen

[Tsvetkov, Krum]

Hi,

Sorry for the very late note. Memory Analyzer also intends to participate in 
the Oxygen release with its 1.7.0 release:
https://projects.eclipse.org/projects/tools.mat/releases/1.7.0

We'd like to keep the +3 offset as in the years before.

Regards,
Krum

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Memory Analzyer participation in Neon

[Tsvetkov, Krum]

The Memory Analyzer project (tools.mat) will participate in the Neon release 
train with a 1.6.0 release:
https://projects.eclipse.org/projects/tools.mat/releases/1.6.0

As in previous years the project will have offset +3.

Regards,
Krum

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Memory Analyzer participation in the Luna release

[Tsvetkov, Krum]

Hi,

Memory Analyzer will participate in the Luna simultaneous release:
https://projects.eclipse.org/projects/tools.mat/releases/1.4.0

In previous releases MAT was +3 and will stay so for Luna.

MAT has dependency to the chart engine of BIRT.

Krum
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Status and outlook for Luna M1

[Tsvetkov, Krum]

Memory Analyzer is now also enabled.
We disabled our charts feature, as it depends on BIRT, which is not yet enabled.

I had troubles pushing (couldn't get through our corporate proxy).
Thanks to Matthias who made the changes instead of me.


From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David M 
Williams
Sent: Mittwoch, 21. August 2013 06:01
To: cross-project-issues-dev@eclipse.org
Subject: [cross-project-issues-dev] Status and outlook for Luna M1

Doesn't look good. I'll admit there is one day left, but so far 50 projects 
have not even enabled their contribution to Luna (pasted below).

Thank you to the 20 of you who have.

Remember, enable your contribution if you plan to participate (remove the 
enabled=false), but disable your repository if you are simply waiting for 
pre-reqs to get enabled or fixed (disable by adding enabled=false to your 
repository element(s)).

Please ask if questions. (Or, please say if you have explicitly decided not to 
participate in Luna).

Thanks,

= = = = =

This list are those that have not yet enabled contribution:

actf.b3aggrcon - org.eclipse.simrel.build
amalgam.b3aggrcon - org.eclipse.simrel.build
amp.b3aggrcon - org.eclipse.simrel.build
birt.b3aggrcon - org.eclipse.simrel.build
cdt.b3aggrcon - org.eclipse.simrel.build
dltk.b3aggrcon - org.eclipse.simrel.build
dtp.b3aggrcon - org.eclipse.simrel.build
ecf.b3aggrcon - org.eclipse.simrel.build
egit.b3aggrcon - org.eclipse.simrel.build
emf-cdo.b3aggrcon - org.eclipse.simrel.build
emf-compare.b3aggrcon - org.eclipse.simrel.build
emf-diffmerge.b3aggrcon - org.eclipse.simrel.build
emf-query.b3aggrcon - org.eclipse.simrel.build
emf-transaction.b3aggrcon - org.eclipse.simrel.build
emf-validation.b3aggrcon - org.eclipse.simrel.build
emft-ecoretools.b3aggrcon - org.eclipse.simrel.build
emft-eef.b3aggrcon - org.eclipse.simrel.build
emft-egf.b3aggrcon - org.eclipse.simrel.build
emft-emffacet.b3aggrcon - org.eclipse.simrel.build
epp-mpc.b3aggrcon - org.eclipse.simrel.build
gmp-gmf-notation.b3aggrcon - org.eclipse.simrel.build
gmp-gmf-runtime.b3aggrcon - org.eclipse.simrel.build
gmp-gmf-tooling.b3aggrcon - org.eclipse.simrel.build
gmp-graphiti.b3aggrcon - org.eclipse.simrel.build
jubula.b3aggrcon - org.eclipse.simrel.build
jwt.b3aggrcon - org.eclipse.simrel.build
koneki.b3aggrcon - org.eclipse.simrel.build
linuxtools.b3aggrcon - org.eclipse.simrel.build
m2e-wtp.b3aggrcon - org.eclipse.simrel.build
m2e.b3aggrcon - org.eclipse.simrel.build
m2m-atl.b3aggrcon - org.eclipse.simrel.build
m2t-acceleo.b3aggrcon - org.eclipse.simrel.build
mat.b3aggrcon - org.eclipse.simrel.build
mdt-modisco.b3aggrcon - org.eclipse.simrel.build
mdt-papyrus.b3aggrcon - org.eclipse.simrel.build
mft.b3aggrcon - org.eclipse.simrel.build
mmt-qvto.b3aggrcon - org.eclipse.simrel.build
mylyn-docs-intent.b3aggrcon - org.eclipse.simrel.build
mylyn.b3aggrcon - org.eclipse.simrel.build
objectteams.b3aggrcon - org.eclipse.simrel.build
pdt.b3aggrcon - org.eclipse.simrel.build
ptp.b3aggrcon - org.eclipse.simrel.build
sapphire.b3aggrcon - org.eclipse.simrel.build
scout-rap.b3aggrcon - org.eclipse.simrel.build
scout.b3aggrcon - org.eclipse.simrel.build
soa-bpel.b3aggrcon - org.eclipse.simrel.build
soa-sca.b3aggrcon - org.eclipse.simrel.build
tcf.b3aggrcon - org.eclipse.simrel.build
tm.b3aggrcon - org.eclipse.simrel.build
windowbuilder.b3aggrcon - org.eclipse.simrel.build
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Kepler dates, IP Logs, and reviews

[Tsvetkov, Krum]

I opened a ticket some time ago, proposing to have the link on the project 
page: https://bugs.eclipse.org/bugs/show_bug.cgi?id=400551
I guess it will be then easy to find.

Krum


From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Ed Willink
Sent: Freitag, 17. Mai 2013 08:26
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Kepler dates, IP Logs, and reviews

Hi

Found it. It's lurking on the left of
http://eclipse.org/projects/tools/ip_contribution_review.php, so if you ignore 
the rubbish from
http://eclipse.org/projects/tools/ip_contribution_review.php you get the good 
old review.

Regards

Ed Willink

On 17/05/2013 07:18, Ed Willink wrote:
Hi

What has happened to the old (very good) IP tool?

It gave me a good auto-generated log for MDT/OCL that I could easily review.

http://eclipse.org/projects/tools/ip_contribution_review.php is hard to find 
(no link from portal or project page) and gives me a list of over 600 bugs to 
review. No way. There have been zero IP contributions so I expect to do the job 
in 10 minutes not 10 hours.

If there really is a change in diligence then please threshold it at resolution 
after Juno, since all pre-Juno bugs have been IP logged and approved.

Regards

Ed Willink


On 26/04/2013 19:24, The Eclipse Foundation wrote:
Kepler approaches.

I'm starting to get IP Log review requests for the upcoming release. In at 
least two cases, I'm pretty sure that the submitter thought that the release 
date was in May. To be clear, here are the dates:

May 24/2013 - Deadline to submit IP Logs for Kepler releases
June 5/2013 - PMC-approved Review materials submitted to EMO
June 12/2013 - Kepler Uber Release review
June 26/2013 - Kepler release

The IP Logs are not due for another month. It's still a little early, but it's 
perfectly acceptable to submit your IP log for review in advance of the actual 
required-by date. Just keep in mind that the log needs to accurately reflect 
the content that you're releasing; if you anticipate receiving any 
contributions from folks who are not committers, it might be a good idea to 
hold off for a while.

While I'm at it, I'd like to make a plea to everybody to please try and honour 
the dates specified. There are a few projects that make a habit of submitting 
the required materials late; this causes a lot of stress for everybody 
involved. If you haven't started thinking about your IP Log and review 
documentation, now might be a good time to do so.

I need to have you PMC-approved review documentation before EOB on June 5/2013. 
You can either do what we've been doing for years and submit this information 
as a presentation, document, PDF, or whatever. Or you can just enter review 
information directly in the release record in the Project Management 
Infrastructure. A few of you have already started doing the latter; my sense is 
that it is an easy way to assemble and provide this information. Please let me 
know if you think otherwise, or if there is anything that we can do to improve 
it.

The PMC approval part is important. Get it approved. This may take some time. 
Plan to engage your PMC at least a full week in advance of the June 5 deadline. 
PMC members, please make sure that the document is complete and that you are 
satisfied with its content before providing your approval. When I look at the 
extremely short (or non-existent) outside contributions sections on some IP 
logs, I grow concerned that some projects aren't doing enough to court the 
community and grow diversity.

Please use the Release Review checklist to make sure that you've done all the 
necessary bits:

http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist

Note that this checklist has been around for a long time. There should be 
nothing new or surprising here.

I've noticed that a lot of projects do not have plans posted. This is an 
important and necessary part of the development process. Plan information can 
be entered directly in the release record in the Project Management 
Infrastructure. Providing a project plan in a standard format is required. 
Wrestling with XML is no longer required. It's easy. Please make this happen.

Note that planning should happen at the beginning of a release cycle. PMCs, 
please impress the importance of this on your projects.

Thanks,

Wayne
--
Wayne Beaton on behalf of the Eclipse Foundationhttp://www.eclipse.org/
[EclipseCon France 2013]http://www.eclipsecon.org/france2013




___

cross-project-issues-dev mailing list

cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



No virus found in this message.
Checked by AVG - www.avg.comhttp://www.avg.com
Version: 2013.0.3272 / Virus Database: 3162/6275 - Release Date: 04/26/13

Re: [cross-project-issues-dev] Status and outlook for M7

[Tsvetkov, Krum]

Hi,

I made a change to update MAT contribution for M7 (updated the p2repo location 
and the version numbers), and the aggregator build picked it:
https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/421/

However, when I look into the console logs I see that the build still takes our 
old bundles. Did I miss something?

Git tree:
http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/mat.b3aggrcon
...
  repositories 
location=http://download.eclipse.org/mat/kepler/M7/update-site/; 
description=Memory Analyzer Updates
features name=org.eclipse.mat.feature.feature.group 
versionRange=1.3.0.201305080113
...

Build output:
https://hudson.eclipse.org/hudson/job/simrel.kepler.runaggregator/421/consoleText

...

 [exec] Loading repository 
file:///home/data/httpd/download.eclipse.org/mat/kepler/M5/update-site
...

 [exec] - mirroring artifact 
osgi.bundle,org.eclipse.mat.api,1.3.0.201302052014
...

Any hints?
I checked the commit id in the console log, and it is my commit.

Krum
PS: I just saw that the next build still uses our old contribution.

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David M 
Williams
Sent: Mittwoch, 8. Mai 2013 08:09
To: cross-project-issues-dev@eclipse.org
Subject: [cross-project-issues-dev] Status and outlook for M7

Just a reminder that today (Wednesday) is the last day to make contributions 
towards the M7 Sim. Rel. repository.

As usual, we will set the deadline for 5 PM Eastern ... but, glad to be 
flexible for a few additional hours, if projects speaks up here to this list 
and requests additional hour or two (and preferably why)

Don't forget to check the repo reports from time to time ... lots of good stuff 
in there to fix for RC1.
http://build.eclipse.org/simrel/kepler/reporeports/

Here are two things keeping me awake tonight (among others, not related to Sim. 
Release):

1) I believe EGit is planning to move to 3.0.0 (still) in M7 and I have seen 
no warm up contributions yet, so I am anxious to see what, if anything breaks 
from that. (Short runway!)

2) I've not seen a green build for EPP for M7 and in talking to Markus, he's 
not had time to work on it yet, getting RAP contribution ready ... so, in other 
words ... I sure hope no one (such as my Platform builds, broke the EPP builds!)

So ... have a good Wednesday! Sleep well. :)
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Status and Outlook for Kepler M4, +2 day

[Tsvetkov, Krum]

 mat.b3aggrcon - org.eclipse.simrel.build
I just added a new version of MAT and re-enabled it.
Waiting for the build results...

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of David M 
Williams
Sent: Dienstag, 18. Dezember 2012 23:47
To: Cross project issues
Subject: [cross-project-issues-dev] Status and Outlook for Kepler M4, +2 day

Lots of activities today, going much better than yesterday. Appears nearly 
everyone is mostly in, some waiting for the BIRT fix. One day to go!

amp.b3aggrcon - org.eclipse.simrel.build
birt.b3aggrcon - org.eclipse.simrel.build
dltk.b3aggrcon - org.eclipse.simrel.build (2 matches)
egit.b3aggrcon - org.eclipse.simrel.build
mat.b3aggrcon - org.eclipse.simrel.build
soa-bpel.b3aggrcon - org.eclipse.simrel.build
webtools.b3aggrcon - org.eclipse.simrel.build

Thanks for everyone's attention and quick fixes when the aggregation does break.

We don't have to be perfectly clean for M4, but for those 64 missing about.html
http://build.eclipse.org/simrel/kepler/reporeports/reports/layoutCheck.txt

or 8 incorrect or missing license files in features,
http://build.eclipse.org/simrel/kepler/reporeports/reports/licenseConsistency.html

be sure to set aside some time in January to fix these types of issues early, 
if you don't fix for M4, and not leave to the very end.

Thanks,
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Kepler Aggregator cannot start

[Tsvetkov, Krum]

Hi,

sorry for the spam if this problem was reported already in some form.
The last two builds of the Kepler aggregator failed with the following 
exception:

Building remotely on Fastlane
Checkout:simrel.kepler.runaggregator / 
/opt/users/hudsonbuild/workspace/simrel.kepler.runaggregator - 
hudson.remoting.Channel@115ed9ec:Fastlane
Using strategy: Default
Last Built Revision: Revision 021937fb7740edb6a70852dfbe338e4f4dee6d53 
(origin/master)
FATAL: cannot assign instance of hudson.EnvVars to field 
hudson.plugins.git.GitSCM$3.val$environment of type hudson.EnvVars in instance 
of hudson.plugins.git.GitSCM$3
java.lang.ClassCastException: cannot assign instance of hudson.EnvVars to field 
hudson.plugins.git.GitSCM$3.val$environment of type hudson.EnvVars in instance 
of hudson.plugins.git.GitSCM$3
at 
java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(ObjectStreamClass.java:2032)
at 
java.io.ObjectStreamClass.setObjFieldValues(ObjectStreamClass.java:1212)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1953)
at 
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at 
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
at 
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at 
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at 
java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at hudson.remoting.UserRequest.deserialize(UserRequest.java:178)
at hudson.remoting.UserRequest.perform(UserRequest.java:98)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:283)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at 
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)

https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/job/simrel.kepler.runaggregator/136/console

Any  idea how to overcome this? I just wanted to check that my contribution 
doesn't break the build :)

Krum
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev