Here are the minutes of meeting.
-- Sriram
---------- Forwarded message ----------
From: Sriram Narayanan <srir...@gmail.com>
Date: Mon, Jan 30, 2012 at 12:11 AM
Subject: Minutes of meeting - Jan 28 2012
To: Bangalore OpenSolaris User Group <ug-b...@opensolaris.org>
The meeting was held at Thoughtworks Koramangala, Bangalore. There
were 4 attendees this time and we discussed a number of things
1. Discussion about Belenix directions.
Sriram informed others that he'd resumed work on Belenix again, and
that the website would be hosted at the new server at Moscow.
2. Discussion on Continuous Integration.
The four attendees engaged in a discussion on Continuous Integration,
and the various practices that are applied to ensure that Continuous
Integration works for all. There was also a demo of how build
pipelines, build stages and jobs can be used to decrease build times,
and how build agents can be used to distribute build tasks.
3. A comparison between Continuous Integration and gated checkins.
At Sun/Oracle, the development process for ON is the gated checkin
process. The attendees compared this with Continuous Integration. One
of the realizations was that if teams working on features are provided
with separate and complete build pipelines to test their integrations
with upstream, then merges would be just large changesets backed by
the confidence that a lot of the integration would have already been
tested.
"Feature Branches - the pros and the cons" is a rather large topic, so
we did not discuss this more.
4. A review of a soon-to-be-submitted proposal on build systems
Sriram gate a brief sketch about his exploratory work on a zone based
build grid, where build zones would be used for building packages, and
all dependencies would themselves be used as packages. This document
needs to be proof read once and then submitted to the belenix-dev
mailing list.
5. A review of the ON folder structure for Continuous Integration
The discussion then moved to what would be required if ON were to be
build using a Continuous Integration process. The idea: let a
developer check in code, and let only that specific component be
built. Let the non-kernel stuff be build separately, and a de-coupling
be in place.
We reviewed the ON folder structure using the opengrok instance at
opensolaris.org. We discussed how drivers are placed separately from
various commands such as bash and vi, and how it is possible to have
incremental compiles. Oneinvestigation point identified was "how to
update the CTF data" in genunix as well as the driver/module when a
driver or other module is specifically built and updated".
All in all, the various discussions kept us engaged for two whole
hours, and the next meeting in Feb should hopefully be equally (if not
more) engaging and informative.
-- Sriram
------------------------------------
Belenix: www.belenix.org
Twitter: @sriramnrn
--
------------------------------------
Belenix: www.belenix.org
Twitter: @sriramnrn
_______________________________________________
belenix-discuss mailing list
http://mail.opensolaris.org/mailman/listinfo/belenix-discuss
http://groups.google.com/group/belenix-discuss