[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:
----------------------------------
[~tnolan] - Since this issue relates to the actual product UI, please assign this to the appropriate person in the UXD team.
> [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)
7 years, 6 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:
----------------------------------
The Brand team create ALL product logos for Red Hat. They post them in the PNT portal for use. This keeps product logos consistent and up-to-date.
This request will have to wait for the Brand team post the new logo for this product.
> [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)
7 years, 6 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 edited comment on JBDS-4730 at 9/20/18 9:47 AM:
-----------------------------------------------------------
[~rpdavis]
The Brand team create ALL product logos for Red Hat. They post them in the PNT portal for use. This keeps product logos consistent and up-to-date.
This request will have to wait for the Brand team post the new logo for this product.
was (Author: james.cobb):
The Brand team create ALL product logos for Red Hat. They post them in the PNT portal for use. This keeps product logos consistent and up-to-date.
This request will have to wait for the Brand team post the new logo for this product.
> [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)
7 years, 6 months
[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by Bob Davis (JIRA)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
Bob Davis edited comment on JBDS-4730 at 9/20/18 9:10 AM:
----------------------------------------------------------
Her information was out of date, [~james.cobb].
Red Hat CodeReady Studio is the name we finally settled on per the GitLab conversation.
Bob
was (Author: rpdavis):
Her information was out of date, [~james.cobb].
Red Hat Developer Studio is the name we finally settled on per the GitLab conversation.
Bob
> [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)
7 years, 6 months
[JBoss JIRA] (JBDS-4730) [Rebranding] Use "Red Hat CodeReady Studio" instead of "Red Hat Developer Studio" in graphics & text
by Bob Davis (JIRA)
[ https://issues.jboss.org/browse/JBDS-4730?page=com.atlassian.jira.plugin.... ]
Bob Davis commented on JBDS-4730:
---------------------------------
Her information was out of date, [~james.cobb].
Red Hat Developer Studio is the name we finally settled on per the GitLab conversation.
Bob
> [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)
7 years, 6 months
[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 commented on JBIDE-26379:
------------------------------------------
I think that we have to rename the packages if we move it to a different component. So we do this after the GA?
> 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)
7 years, 6 months
[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-26180:
--------------------------------
Description:
In order to start Eclipse 4.9-based builds, we need an updated target platform.
For sprint 152 / AM1: simrel M1
For sprint 153 / AM2: simrel M2
For sprint 154 / AM3: simrel M3
For sprint 155 / GA: simrel RC2/GA
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
Also:
* reddeer 2.3
* m2e http://download.eclipse.org/technology/m2e/releases/1.9/1.9.1.20180912-1601/
was:
In order to start Eclipse 4.9-based builds, we need an updated target platform.
For sprint 152 / AM1: simrel M1
For sprint 153 / AM2: simrel M2
For sprint 154 / AM3: simrel M3
For sprint 155 / GA: simrel RC2/GA
Coming in the next update, some orbit changes:
* batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
Also:
* reddeer 2.3
* m2e http://download.eclipse.org/technology/m2e/milestones/1.9/1.9.1.20180829-...
> TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)
> ----------------------------------------------------------------
>
> Key: JBIDE-26180
> URL: https://issues.jboss.org/browse/JBIDE-26180
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.9.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: releasework
> Fix For: 4.9.0.Final
>
> Attachments: am1-vs-am2.p2diff.txt, p2diff.am2.am3.all.ignoreVersions.txt, p2diff.am2.am3.all.txt
>
>
> In order to start Eclipse 4.9-based builds, we need an updated target platform.
> For sprint 152 / AM1: simrel M1
> For sprint 153 / AM2: simrel M2
> For sprint 154 / AM3: simrel M3
> For sprint 155 / GA: simrel RC2/GA
> Coming in the next update, some orbit changes:
> * batik, icu4j, platform, felix gogo, httpclient (due 27 Aug)
> Also:
> * reddeer 2.3
> * m2e http://download.eclipse.org/technology/m2e/releases/1.9/1.9.1.20180912-1601/
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months