respin-b needed
by Max Rydahl Andersen
JBIDE-20311 was not fixed.
openshift was built before foundation thus it was not picking up the
reverted api change.
Details in jira - it was a "fun" one to figure out. Thanks mlabuda :)
Nick - possible to do a respin and reaggregate ?
mini-retrospective:
if we actually ran tests on the aggregated build AND the tests tested
the fix we made we would have caught this.
/max
http://about.me/maxandersen
8 years, 9 months
ACTION REQUIRED: JBDS 9 / JBT 4.3 Beta2 respin-a code freeze is TOMORROW // updated Beta2 release schedule // vacation reminders
by Nick Boldt
The cut off for getting last-minute blockers into Beta2 is the end of
tomorrow. After that, no more changes will be accepted into Beta2.
This list [1] is now at 21 issues, with 5 unresolved. Of these 5, only 3
are BLOCKER or CRITICAL. Please do not include issues which are of lower
priority that this. Please also ensure you get your PRs reviewed before
pushing into the Beta2x branch.
[1]
https://issues.jboss.org/issues/?jql=filter%20%3D%20ds_latest_freeze%20AN...
---
Here's the release schedule, modified to accommodate respin-a.
* Thur 23 Jul: EOD code freeze respin-a; all components and aggregates
build over night.
* Fri 24 Jul: builds staged for QE starting @ noon EDT, avail ~3pm EDT
* Mon 27 Jul: QE starts testing; signoff EOD Tues AT THE LATEST (earlier
is better!) (cc: Len/Martin)
* Wed 29 Jul: bits released to jboss.org (cc: Paul),
devstudio.redhat.com & customer portal (cc: Chris)
* Thu 30 Jul: blog/announcements go out (cc: Alexey/Fred)
This new schedule delays the planned release date by 2 days - was Jul
27; now Jul 29.
---
Please note these vacations:
* Mickael: Jul 20 - Aug 20
* Max: Jul 25 - Aug 8
* Nick: Jul 30 - Aug 4
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
8 years, 9 months
Please remember - two set of eyeballs on changes before they go into code frozen branch
by Max Rydahl Andersen
Hey,
Just a reminder that we are in code frozen state for JBoss Tools and
Developer Studio.
That means *any* change, no matter if in code, docs, releng scripts,
etc. should at least have
someone else review it *before* it goes into the 4.3/9.0 branches.
It does slow things down, but
we've found more in these reviews historically than I care to think what
we missed - plus it helps
spread the knowledge of what is going in ;)
Also, having *tests* included for the changes is crucial and very
helpful in getting it reviewed faster.
We got a good chunk on vacation but this week Alexey, Denis, Fred and I
are still around so do please
ping on #jbosstools if you are missing a set of eyes.
Thanks,
/max
http://about.me/maxandersen
8 years, 9 months
