It is too late for SR2, for several reasons, but a great suggestion for
Kepler, if the TM project (or others) want it.
Just to briefly outline the reasons, we are already up to RC2 and RC3, so
I think it'd have to be a blocking problem to cause all that stress, and
it doesn't sound like a
Right now our master branch is still being using for Juno maintenance.
We'll put this into our Kepler builds when 1) we create our Juno
maintenance branch off the master (probably on Feb 25) and 2) the CQ is
approved. The earliest Kepler build that you'll see it would be Kepler
M6.
-- Dave
Thanks for the reminder, David. I've asked Janet about the date and
will announce what she decides when I hear back.
Wayne
On 01/29/2013 03:17 AM, David M Williams wrote:
And, Kepler is not that far away. I
don't recall seeing the
Sorry if this is another dumb question. The result of the Juno aggregation goes
to releases/maintenance, right?
The reason that I ask is that the console log appears to indicate that the last
build aggregated PTP 6.0.4.201301291850, however when I look in
releases/maintenance, all I see is
Check now.
The final step to get into .../releases/maintenance depends on me
running a manual job, and I was 3 days behind. (but just now promoted).
I'll get that automated one of these years. :/
Thanks,
From: Greg Watson g.wat...@computer.org
To: Cross project issues
