I think this is more overhead than we can afford. Ensuring we can do
an automated build/test cycle on branches/legals before integrating
to branches/4.0b1 is cheap and will catch big issues. I think we need
to rely on code reviewers to verify that the change does fix the
issue -- this will use the resource we have more of (developers)
while keeping QA focused on the test plan.
jim
On Dec 8, 2006, at 1:06 PM, Benjamin Shine wrote:
To clarify a tricky step in the process:
We shouldn't move changes into the 4.0b1 branch without being very
confident about them, and to be very confident about them, we need
to have them verified in an official build. If we don't do a legals
build before integrating to 4.0b1, then we're losing the benefit of
having a buffer.
therefore: changes must go through an official legals build, and be
verified by mamye in an official legals build, before they will be
integrated to 4.0b1.
in other words... breathe deeply!
On Dec 7, 2006, at 12:48 PM, Jim Grandy wrote:
A possibly non-obvious consequence of this is that all new bugs
should be filed against OL4, not OL4B1. The one exception is if a
bug reproduces in branches/4.0b1 and not in branches/legals --
then it should be filed against OL4B1.
jim
On Dec 7, 2006, at 11:52 AM, Jim Grandy wrote:
I wanted to let everyone know that we branched for OL4 Beta 1
this morning. The release branch is:
http://svn.openlaszlo.org/openlaszlo/branches/4.0b1
Developers (including tech doc) should continue to check into
branches/legals, with proper code reviews. If you have a change
that you think should be considered for 4.0b1, send an email to
laszlo-dev with the following information required:
- SVN revision numbers
- JIRA bug numbers covered
- A prose description of the scope of the change. If you
considered alternative fixes that might merit consideration for
the release, mention those.
- A prose description of the riskiness of the change. What would
need to be re-tested if we took this change?
We're also making some changes to JIRA to handle the branch
process. I've renamed this release and the next one "OL4B1" and
"OL4B2" respectively. I'm creating an "OL4" release and moving
all OL4B1 bugs to OL4. This is so that you are all resolving
changes against the legals branch. When a change is approved for
integration into OL4B1, we will *add* that release to the Fix
Versions field.
Please go back and read that paragraph again. It's important we
all understand this: you check changes in with Fix Versions=OL4,
and when a change is approved for B1 we integrate the change into
branches/4.0b1, and add OL4B1 to Fix Versions.
jim
benjamin shine
software engineer
[EMAIL PROTECTED]
