ACTION REQUIRED: Code Freeze for end of Sprint 114 :: prepare for this week's staging build
by Nick Boldt
TL;DR:
* code freeze for all projects' master branches starts *today at 2pm PST /
5pm EST / 11pm CST*.
* *code freeze lifts on Wed*, May 25 after the Demo calls, at the start of
Sprint 115.
* you *don't need to create a branch* or update your root pom to a newer
parent pom (yay, less process!)
* *build will run Thursday night* and be copied to /staging/ on Friday
morning EST.
* *From Fri to Wed, you should *NOT* push anything into master branch*;
instead, see below for other work you can do to close out the sprint
----
As Sprint 114 is done on Wed, May 25 (and we need something that's demoable
that day!), it's time again to do a code freeze in master so that I can
build the latest CI bits (Thurs), pull them tomorrow (Fri), turn that into
something staged for QE to test (Mon), and then demo (Tues).
So, here's how that will work:
* we will not create branches
* we will just pull the latest bits from master -- whatever is committed as
of 2pm PST / 5pm EST / 11pm CST is what will be built.
* we will use parent pom 4.4.0.Alpha1-SNAPSHOT - no Task JIRA needed to
change this to Alpha2
* no root pom changes in each project are needed (we'll use
4.4.0.Alpha1-SNAPSHOT) - again, no Task JIRA needed
* features and plugins will still be called "Alpha1", not "Alpha2". This is
simply to denote QUALITY, not to identify WHICH sprint/milestone.
This code freeze will continue until Wed, May 25 when this sprint (Sprint
114) ends & the next one (Sprint 115) starts.
If you have things you need to commit on Friday, here's how you can keep
working without losing productivity:
* leave those commits in a PR or topic branch. Have a bunch of commits that
depend on others? Create a "testing" branch and push everything there; then
at the start of the next sprint, merge testing -> master.
* work on doc or N&N
* write a blog
* create a screencast / demo of your latest accomplishments!
* do some usability testing of your component or some other component
* use your tools! open some JIRAs if you find problems!
* JIRA cleanup/triage
* plan for the next sprint
Freaked out? Talk to Max or Alexey. They agree it's useful to do the above
things at least ONCE every 3 weeks instead of at the end of the release.
Welcome to Agile. :D
What's the process we'll use for this build? I will:
* build everything Thursday night,
* disable the jobs Friday morning,
* copy bits from /snapshots/ to /staging/AlphaX/,
* announce it to QE, &
* re-enable the jobs
* tag the projects using the SHAs used to produce the build
Note that the staging folder will be called Alpha2, as this is a
"productization" step and is not dependent on parent pom or BUILD_ALIAS. I
want to split the notion of "what the bits are called" from "what the
release is called" since that's the direction Program Management is
heading.
---
Aside: I'm going rock climbing north of Montreal for the long weekend
(Monday is a holiday here in Canada) so I'll be working late
tonight & offline by about 2pm tomorrow. Won't be online again until
Tuesday morning. If anything goes seriously wrong, ping Mickael or Alexey.
:D
Thanks for reading this far!
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
7 years, 11 months
Tycho 0.25.0 available for testing
by Nick Boldt
FYI. If you're bored and want something to do, please run your *master
branch* builds locally using Tycho 0.25 to see if anything breaks.
I've already added the 0.25.0 staging site to the parent pom so the
bits should resolve.
mvn clean install -DtychoVersion=0.25.0
More info:
https://wiki.eclipse.org/Tycho/Release_Notes/0.25
----
Hi,
> Tycho milestone release 0.25.0 has been staged. For details of new features and bugfixes, see release notes [1].
> Please help by testing the staged milestone build. To use it, change your tycho version to 0.25.0 and add snippet [2] to your pom.
works fine for Eclipse Code Recommenders.
We even made use of some of the new features
(target-platform-validation-plugin:validate-target-platform ability to
be defined in paerten POMs [1]) and the new <jvmArgs> syntax for
tycho-eclipse-plugin:eclipse-run. :-)
Best wishes,
Andreas
[1] <https://bugs.eclipse.org/bugs/show_bug.cgi?id=483405>
[2] <https://bugs.eclipse.org/bugs/show_bug.cgi?id=486799>
--
Codetrails GmbH
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940
_______________________________________________
tycho-user mailing list
tycho-user(a)eclipse.org
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user
--
Nick Boldt :: Productization Lead :: JBoss Tools & Dev Studio :: Red Hat, Inc.
http://nick.divbyzero.com
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
7 years, 11 months
Arquillian testing in JBoss Tools
by Brian Fitzpatrick
Hi all,
I'm going fishing for information here, but do we have any facility in
JBoss Tools for helping folks create Arquillian tests?
Seems that it would be a good fit for working with the Servers/Runtime
framework maybe?
--Fitz
--
Brian "Fitz" Fitzpatrick
Sr. Software Developer, Fuse Eclipse Tooling
7 years, 11 months
jira sprint open/closing
by Max Rydahl Andersen
Hey,
I can't see the history of sprint-edits in jira so posting this to wider
list for info.
Someone started devex #114 on May 4th (correct date) but did not close
devex #113 so all the issues on it is still lingering in #113.
I'm sure this was done with good intentions and whoever did it might be
missing some permissions (dumb jira), but this gives everyone some extra
bookkeeping to do since when I marked #113 closed (end day May 3rd) we
ended up with:
devex #113 April 2016
74 issues were Done.
13 incomplete issues will be returned to the top of the backlog.
1 partially complete issue will be returned to the top of the backlog.
Those 14 issues I assume was on #113 for a reason - they are now no
longer on the sprint boards.
Thus two things:
A) Don't start a new sprint before the one before it is closed.
B) Please go and check the top issues in backlog to see if they are
supposed to be outside
#114
C) Please raise on mailing list(s) when/if sprints can't be closed
properly - especially
when we are in starting phase of figuring out the right permissions
needed etc. to
close/handle the sprints best in jira. I'll then be able to help
figure out what is
missing.
Thanks,
/max
http://about.me/maxandersen
7 years, 11 months
