[jbosstools-issues] [JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

[Misha Ali (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13316009#comment-13316009 ] 

Misha Ali commented on JBIDE-23213:
-----------------------------------

[~mmalina], we can update it pretty much up to the GA date before we release the docs. cc: [~supriya.bharadwaj]

> Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23213
>                 URL: https://issues.jboss.org/browse/JBIDE-23213
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.4.1.Final
>            Reporter: Nick Boldt
>            Assignee: Martin Malina
>             Fix For: 4.4.2.AM3
>
>
> It's time to review the available platforms on which we test devstudio / jbt.
> Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016.
> [0] https://wiki.ubuntu.com/Releases
> * Should we move to 16.04.1 LTS and 16.10?
> * Should we move to 14.04.5 LTS and 16.04.1 LTS ?
> * Should we move to 14.04.5 LTS and 16.10?
> Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1].
> [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/10.1/paged/components-and-supported-configurations/chapter-5-jboss-developer-studio-100-101
> But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right?
> [2] https://fedoraproject.org/wiki/Releases/25/Schedule
> * Should we move to F24 and F25?



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)