[jbosstools-issues] [JBoss JIRA] (JBDS-4362) Consider eliminating the devstudio EAP installer bundle?

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-4362 at 4/27/17 9:21 AM:
-----------------------------------------------------------

Thanks, Jeff. The only projects in the github jbdevstudio org that's not already public are:

* https://github.com/jbdevstudio/jbdevstudio-artwork - branding & artwork used in the installer. No real reason to keep it private other than "because we do". Same images are also in jbdevstudio-product repo, which is public.
* https://github.com/jbdevstudio/jbdevstudio-qa - QE tests - could maybe be public if we wanted (I'm not sure if there's anything in there that contains internal infrastructure details)
* https://github.com/jbdevstudio/jbdevstudio-ci - Jenkins job configs (contains internal infrastructure details so should remain private)

So... as to the SOURCES for devstudio ... at this point it's all public and open source. 

Dropping the EAP bundle of devstudio means everything we *BUILD* is also public & open source, as there's no EAP license requirement. 



> Consider eliminating the devstudio EAP installer bundle?
> --------------------------------------------------------
>
>                 Key: JBDS-4362
>                 URL: https://issues.jboss.org/browse/JBDS-4362
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: installer, integration-platform
>    Affects Versions: 10.4.0.AM3
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 11.0.0.AM1
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server. 
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely? 
> That way only the devSUITE installer would include EAP.



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