[JBoss JIRA] (JBIDE-24447) Look for minishift configuration in MINISHIFT_HOME
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24447:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = 4.5.x
> Look for minishift configuration in MINISHIFT_HOME
> --------------------------------------------------
>
> Key: JBIDE-24447
> URL: https://issues.jboss.org/browse/JBIDE-24447
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection
> Affects Versions: 4.4.4.Final
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
> Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
>
>
> One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else than in ~/.minishift
> It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24674) automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24674:
-------------------------------
Summary: automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation (was: automatically punt unresolved issues to .x or the next sprint)
> automatically punt unresolved issues to .x or the next sprint; send reminder emails about sprint creation
> ---------------------------------------------------------------------------------------------------------
>
> 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
> Labels: releasework
> Fix For: 4.5.1.AM1
>
>
> 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, 7 months