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 > <https://issues.jalview.org/issues/?filter=10613&jql=project%20%3D%20JAL%20AND%20status%20in%20%28%22Ready%20for%20testing%22%2C%20%22Being%20tested%22%29%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: 1. merge onto your local develop 2. verify that what was tested really was passed. 3. verify that the original bug was actually addressed - not just that the tests pass. 4. Check the ant makeApplet build works locally - this usually catches package contamination issues (ant clean makeApplet to be sure). 5. if all goes well - push the merge to the build server. 6. 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 7. 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
_______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
