We use bundles like config maps (to specify what versions to load) and
applications (to group packages together). We use packages somewhat like
sub-applications are used in ENVY (to categorize code). Where packages
declare prerequisites, they do not specify versions because that would
conflict with the version lineup specified by the bundle.
Developers version their package changes as integration-ready. Release
tools find and merge all integration-ready changes (for all contained
items) to produce an internal-release version with a ".0" suffix to
indicate an integration point that developers can base further changes
on. The ENVY 'open edition' functionality that some people like can be
achieved by just using the release tools to merge integration-ready code
and re-parent (skipping the publish part); however, developers usually
publish a new internal-release version when they feel their changes are
safe for general use. The release tools we've developed are an important
part of making this all work so well.
I don't care if it is made easier to configure package prerequisites
because we would probably still use bundles. Setting package version
prerequisites would be in conflict with the way we use bundles for
version lineups. I see no benefit to declaring an inverse relationship
between versions. This old dog thinks in terms of containment and
snapshots.
With ENVY you could create a new map edition and customize the lineup
without having contained items loaded. Much trickery needs to be done in
order configure bundles prior to load. For example, this affects us with
each new GBS release because GBS only initializes properly when loaded
from a parcel and store-load-initialization often leaves GBS inoperable.
The code relationship that is maintained with a loaded parcel (that is
also represented in StORE) makes it difficult to just replace and reload
the parcel files. Those issues are higher priority to me than easier
prerequisite setting.
Paul Baumann
-----Original Message-----
From:
vwnc-bounces@... [mailto:
vwnc-bounces@...] On
Behalf Of Bruce Badger
Sent: Monday, May 12, 2008 6:42 PM
To: VW NC
Subject: [vwnc] Bundles
On his Blog, Jim asked about Store Bundles:
* Do you use bundles?
* If so, how do you use them, and why?
* If setting explicit pre-reqs was easier, would you still use
bundles?
I do use bundles.
I use nested bundles with an outer master bundle for every project.
Even if setting preq versions were easier I probably still use bundles.
I like the explicit containment.
--
Make the most of your skills - with OpenSkills
http://www.openskills.org/_______________________________________________
vwnc mailing list
vwnc@...
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
--------------------------------------------------------
This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.
_______________________________________________
vwnc mailing list
vwnc@...
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc