[JBoss JIRA] (JBIDE-16657) handle the case where development = stable
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16657?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16657:
----------------------------------------
Sprint: Sprint to 31.03.14
> handle the case where development = stable
> -------------------------------------------
>
> Key: JBIDE-16657
> URL: https://issues.jboss.org/browse/JBIDE-16657
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Fix For: 4.2.0.Beta1
>
>
> once we release Final, the development updatesite actually contains final and not the latest CR1 so there is a mismatch between website and reality ;)
> Suggestion:
> Add "marker" to latest_development in products.yml that will add an alert
> to the latest active development download that the updatesite actually has stable.
> actualcontent: 4.1.0.Final
> Would give something like:
> Info: 4.1.0.Final have been released and is what you will get when installing from the development update site.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Martin Malina closed JBDS-2862.
-------------------------------
OK, it works as you describe. It's not pretty, but it seems we cannot do anything here. Closing. Verified in JBDS 7.1.1.CR1 B672
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.CR1
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install JBDS.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-12355.
---------------------------------------
Resolution: Done
major website redesign is done and on staging.
I've converted remaining subtasks to full issues and added them to JBIDE-16580 epic (board: https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=641&view=planni...)
> JBoss tools website redesign
> ----------------------------
>
> Key: JBIDE-12355
> URL: https://issues.jboss.org/browse/JBIDE-12355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta1
>
> Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
> etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
> http://tools-stg.jboss.org/ <-- current staged version
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month