[JBoss JIRA] (JBIDE-26379) Launcher: should be moved from base to central
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26379?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26379:
-------------------------------------
Labels: launcher_wizard (was: )
> Launcher: should be moved from base to central
> ----------------------------------------------
>
> Key: JBIDE-26379
> URL: https://issues.jboss.org/browse/JBIDE-26379
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, common
> Affects Versions: 4.9.0.AM3
> Reporter: Andre Dietisheim
> Labels: launcher_wizard
>
> as discussed in https://github.com/jbosstools/jbosstools-base/pull/631#issuecomment-42109...
> {quote}
> This should all live in central, and it shouldn't really be added to the common.all feature if we intend to simply move it later.
> Give it it's own feature, add it to the master list of features added to the project, and then later move it to the central repo.
> I personally believe a rename-and-move is just fine even before a Final. Keeping it where it is through a final actually is what's harder to change. Then it becomes a sort of API that the common.all feature contains this launcher, and later it won't.
> {quote}
> we should move the launcher from jbosstools-base to jbosstools-central
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months
[JBoss JIRA] (JBIDE-26379) Launcher: should be moved from base to central
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-26379:
----------------------------------------
Summary: Launcher: should be moved from base to central
Key: JBIDE-26379
URL: https://issues.jboss.org/browse/JBIDE-26379
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, common
Affects Versions: 4.9.0.AM3
Reporter: Andre Dietisheim
as discussed in https://github.com/jbosstools/jbosstools-base/pull/631#issuecomment-42109...
{quote}
This should all live in central, and it shouldn't really be added to the common.all feature if we intend to simply move it later.
Give it it's own feature, add it to the master list of features added to the project, and then later move it to the central repo.
I personally believe a rename-and-move is just fine even before a Final. Keeping it where it is through a final actually is what's harder to change. Then it becomes a sort of API that the common.all feature contains this launcher, and later it won't.
{quote}
we should move the launcher from jbosstools-base to jbosstools-central
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months
[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by James Cobb (JIRA)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
James Cobb commented on JBDS-4730:
----------------------------------
[~jeffmaury] [~nickboldt] -
There seems to be a disconnect between what Jessica Burkitt in Brand emailed me (what I posted above) and where the conversation in gitlab is doing.
I'm staying out of that conversation.
> [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4730
> URL: https://issues.jboss.org/browse/JBDS-4730
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: build, installer
> Affects Versions: 12.9.0.AM3
> Reporter: Nick Boldt
> Assignee: James Cobb
> Priority: Blocker
> Fix For: 12.10.0.AM1
>
>
> Branding has requested that we rename devstudio from "Red Hat Developer Studio" to "Red Hat CodeReady Studio".
> As we did recently in JBDS-4706, we'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/
> We'll need this rebrand done for the upcoming December release. All changes need to be done by November 6 so they can be included in the AM1 feature complete release on Nov 13, in support of the docs team, updating screenshots, install instructions, etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
5 years, 9 months