<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Probably it was a bad idea to change the process/terminology in the
last minutes. It created too much confusion.<br>
We didn't have formal code freeze. It's why I prefer to call this
build a snapshot, not the CR1 as you Nick announced it in your
email.<br>
The formal code freeze is going to happen this Thu.<br>
<br>
Anyway, we are still working in 4.3.x branch (mostly OS/CDK stuff).
We will do a formal code freeze this Thu and will provide a new CR1
build which we will rename to GA if we don't have respins.<br>
Let's discuss all this stuff on tomorrow build.next call.<br>
<br>
Thanks.<br>
<br>
<div class="moz-cite-prefix">On 03/29/2016 12:27 PM, Nick Boldt
wrote:<br>
</div>
<blockquote
cite="mid:CA+QcL13oA49sNxLVEGNibXH5kaD9syPXA3S+t7iTKE-eDyvHLg@mail.gmail.com"
type="cite">
<div dir="ltr">No, we did not code freeze last week. That's why
the minutes from the JBDS PM call say that the code freeze
slipped a week to Mar 31. <br>
<div><br>
</div>
<div>That's also why there were no task jiras sent out to remind
people of the steps needed to perform a code freeze. </div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Mar 29, 2016 at 12:26 PM,
Alexey Kazakov <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:alkazako@redhat.com" target="_blank">alkazako@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class=""> <br>
<br>
<div>On 03/29/2016 12:23 PM, Leonard Dimaggio wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>I thought that the current build was the result
of a code freeze, for all features other than
OpenShift - and that OpenShift would be frozen for
the March 31 build. No?<br>
</div>
</div>
</blockquote>
<br>
</span> That's correct.
<div>
<div class="h5"><br>
<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
-- Len<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Mar 29, 2016 at
12:09 PM, Alexey Kazakov <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:alkazako@redhat.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:alkazako@redhat.com">alkazako@redhat.com</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">We are not going to
fix all OS/CDK current criticals/blockers
targeted<br>
CR1. It's just impossible. We still need to
triage them. So we don't<br>
expect a lot of changes this week.<br>
We discussed that plan last week (which I
agree may be confusing) with<br>
Len. But if QE think they don't need any
special build until the formal<br>
code freeze this Thu because it doesn't help
you then let us know.<br>
<br>
Thanks.<br>
<div>
<div><br>
On 03/29/2016 11:47 AM, Marian Labuda
wrote:<br>
> Hey,<br>
><br>
> We in QE were wondering what is the
purpose of this kind of testing when there
was no formal CF yet. It has not changed
almost anything for us, because we are
already testing nightly builds for few
weeks. At first we thought it is the
approach to JIRAs what makes sense
(reviewing/acking before merging), but
this is already happening outside of
official testing phase. Having a code
freeze would make sense if there still
wouldn't be so many JIRAs to be fixed.
E.g. OpenShift has 6 blockers and 2
criticals which should be fixed before
formal CF (there are totally 19 blockers
and criticals not resolved and targeting
CR1, but half of them are installer
related with label havoc). And I think it
is far more safe to test on nightly build,
where those fixes are addressed to be sure
it is really fixed and no other
significant issue has raised. Could you
please bring light into this?<br>
><br>
> --Marian<br>
><br>
> ----- Original Message -----<br>
> From: "Alexey Kazakov" <<a
moz-do-not-send="true"
href="mailto:alkazako@redhat.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:alkazako@redhat.com">alkazako@redhat.com</a></a>><br>
> To: <a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org"
target="_blank">jbosstools-dev@lists.jboss.org</a><br>
> Sent: Monday, March 28, 2016 5:21:57
PM<br>
> Subject: [jbosstools-dev] 4.3.1 code
freeze and our plans for this week<br>
><br>
> Just for the clarification. To make
sure we all are on the same page.<br>
><br>
> We didn't have a formal code freeze
last week on March 24th as was planned
before. We didn't branch etc.<br>
><br>
> This is what we are going to do
instead:<br>
><br>
> 1. Nick built a snapshot build from
4.3.x branch on March 24th (the links are
below in the Nick's original email). It's
what he called JBoss Tools Core 4.3.1.CR1
bits<br>
> 2. QE can now start testing that
snapshot build<br>
> 3. Developers continue to work on
blocker/critical 4.3.1 issues this week
BUT please make sure:<br>
> - all PRs are properly reviewed and
approved by Fred, Max or Alexey before
merged to 4.3.x.<br>
> - all issues fixed this week have a
label "reapin-a" so it will help QE to see
what was fixed between two builds.<br>
> 4. The formal code freeze (Nick will
create all needed JIRA tasks and we will
branch, etc) is going to happen on this
Thursday, March 31. Let's call it JBoss
Tools Core 4.3.1.CR1 a<br>
> Those bits will be built from the
frozen 4.3.1.x branch and will be used in
GA release.<br>
> 5. We may build (and announce) more
respins if needed.<br>
> 6. After the code freeze this week we
would need to focus on documentation which
will include N&N. We also will help
the installer and doc teams with the
getting started page of the installer.<br>
><br>
> Thanks.<br>
><br>
><br>
> On 03/26/2016 02:11 PM, Nick Boldt
wrote:<br>
><br>
><br>
><br>
> As always, these are not FINAL bits,
but preliminary results for QE &<br>
> community testing. Not for use by
customers or end users.<br>
><br>
> Update site: <a
moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/mars/staging/updates/"
rel="noreferrer" target="_blank"><a class="moz-txt-link-freetext" href="http://download.jboss.org/jbosstools/mars/staging/updates/">http://download.jboss.org/jbosstools/mars/staging/updates/</a></a>
New + noteworthy (subject to change):<br>
> * <a moz-do-not-send="true"
href="https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew"
rel="noreferrer" target="_blank">https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew</a>
* <a moz-do-not-send="true"
href="http://tools.jboss.org/documentation/whatsnew/"
rel="noreferrer" target="_blank">http://tools.jboss.org/documentation/whatsnew/</a>
Schedule: <a moz-do-not-send="true"
href="https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page"
rel="noreferrer" target="_blank">https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page</a>
--<br>
><br>
> Additional update sites:<br>
> * <a moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1/"
rel="noreferrer" target="_blank">http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1/</a>
* <a moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.1.CR1/"
rel="noreferrer" target="_blank">http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.1.CR1/</a>
Target platforms:<br>
> * <a moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.2.CR1-SNAPSHOT"
rel="noreferrer" target="_blank">http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.2.CR1-SNAPSHOT</a>
* <a moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.52.0.CR1-SNAPSHOT"
rel="noreferrer" target="_blank">http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.52.0.CR1-SNAPSHOT</a>
Discovery sites:<br>
> * <a moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.1.CR1/"
rel="noreferrer" target="_blank">http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.1.CR1/</a>
* <a moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.1.CR1/"
rel="noreferrer" target="_blank">http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.1.CR1/</a>
Build folders (for build logs & update
site zips):<br>
> * <a moz-do-not-send="true"
href="http://download.jboss.org/jbosstools/mars/staging/builds/"
rel="noreferrer" target="_blank">http://download.jboss.org/jbosstools/mars/staging/builds/</a><br>
><br>
><br>
>
_______________________________________________<br>
> jbosstools-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org"
target="_blank">jbosstools-dev@lists.jboss.org</a><br>
> <a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
<br>
_______________________________________________<br>
jbosstools-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org"
target="_blank">jbosstools-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Len DiMaggio (<a
moz-do-not-send="true"
href="mailto:ldimaggi@redhat.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:ldimaggi@redhat.com">ldimaggi@redhat.com</a></a>)<br>
JBoss by Red Hat<br>
314 Littleton Road<br>
Westford, MA 01886 USA<br>
tel: <a moz-do-not-send="true"
href="tel:978.392.3179"
value="+19783923179" target="_blank">978.392.3179</a><br>
cell: <a moz-do-not-send="true"
href="tel:781.472.9912"
value="+17814729912" target="_blank">781.472.9912</a><br>
<a moz-do-not-send="true"
href="http://www.redhat.com"
target="_blank">http://www.redhat.com</a><br>
<a moz-do-not-send="true"
href="http://community.jboss.org/people/ldimaggio"
target="_blank">http://community.jboss.org/people/ldimaggio</a><br>
<br>
<img moz-do-not-send="true"
src="http://www.redhat.com/g/logos/RedHat_JBoss_logo.png"><br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
jbosstools-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev"
rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools & Dev Studio<br>
<a moz-do-not-send="true"
href="http://nick.divbyzero.com" target="_blank">http://nick.divbyzero.com</a><br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>