[jbosstools-dev] 4.3.1 code freeze and our plans for this week

Tue Mar 29 12:27:34 EDT 2016

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.

That's also why there were no task jiras sent out to remind people of the
steps needed to perform a code freeze.

On Tue, Mar 29, 2016 at 12:26 PM, Alexey Kazakov <alkazako at redhat.com>
wrote:

>
>
> On 03/29/2016 12:23 PM, Leonard Dimaggio wrote:
>
> 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?
>
>
> That's correct.
>
>
>
>
> -- Len
>
> On Tue, Mar 29, 2016 at 12:09 PM, Alexey Kazakov <alkazako at redhat.com>
> wrote:
>
>> We are not going to fix all OS/CDK current criticals/blockers targeted
>> CR1. It's just impossible. We still need to triage them. So we don't
>> expect a lot of changes this week.
>> We discussed that plan last week (which I agree may be confusing) with
>> Len. But if QE think they don't need any special build until the formal
>> code freeze this Thu because it doesn't help you then let us know.
>>
>> Thanks.
>>
>> On 03/29/2016 11:47 AM, Marian Labuda wrote:
>> > Hey,
>> >
>> > 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?
>> >
>> > --Marian
>> >
>> > ----- Original Message -----
>> > From: "Alexey Kazakov" < <alkazako at redhat.com>alkazako at redhat.com>
>> > To: jbosstools-dev at lists.jboss.org
>> > Sent: Monday, March 28, 2016 5:21:57 PM
>> > Subject: [jbosstools-dev] 4.3.1 code freeze and our plans for this week
>> >
>> > Just for the clarification. To make sure we all are on the same page.
>> >
>> > We didn't have a formal code freeze last week on March 24th as was
>> planned before. We didn't branch etc.
>> >
>> > This is what we are going to do instead:
>> >
>> > 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
>> > 2. QE can now start testing that snapshot build
>> > 3. Developers continue to work on blocker/critical 4.3.1 issues this
>> week BUT please make sure:
>> > - all PRs are properly reviewed and approved by Fred, Max or Alexey
>> before merged to 4.3.x.
>> > - all issues fixed this week have a label "reapin-a" so it will help QE
>> to see what was fixed between two builds.
>> > 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
>> > Those bits will be built from the frozen 4.3.1.x branch and will be
>> used in GA release.
>> > 5. We may build (and announce) more respins if needed.
>> > 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.
>> >
>> > Thanks.
>> >
>> >
>> > On 03/26/2016 02:11 PM, Nick Boldt wrote:
>> >
>> >
>> >
>> > As always, these are not FINAL bits, but preliminary results for QE &
>> > community testing. Not for use by customers or end users.
>> >
>> > Update site: http://download.jboss.org/jbosstools/mars/staging/updates/
>> New + noteworthy (subject to change):
>> > *
>> https://github.com/jbosstools/jbosstools-website/tree/master/documentation/whatsnew
>> * http://tools.jboss.org/documentation/whatsnew/ Schedule:
>> https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page
>> --
>> >
>> > Additional update sites:
>> > *
>> http://download.jboss.org/jbosstools/mars/staging/updates/core/4.3.1.CR1/
>> *
>> http://download.jboss.org/jbosstools/mars/staging/updates/coretests/4.3.1.CR1/
>> Target platforms:
>> > *
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.50.2.CR1-SNAPSHOT
>> *
>> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.52.0.CR1-SNAPSHOT
>> Discovery sites:
>> > *
>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.central/4.3.1.CR1/
>> *
>> http://download.jboss.org/jbosstools/mars/staging/updates/discovery.earlyaccess/4.3.1.CR1/
>> Build folders (for build logs & update site zips):
>> > * http://download.jboss.org/jbosstools/mars/staging/builds/
>> >
>> >
>> > _______________________________________________
>> > jbosstools-dev mailing list
>> > jbosstools-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>
>
>
> --
> Len DiMaggio (ldimaggi at redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886  USA
> tel:  978.392.3179
> cell: 781.472.9912
> http://www.redhat.com
> http://community.jboss.org/people/ldimaggio
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20160329/96902a8f/attachment.html 