July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24674) update the list of nag emails to send on QE stage day

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24674: ------------------------------------ First step: creation of a script to automatically move issues from one fixversion/sprint to another: https://github.com/jbosstools/jbosstools-build-ci/pull/167 https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/checkU... Sample usage: {code} python -W ignore ./checkUnresolvedIssues.py --jira https://issues.stage.jboss.org --jirauser ME --jirapwd SECRET --jbt 4.5.0.AM2 --jbt_NEXT 4.5.0.Final --ds 11.0.0.AM2 --ds_NEXT 11.0.0.GA --sprint "devex #134 Jun 2017" --sprint_NEXT "devex #135 July 2017"{code} For more output, can use -X for debug, -S to skip validation of the fixversions before proceeding, and -A to make changes non-interactively. For a future milestone, we can then wrap a Jenkins job around this and have the unresolved JIRAs moved automatically. [~jeffmaury] can you review the queries I'm using to find issues to move? > update the list of nag emails to send on QE stage day > ----------------------------------------------------- > > Key: JBIDE-24674 > URL: https://issues.jboss.org/browse/JBIDE-24674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. > We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. > And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24674) update the list of nag emails to send on QE stage day

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24674 at 7/21/17 5:42 PM: ------------------------------------------------------------- First step: creation of a script to automatically move issues from one fixversion/sprint to another: https://github.com/jbosstools/jbosstools-build-ci/pull/167 https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/checkU... Sample usage: {code} python -W ignore ./checkUnresolvedIssues.py \ --jira https://issues.stage.jboss.org --jirauser ME --jirapwd SECRET \ --jbt 4.5.0.AM2 --jbt_NEXT 4.5.0.Final \ --ds 11.0.0.AM2 --ds_NEXT 11.0.0.GA \ --sprint "devex #134 Jun 2017" --sprint_NEXT "devex #135 July 2017"{code} For more output, can use -X for debug, -S to skip validation of the fixversions before proceeding, and -A to make changes non-interactively. For a future milestone, we can then wrap a Jenkins job around this and have the unresolved JIRAs moved automatically. [~jeffmaury] can you review the queries I'm using to find issues to move? was (Author: nickboldt): First step: creation of a script to automatically move issues from one fixversion/sprint to another: https://github.com/jbosstools/jbosstools-build-ci/pull/167 https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/checkU... Sample usage: {code} python -W ignore ./checkUnresolvedIssues.py --jira https://issues.stage.jboss.org --jirauser ME --jirapwd SECRET --jbt 4.5.0.AM2 --jbt_NEXT 4.5.0.Final --ds 11.0.0.AM2 --ds_NEXT 11.0.0.GA --sprint "devex #134 Jun 2017" --sprint_NEXT "devex #135 July 2017"{code} For more output, can use -X for debug, -S to skip validation of the fixversions before proceeding, and -A to make changes non-interactively. For a future milestone, we can then wrap a Jenkins job around this and have the unresolved JIRAs moved automatically. [~jeffmaury] can you review the queries I'm using to find issues to move? > update the list of nag emails to send on QE stage day > ----------------------------------------------------- > > Key: JBIDE-24674 > URL: https://issues.jboss.org/browse/JBIDE-24674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. > We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. > And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4412) DevSuite 1.4 Installer Make progress/status clearer/easier to see

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4412?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4412: -------------------------------- Fix Version/s: 11.0.0.GA > DevSuite 1.4 Installer Make progress/status clearer/easier to see > ----------------------------------------------------------------- > > Key: JBDS-4412 > URL: https://issues.jboss.org/browse/JBDS-4412 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 11.0.0.GA > > > The overall installation progress for DevSuite 1.4 is difficult to see. You've got to scroll back and forth through the boxes to look for the small text that indicates what's going on. > Suggestions: > # There should be an overall progress at the top > # There should be some indication it is still working > # the status text in the boxes is the same color and size as the version number and other comment text making it difficult to pick out. It's easy to miss that there is status text and that it is being updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4406) DevSuite 1.4 Installer should indicate choose 1 hypervisor

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4406?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4406: -------------------------------- Fix Version/s: 11.0.0.GA > DevSuite 1.4 Installer should indicate choose 1 hypervisor > ---------------------------------------------------------- > > Key: JBDS-4406 > URL: https://issues.jboss.org/browse/JBDS-4406 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Priority: Minor > Labels: ui > Fix For: 11.0.0.GA > > > The installer (on Windows) should indicate that only one hypervisor, Hyper-V OR Virtualbox, is needed. A user could get the wrong impression that both are needed. > In my case, it selected to install VirtualBox because Hyper-V was present but not enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4406) DevSuite 1.4 Installer should indicate choose 1 hypervisor

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4406?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4406: ----------------------------------- Assignee: Denis Golovin > DevSuite 1.4 Installer should indicate choose 1 hypervisor > ---------------------------------------------------------- > > Key: JBDS-4406 > URL: https://issues.jboss.org/browse/JBDS-4406 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: DevSuite 1.4 installer, Windows 10 Pro/64 > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 11.0.0.GA > > > The installer (on Windows) should indicate that only one hypervisor, Hyper-V OR Virtualbox, is needed. A user could get the wrong impression that both are needed. > In my case, it selected to install VirtualBox because Hyper-V was present but not enabled. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1145) Set the SwitchYard Tooling as deprecated

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1145?page=com.atlassian.jira.plugin... ] Brian Fitzpatrick commented on JBTIS-1145: ------------------------------------------ Went ahead and merged the tooling change for the update site as well. > Set the SwitchYard Tooling as deprecated > ---------------------------------------- > > Key: JBTIS-1145 > URL: https://issues.jboss.org/browse/JBTIS-1145 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 11.0.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.5.0.CR2, 11.0.0.CR2 > > Attachments: devstudiois_deprecate_sy.png, devstudiois_deprecate_sy2.png, index-with-deprecation.png > > > Set the SwitchYard Tooling as deprecated > * in standalone installer > * in update site -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24737) [jeetools] Merge jeetools and ejbtools

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24737?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24737: -------------------------------- Summary: [jeetools] Merge jeetools and ejbtools (was: Merge jeetools and ejbtools) > [jeetools] Merge jeetools and ejbtools > -------------------------------------- > > Key: JBIDE-24737 > URL: https://issues.jboss.org/browse/JBIDE-24737 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream > Reporter: Rob Stryker > > jeetools and servertools have extensive interconnections on a plugin level. These two should be merged. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4479) DevSuite Installer: Update CDK to 3.1.0.CR1 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4479?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4479: ------------------------------------- Verified on latest build, installation works for me. > DevSuite Installer: Update CDK to 3.1.0.CR1 release > --------------------------------------------------- > > Key: JBDS-4479 > URL: https://issues.jboss.org/browse/JBDS-4479 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.0.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4479) DevSuite Installer: Update CDK to 3.1.0.CR1 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4479?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4479: ----------------------------------- Assignee: Denis Golovin (was: Sudhir Verma) > DevSuite Installer: Update CDK to 3.1.0.CR1 release > --------------------------------------------------- > > Key: JBDS-4479 > URL: https://issues.jboss.org/browse/JBDS-4479 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4479) DevSuite Installer: Update CDK to 3.1.0.CR1 release

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4479?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4479: ----------------------------------- Assignee: Sudhir Verma (was: Denis Golovin) > DevSuite Installer: Update CDK to 3.1.0.CR1 release > --------------------------------------------------- > > Key: JBDS-4479 > URL: https://issues.jboss.org/browse/JBDS-4479 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Denis Golovin > Assignee: Sudhir Verma > Fix For: 11.0.0.GA > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2017