[WG: Sakai QA] [Building Sakai] [DG: Teaching & Learning] Upgrade: Jira 4.2.2->4.4 and Confluence 3.4.6->4.1 (30/31 March 2012)

[Matthew Jones]

FYI: The main push for the upgrade *now* is mostly because the CLE release
team was discussing changing the workflow to better aide QA in testing the
release. I'd noticed that the newer version of Jira had really nice
workflow visualization tools which should make it clearer what how this new
workflow is intended to work, rather than us having to write tons of text
about it that people would consider too long and won't read.

There appeared to be a lot of other useful additions that had little impact
to the user overall use experience. I did see that jira 5.X is available,
but if anyone remembers 3.X->4.X, this took some getting used to, so it
seemed like a smaller step at this point to get what we needed was bigger
than a giant leap which might confuse everyone. Since we were in active QA
and bug resoltion for the 2.9 cycle, it seemed like it would be
less disruptive to wait a few months and see how the minor upgrade went?

On Tue, Mar 27, 2012 at 5:01 AM, Adam Marshall
<adam.marshall at oucs.ox.ac.uk>wrote:

> Why not move to jira 5 whilst you're at it? It has social networking
> features and allows you to link to remote Jiras.
>
> This latter feature would be particularly useful for us as we run our own
> jira and we spend a lot of time linking from our Jira to the SAK jira.
>
> adam
>
> > -----Original Message-----
> > From: pedagogy-bounces at collab.sakaiproject.org [mailto:pedagogy-
> > bounces at collab.sakaiproject.org] On Behalf Of Anthony Whyte
> > Sent: 27 March 2012 00:59
> > To: Developers Sakai-Dev; Sakai QA; pedagogy at collab.sakaiproject.org;
> oae-
> > dev OAE; production oae
> > Subject: [DG: Teaching & Learning] Upgrade: Jira 4.2.2->4.4 and
> Confluence
> > 3.4.6->4.1 (30/31 March 2012)
> >
> > Members of the CLE team have requested that we upgrade the Community
> > Jira instance from 4.2 to 4.4 in order to leverage a variety of
> improvements
> > including a visual workflow designer.  In order to perform the Jira
> upgrade we
> > will also need to upgrade Confluence from version 3.4.6 to 4.1 since
> changes
> > to Jira's user database requires Confluence 4.1 or greater in order to
> support
> > user delegation.  The upgrade is tentatively scheduled for this Friday,
> 10 PM
> > PDT.  The maintenance window is between 2-4 hours.
> >
> > Jira 4.4=Visual Workflow Designer, a Workflow Viewer from the 'View
> Issue'
> > page, simplified Administration and user-specific Time Zones. We are also
> > very pleased to announce that the JIRA installation and upgrade processes
> > have been improved and largely automated, etc [1].
> >
> > Confluence 4.1=Autoconvert feature, new image effects, find and replace,
> > new icons, improved translation features and global PDF stylesheets, etc
> [2].
> >
> > If you object to either the timing or the upgrade itself please reply on
> list.
> >
> > Cheers,
> >
> > Anthony
> >
> > _____________________
> >
> > [1] Jira 4.4 release notes:
> > http://confluence.atlassian.com/display/JIRA/JIRA+4.4+Release+Notes
> > [2] Confluence 4.1 release notes:
> > http://confluence.atlassian.com/display/DOC/Confluence+4.1+Release+Not
> > es
> >
> >
> >
> >
> >
> > _______________________________________________
> > pedagogy mailing list
> > pedagogy at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/pedagogy
> >
> > TO UNSUBSCRIBE: send email to pedagogy-
> > unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20120327/149d40b5/attachment.html