[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and outlook for Luna SR2

Ok, perhaps a good time to remind everyone, then, that if you do have "no change in your b3 aggrcon files" but, for what ever reason, want a new "build", you can either "touch" one of your files with something innocent, or, better, you do have permission to "start a "runAggregator" job on Hudson, at
https://hudson.eclipse.org/hudson/view/Repository%20Aggregation/
as described in one of our FAQs:
https://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#But_what_if_I_really_want_to_kick_off_the_build_myself.3F

(Only a few of us have permission to "promote a build", though, so if you ever end up "waiting for a promotion", say, for more than an hour (and no other aggregation jobs are running), and you really need it, don't hesitate to post a note here to cross-project asking for a promotion ... we might have just lost track, or gotten distracted).

One more "word of advice" (which, I don't think will apply here ... not right now, anyway) is that in general, if you ever have an unsigned version, that has "been in a build" and then distributed, and then you sign it, technically the qualifier should be incremented, so those bundles/features appear "newer" than the unsigned ones. Otherwise, if anyone already has you unsigned versions installed, they will not get the signed version (since, with the qualifier is the same, p2 assume "they are exactly the same thing" and will not re-install them (in most cases). But, as I said, I don't think that applies here (because we purposely replace all bundles in a b3 aggregation build, not yet trusting contributors to have "distinct content" per qualifier ... so I suspect no work is needed here from you (unless, you know better, about how long it has been unsigned).

Thanks,

P.S. Still hope you learn how to "pack200" them someday. Again, feel free to ask for help, here on this list, or in bugzilla.




From:        Ben Gamble <BGamble@xxxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        02/18/2015 01:47 AM
Subject:        Re: [cross-project-issues-dev] Status and outlook for Luna SR2
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




Actually I donât know how weird this is, but the BIRT source has not changed since RC1, which means neither have the versions of the primary features listed in birt.b3aggrcon.  The plugins in the repository they point into have, though (today).  (In particular, they are now signed.)
 
n  Ben
 
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent:
Tuesday, February 17, 2015 10:29 PM
To:
Cross project issues
Subject:
Re: [cross-project-issues-dev] Status and outlook for Luna SR2

 
The reports are generated when ever a build is promoted to "maintenance". From what I can see, there has been no changes to promote, for about 28 hours. (Though, a build will finish in about an hour).

Have you made the changes a while ago, and have just been waiting for a "build" (which, must happen before a "promote")?


In any case, check back in an hour or two.


Thanks,





From:        
Ben Gamble <BGamble@xxxxxxxxxxx>
To:        
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        
02/18/2015 12:52 AM
Subject:        
Re: [cross-project-issues-dev] Status and outlook for Luna SR2
Sent by:        
cross-project-issues-dev-bounces@xxxxxxxxxxx





Are these reports rerun on a schedule or something?  Iâd like to see whether I fixed BIRT properly.

 
n  
Ben
 
From:
cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent:
Tuesday, February 17, 2015 7:21 AM
To:
Cross project issues
Subject:
[cross-project-issues-dev] Status and outlook for Luna SR2

 

Don't forget a) tomorrow, Wednesday, 2/18, is the last scheduled day for any contributions to Luna SR2,
and b) you don't have to wait until the last day to make a contribution!

For example, as it is, it is hard to see other unsigned bundles, as there are so many from BIRT, in

http://build.eclipse.org/simrel/luna/reporeports/reports/verifydiroutput/unsigned.txt

If I go to the trouble to sort and filter, I see these others. Do any of them come from BIRT? We have already had a community/user complaint about one of them (
Bug 460094)


 javax.persistence_2.1.0.v201304241213.jar:

 org.apache.derby.core_10.5.1.1_v201501121639.jar.pack.gz:

 org.apache.derby.core_10.5.1.1_v201501121639.jar:

 org.eclipse.gemini.jpa_1.2.0.M1.jar:

 org.w3c.sac_1.3.0.v201501121639.jar.pack.gz:

 org.w3c.sac_1.3.0.v201501121639.jar:

 uk.co.spudsoft.birt.emitters.excel.source_4.4.2.v201410272105.jar.pack.gz:

 uk.co.spudsoft.birt.emitters.excel.source_4.4.2.v201410272105.jar:

 uk.co.spudsoft.birt.emitters.excel_4.4.2.v201410272105.jar.pack.gz:

 uk.co.spudsoft.birt.emitters.excel_4.4.2.v201410272105.jar:



Also ... pay heed .... several (not BIRT) are missing legal files:

http://build.eclipse.org/simrel/luna/reporeports/reports/layoutCheck.txt
  Checking: /home/data/httpd/download.eclipse.org/releases/maintenance/features
Checked 1119 of 1119.
Errors found: 2
Missing (edl-v10.html|epl-v10.html) in file: org.eclipse.xwt.feature_1.0.0.v20140612-1647.jar
Missing (edl-v10.html|epl-v10.html) in file: org.eclipse.xwt.source.feature_1.0.0.v20140612-1647.jar

Checking: /home/data/httpd/download.eclipse.org/releases/maintenance/plugins
Checked 5440 of 5440.
Errors found: 4
Missing (?:about|about_org.eclipse.emf.emfstore.client.ui.rap).html in file: org.eclipse.emf.emfstore.client.ui.rap_1.4.1.v20150213-0904.jar
Missing (?:about|about_org.eclipse.emf.emfstore.client.ui.rcp).html in file: org.eclipse.emf.emfstore.client.ui.rcp_1.4.1.v20150213-0904.jar
Missing (?:about|about_org.eclipse.gmf.examples.runtime.diagram.layout).html in file: org.eclipse.gmf.examples.runtime.diagram.layout_1.8.1.201408201453.jar
Missing (?:about|about_org.eclipse.ptp.etfw.feedback.perfsuite.doc.user).html in file: org.eclipse.ptp.etfw.feedback.perfsuite.doc.user_1.0.0.201502031415.jar



One day left!







From:        
Ben Gamble <BGamble@xxxxxxxxxxx>
To:        
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        
02/12/2015 07:47 PM
Subject:        
Re: [cross-project-issues-dev] Luna SR2 RC3 Repository is complete
Sent by:        
cross-project-issues-dev-bounces@xxxxxxxxxxx






Good question.  Looking into it.


Ben Gamble /
bgamble@xxxxxxxxxxxx

From:
cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent:
Wednesday, February 11, 2015 3:56 PM
To:
cross-project-issues-dev@xxxxxxxxxxx
Subject:
[cross-project-issues-dev] Luna SR2 RC3 Repository is complete


[â]


I wonder what's happened to BIRT's signing? But assume it will be fixed soon?

http://build.eclipse.org/simrel/luna/reporeports/reports/verifydiroutput/unsigned.txt _______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev