[JBoss JIRA] (JBIDE-22187) Duplicate Openshift connections
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22187:
-----------------------------------
Assignee: Andre Dietisheim
> Duplicate Openshift connections
> -------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22187) Duplicate Openshift connections
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22187:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Duplicate Openshift connections
> -------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Fix For: 4.4.0.Alpha1
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TOOLSDOC-729) JBDS 9.1 GA: Release Notes
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-729?page=com.atlassian.jira.plug... ]
Martin Malina commented on TOOLSDOC-729:
----------------------------------------
[~mhusnain], some notes:
2. About this Release
JBoss Developer Studio 9.1 Beta2 is an upgrade of JBoss Developer Studio 9.0.
- update to GA
It now requires a minimum of Java 8 to run.
- this is nothing new, so I would remove the word "now"
3. New Features and Enhancements
- you shouldn't have sections about beta1 and beta2, but instead have an overall list of n&n. The main reason is that users of JBDS 9.1.0.GA shouldn't have to know about Beta releases at all.
That's how the N&N should work also - for 4.3.1.Final, it should show an aggregation of Beta1, Beta2 and CR1: http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.1.Final.html
But not everything is there yet. Alexey clarified this for me:
{quote}
you will see the *.final N&N but you won't see the aggregation of all N&Ns until we "release" .Final version in product.yaml
{quote}
The aggregation is optional per item - for example in beta, forge runtime was update to 3.0.0.Beta3. But for GA, it was updated to a newer version still, so you only want to mention the final update.
BTW, wouldn't it make more sense to just link to the N&N at tools.jboss.org rather than copy and paste everything into the release notes doc?
4.1. Resolved Issues
You only list issues with fix version 9.1.0.GA or 4.3.1.Final. That will show a very minimal set of JIRA. Not exactly what we want. A good starting point for preparing a GA Release Notes document is to look at previous releases. This is what we had for 9.0.0.GA:
{code}
(project in (JBDS) AND affectedVersion < 9.0.0.Alpha1 AND fixVersion in (9.0.0.Alpha1, 9.0.0.Alpha2, 9.0.0.Beta1, 9.0.0.Beta2, 9.0.0.CR1, 9.0.0.CR2, 9.0.0.GA) OR project in (JBIDE) AND affectedVersion < 4.3.0.Alpha1 AND fixVersion in (4.3.0.Alpha1, 4.3.0.Alpha2, 4.3.0.Beta1, 4.3.0.Beta2, 4.3.0.Final)) AND type in (Bug) AND resolution in (Done)
{code}
Now, if I remember correctly, we decided to drop the affectedVersion from the query. But the fix versions should still list everything 9.1.0.x.
5. Apply this Release
JBoss Developer Studio 9.1 Beta2 is available from a number of sources:
- update to GA, also the next line
> JBDS 9.1 GA: Release Notes
> --------------------------
>
> Key: TOOLSDOC-729
> URL: https://issues.jboss.org/browse/TOOLSDOC-729
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Reporter: Misha Ali
> Assignee: Misha Ali
>
> Create release notes for GA
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years