[jbosstools-issues] [JBoss JIRA] (JBIDE-22105) Update AERI Server to 2.0

[Marcel Bruch (JIRA)]

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

Marcel Bruch commented on JBIDE-22105:
--------------------------------------

No documentation why. It's a tradeoff decision. At the end it boils down to the question which skill set is available in your team.

> Update AERI Server to 2.0
> -------------------------
>
>                 Key: JBIDE-22105
>                 URL: https://issues.jboss.org/browse/JBIDE-22105
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: aeri
>            Reporter: Marcel Bruch
>            Priority: Minor
>
> I'd like to roll out an update of the aeri server. 
> Notable changes on for Eclipse clients:
> This update changes the sever responses send back to clients on submission of a problem report. The response format is compatible with the Eclipse AERI integration 1.100+
> No breaking changes.
> Most notable changes on the server's web-site:
> * The UI changed from AngularJS to Vaadin 
> * Improved JIRA integration.
> * Improved customization of email digests and bug creation templates
> * Fine-grained control over server-responses
> * Auto-Actions for automated problem state transitions on problem state changes (e.g., _number-of-reporters > 100 && status=open --> Set Severity to major._ or _If new error reports arrived in with bundle.version > 1.2.3 --> set status=reopen.
> Details will be announced separately.
> In this bug I'm looking for a process *how* to perform an server-update for JBoss Tools.
> I'd like to know who needs to be involved in case of major/minor updates? Is some testing / approval from QE required before an update can go live?
> My proposed way of doing a major update:
> * Copy the current database.
> * Set up a sandbox instance running on the copied database
> * Create a JIRA issue for the planned update.
> * After approval by QE switch testing instance to production
> FWIW, I don't plan to announce minor bugfixes and minor improvements (e.g., to duplicate detection) as long as they do have user-observable impact or lead to significant changes in the UI and workflows.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)