ACTION REQUIRED: Code Freeze for Sprint 113 / devex 6 is today
by Nick Boldt
Since the current DevStudio sprint ends on Tuesday May 3 next week,
and we need to have something built and ready to demo on that day,
today (as we have often done on Thursdays in the past) should be
considered a Code Freeze day.
This means that by EOD today (whatever your timezone) please be done
pushing things into master branch.
Over night tonight I will ensure that a build is run to pick up all
fresh commits and will therefore have something I can stage to QE
tomorrow, and that Denis can then use for the devplatform installer
build & signing.
This Alpha1 build will be pushed around 9am PST / 12pm EST / 6pm CST /
9:30pm IST Friday April 29. Exception to this will be IFF dev, QE, or
anyone else finds a blocker before that time. You should fix that
(with at least one +1 on the PR/JIRA) but your MUST ensure you notify
myself via email (or better, via HipChat) so I know to expect the
change in the build pipeline and the resulting delay to the staging
process. Blockers only, please!
Please also ensure you kick off your job *as soon as the commit is
pushed to github*, that would save me having to query for new changes
and manually babysitting your build and all its downstream ones. A
reminder: your job runs automatically on github commits, but only
checks every 8 hours* to avoid building partial commits and causing
failures when commits span across repos.
Not sure where your job is? Look here:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
for your component/project name.
This should give QE all day Monday to find any blockers, and if
necessary, we MIGHT have time to fix them before the demos on Tuesday.
Any questions, please don't hesitate to ask them in this thread or
HipChat or #jbosstools on freenode.
Thanks,
Nick
* - Aside: Should we change that to a check every hour, now that we're Agile?
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
7 years, 12 months
ACTION REQUIRED: 4 issues with no component
by manderse＠redhat.com
This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks!
* No component for JBIDE-22251
https://issues.jboss.org/browse/JBIDE-22251
Summary: adt wireless (customer) support number !18444524051! adt wireless customer service phone number
Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 9:53:28.060293
----------------------------
* No component for JBIDE-22250
https://issues.jboss.org/browse/JBIDE-22250
Summary: (adt) wireless home security number !18444524051! phone adt wireless customer support phone number
Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 9:59:00.060683
----------------------------
* No component for JBDS-3860
https://issues.jboss.org/browse/JBDS-3860
Summary: JBDS 9.1 not connecting to internet
Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 0:07:52.061047
----------------------------
* No component for JBIDE-22252
https://issues.jboss.org/browse/JBIDE-22252
Summary: Adt MONITORING help desk phone number 1844 452 4051 adt MONITORING support phone number
Assignee: None set.
Component: None set - please fix.
Problem: No component - please assign this issue to one or more components.
Last Update: 9:51:21.051558
----------------------------
Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27
8 years
