···
From: jalview-dev-bounces@jalview.org jalview-dev-bounces@jalview.org on behalf of Mungo Carstairs (Staff) g.m.carstairs@dundee.ac.uk
Sent: 15 June 2017 14:47:22
To: Jalview Development List
Subject: Re: [Jalview-dev] Issues pending for 2.10.2
Updates as at Thursday afternoon UK time.
https://issues.jalview.org/browse/JAL-2563?filter=10613&jql=project%20%3D%20JAL%20AND%20status%20in%20(%22In%20Progress%22%2C%20%22Ready%20for%20testing%22%2C%20%22Being%20tested%22)%20AND%20fixVersion%20%3D%202.10.2%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC%2C%20key%20DESC%2C%20fixVersion%20ASC%2C%20assignee%20DESC%2C%20createdDate%20DESC
All branches merged to develop:
- JAL-1648,JAL-2386 (includes JAL-2570), JAL-2589, JAL-2591, JAL-2594
Functional tests all passing except for CrossRefTest (expected).
Ant build makeapplet successful locally, build successful on build server, applet launched ok from server.
Being tested
- JAL-2034 Overview Window refresh for selection, JAL-2563 show ‘B’ position in status bar
- assigned to Jim, on develop - ready to sign off?
Ready for test
- JAL-2295/6 Chimera feature exchange - 3 Unresolved comments in Review
- JAL-2429 findColumnPosition and hidden columns - can you sign this off Jim?
In Progress Blockers:
- JAL-2116 Java 9 testing - with Jim?
- JAL-2321 drop pdb structure on sequence - no progress, bump?
- JAL-2597 missing inserts - can’t reproduce
Release notes:
-
Don’t seem to include issues ‘Being Tested’ other than JAL-2563 show ambiguous residue in status bar, experimental Chimera features
-
Is this still in progress? I didn’t find
- JAL-2379 (>30x speed and memory improvement for large PCA)
- JAL-1632 (new Tree/PCA dialog)
- JAL-2435 option to mirror fonts in split screen
- JAL-2416 ability to drag a score matrix onto an alignment
- JAL-2589 overview (with features) custom gap colour
- and a few other (even) more obscure bug fixes
Mungo
The University of Dundee is a registered Scottish Charity, No: SC015096
The University of Dundee is a registered Scottish Charity, No: SC015096
Mungo Carstairs
Jalview Computational Scientist
The Barton Group
Division of Computational Biology
School of Life Sciences
University of Dundee, Dundee, Scotland, UK
www.jalview.org
www.compbio.dundee.ac.uk
g.m.carstairs@dundee.ac.uk
We’re Scottish University of the Year again!
The Times / Sunday Times Good University Guide 2016 and 2017
From: jalview-dev-bounces@jalview.org jalview-dev-bounces@jalview.org on behalf of Jim Procter jprocter@compbio.dundee.ac.uk
Sent: 14 June 2017 13:57:14
To: Jalview Development List
Subject: Re: [Jalview-dev] Issues pending for 2.10.2
All slated for 2.10.2 must be merged. Blockers affecting 2.10.2 need to be fixed too.
On 12/06/2017 18:51, Mungo Carstairs (Staff) wrote:
A quick review of Being Tested or Ready for Test for 2.10.2, in case any are considered critical and missing from the release candidate.
https://issues.jalview.org/issues/?filter=10613&jql=project%20%3D%20JAL%20AND%20status%20in%20(%22Ready%20for%20testing%22%2C%20%22Being%20tested%22)%20AND%20fixVersion%20%3D%202.10.2%20ORDER%20BY%20key%20ASC%2C%20fixVersion%20ASC%2C%20status%20DESC%2C%20assignee%20DESC%2C%20createdDate%20DESC
On develop (I think)
JAL-2034 overview updates for selection
JAL-2295/6 Chimera-Jalview features exchange (need EXPERIMENTAL=true in Preferences file)
JAL-2429 findColumnPosition and hidden columns
JAL-2551 group colour on resize
JAL-2563 show ‘B’ in status bar
JAL-2577 hide columns by annotation threshold in split frame
Are these noted in the release notes ? Nothing that hasn’t already been tested should be.
On a branch
JAL-1648 remember free text queries
JAL-2386, JAL-2570 (group colour schemes) - both fixes on bug/JAL-2386
JAL-2589 render custom gap colour - on bug/JAL-2589 branch
JAL-2591 race condition in overview window - bug/JAL-2591
JAL-2594 stack trace creating feature on gapped region (no user impact)
Procedure for merging is:
- merge onto your local develop
- verify that what was tested really was passed.
- verify that the original bug was actually addressed - not just that the tests pass.
- Check the ant makeApplet build works locally - this usually catches package contamination issues (ant clean makeApplet to be sure).
- if all goes well - push the merge to the build server.
- Check the build really works again. If it was broken then you need to fix on the branch - since the commits are now public, they can’t be taken back. If all good, issue can be resolved
- resolved issues should then go into release notes. the message needs to be sanitized so it is comprehensible to an end user - issues often need to be merged. commits to the release notes go under the issue for doing the release: JAL-2418.
We are doing a Jalview demo tomorrow - would be nice if the RC is functional !
Jim