My first thought was to
wonder if we
should do new work, with a new feature.xml (and map file) and to not
continuously
re-build the 186 bundles we currently have.
I suspect most of them are pretty
much
"done". I recall in the past that while we had good versions,
we knew there would be changes coming associated with source
attachments,
etc.
so it was not that much of a stretch
to think of re-building all of them all, even though they were not
changing
much. While I am sure we will find exceptions and want to rebuild some
of them where we find errors or improvements to make, it sort of goes
again
my "efficient programmer" nature to keep rebuilding hundreds
of bundles which are not changing. For those wondering, ... our current
Orbit builds take "just" an hour or so to run ... but sometimes
we want to do several per day, sometimes in quick succession, and then
you also have all the duplicate storage, etc., so in general doesn't
seem
like a good practice to rebuild hundreds when only a few have changed
(and,
one of the objectives of Orbit was to demonstrate best practices :)
+1
My second thought, was to
wonder if
there is some P2 magic (the "it-just-works provisioning platform")
that would allow some better conceptualization to drive the build,
instead
of a "feature". Any volunteers to educate us and/or create a
P2'd build?
I think there is lots of opportunity there. I'd be happy to outline
the build related vision that we have had for this kind of provisioning
system since it was first conceived.
I bring this up now, to
ask this Orbit-dev
list if we should have a short "moratorium" on new builds for
a week or so, until we get this settled? Or, if it seems like it will
take
a long time to settle, and we should just keep moving and sort it out
as
we go? As once concrete example, if we were going to start with a
"fresh"
feature.xml file (and a new map file) for new work, then I'd like to
leave
the current one just as it is (or, was, for our Ganymede R-build) just
to have a clear dividing point.
IMHO this not going to be sorted out any time soon. It is not a
trivial problem and while p2 has function that will help, it is not a
complete cover of this problem set.
Any one else had enough
time yet to
have thoughts of Orbit's future?
I used my available time in answer this mail ;-)
Jeff
|
