Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Ganymede Must Do's (#13, #15)

Martin, regarding #13,

The jars must be conditioned for packing in the project's regular build process.  If they are not conditioned before submitted to the Ganymede build, the output will just be regular jars, instead of the  bandwidth friendly pack.gz jar files.
Implementing a digest on the update site is easy to do and improves the user experience tremendously when downloading updates, so why not :-)  Digests are implemented independantly in each update site.



Martin Oberhuber <martin.oberhuber@xxxxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

11/01/2007 09:32 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
[cross-project-issues-dev] Ganymede Must Do's (#13, #15)

Hi all,

when reviewing Ganymede must do's for a recent DSDP PMC meeting,
I came across two issues or questions:

* #13 - pack200 and digesting:
 I tought that the pack200 stage and digesting are actually done by the
 Ganymatic when copying the projects to the common site. Is it really
 a must-do that projects pack and digest their own update sites?

 It certainly doesn't hurt, but is the argument really to save download
 bandwith or should the argument be that projects ensure their
 bits don't get corrupted by pack200 when it's done later by the

* #15 - declaring plugin sizes in feature.xml
  Are you aware that currently, a bug in update manager inhibits
  showing the declared sizes when a digest is made - which is
  required as per #13:
  Also, there is an open bug asking for releng / build process
  to automatically compute the plugin and feature sizes:
  I think that when #15 is a must do, there should be some
  automation around computing the sizes.

Any comments?

Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member

cross-project-issues-dev mailing list

Back to the top