|Re: [cross-project-issues-dev] RC5 ... are we done yet?|
Yes, we are. Well, for staging site.
Activity is quiet and no one has mentioned being delayed, so assuming we
And, just sort of done for sort of a short period of time.
If someone really does have a true stop-ship bug, you can post re-spin
request here for consideration to see if everyone else agrees to re-spin.
(remember, it would have to be more than just a bad bug ... but something
damaging to users or infrastructure).
I know as we enter final daze
(hint, read the document!)
many people will eventually (over next week or two, depending on your
releng processes) want to update your .build file to point to your
"permanent" update site, instead of "milestones" or "interim", etc. That's
fine, I'll leave builds "on" but these builds will not be pushed to
'staging' (staging is done).
That's fine, on one condition ... that you still make sure your .build
file is correct and really "builds" ok. That's why we leave the builder
active. We need to keep in a state of being able to re-build, in case it
is needed for some reason. That's just good releng hygiene. It is harder,
with Simultaneous Release, since the build "data" comes from two sources,
the .build files (which we could tag, have control over, etc.) but also
your own update sites, which totally depends on you and requires you to
keep "constant" so we can always re-build, if we had to. And, don't
forget, vice-versa ... if/when you change your "milestones" directory to
"updates" (or similar) be sure you update your .build file so it will be
accurate and continue to build.
So, what next, after that?
In about a month (or so) we'll start some maintenance efforts for Galileo
SR1. At that point you'll update your .build files again (if you have
maintenance) and provide an interim maintenance update site to pull from.
But please do not modify your .build files for maintenance until
instructed ... just to make sure we are all ready and know what's going
As always, if questions, issues, or you need something special, just ask
(here on cross-project list).
cross-project-issues-dev mailing list
Back to the top