On Sat, Sep 5, 2020 at 5:01 PM Mike Jumper <[email protected]> wrote:

> Hello all,
>
> Per release procedures [1], I'd like to get the discussion going on the
> 1.3.0 release scope, so that maybe we can aim to get back into a quicker
> release rhythm (perhaps aiming for mid-September?).
>
>
Sounds good to me.


> The following have already been completed, merged, etc.:
>
> GUACAMOLE-753 - Add TOTP auth method to start.sh for Docker image
> GUACAMOLE-819 - Documented Duo secret key length is incorrect
> GUACAMOLE-919 - An I/O error occurred while sending to the backend
> GUACAMOLE-942 - Query may fail if all connections disconnect while listing
> active connections
> GUACAMOLE-949 - Remove unused UNIX_TIME macro
> GUACAMOLE-980 - used tomcat-jre8 Docker-Image seems to be deprecated
> GUACAMOLE-982 - Typo mistake : incorrect the error log message of RDP
> GUACAMOLE-987 - ldap-user-attributes is not set via an env variable
> GUACAMOLE-1001 - RADIUS Extension Needs Additional Attributes
> GUACAMOLE-1054 - Improve Russian translation
> GUACAMOLE-1082 - Add guacamole-auth-cas to docker Script
> GUACAMOLE-1103 - Typo mistake : the incorrect comment of a variable for the
> RDP setting
> GUACAMOLE-1107 - "allowed-languages" property incorrectly documented as
> "available-languages"
> GUACAMOLE-1110 - Size and security improvements for Docker images
> GUACAMOLE-1114 - Problem that the guacamole server doesn't destroy some
> thread mutexes
> GUACAMOLE-1120 - CAS module causes app.js download errors
> GUACAMOLE-1122 - Fail in compile of RDP protocol when SSH is unavailable
> GUACAMOLE-1125 - Ctrl+Alt+End(Supr) only working once
> GUACAMOLE-1135 - MySQL SSL - Trust Store Paths Expecting URI
> GUACAMOLE-1136 - MySQL SSL Client Cert Environment Variables Return Trust
> Store
> GUACAMOLE-1147 - Add support for additional LDAP properties in Docker
> GUACAMOLE-1149 - Login using LDAP fails internally if TOTP is used without
> automatic user creation
> GUACAMOLE-1150 - Connection group permissions aren't checked correctly
> GUACAMOLE-1151 - Add nbproject directory to .gitignore file
> GUACAMOLE-1152 - Enabling skip-if-unavailable breaks expired password
> change
> GUACAMOLE-1158 - RDP "disable-copy" flag does not work
>
>
That's a pretty healthy list for three-ish months work!


> The following are in-progress with some changes already merged:
>
> GUACAMOLE-221 - Parameter prompting within client interface
> GUACAMOLE-857 - Add Docker Image Support for HTTP Header-Based
> Authentication
> GUACAMOLE-1081 - option to convert usernames to all lowercase
> GUACAMOLE-1123 - Standardize on filtered history query for user and
> connection management
>
>
My only question, here, would be on timing of creating the staging/1.3.0
branch - do we try to finish the merge of these into master prior to doing
the staging change, or does it matter that much?


> The following are in-progress, already marked for 1.3.0, and have
> corresponding outstanding PRs:
>
> GUACAMOLE-760 - add timezone info using DB Connection string
> GUACAMOLE-793 - CAS Provider returns Group - like LDAP Provider
> GUACAMOLE-903 - Improved Chinese internationalization support
> GUACAMOLE-1031 - SFTP upload directory ignored
> GUACAMOLE-1078 - Add Catalan Language to Guacamole
>
> Thoughts?
>
>
My only other thought is maybe to add in any that are verified to be
regressions or bugs from 1.1.0 and 1.2.0. At a glance I see the following
potential candidates:

https://issues.apache.org/jira/browse/GUACAMOLE-1113
https://issues.apache.org/jira/browse/GUACAMOLE-1038
https://issues.apache.org/jira/browse/GUACAMOLE-912
https://issues.apache.org/jira/browse/GUACAMOLE-1140
https://issues.apache.org/jira/browse/GUACAMOLE-1146
https://issues.apache.org/jira/browse/GUACAMOLE-1138
https://issues.apache.org/jira/browse/GUACAMOLE-1129
https://issues.apache.org/jira/browse/GUACAMOLE-1133
https://issues.apache.org/jira/browse/GUACAMOLE-1021

I'm not saying all of these *have* to be included in the 1.3.0 release, but
if everyone can jump in and do a little work to verify whether or not these
are actually valid issues/bugs, and maybe knock out a few here and there,
we could add a few bug fixes to the list.

-Nick

Reply via email to