On Sat, Sep 5, 2020 at 6:20 PM Nick Couchman <[email protected]> wrote:
> ... > > 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? > It shouldn't matter. As long as we consistently merge "staging/1.3.0" back to master, things will be correct and the content of the 1.3.0 release will be safely isolated to only those changes intended for 1.3.0. ... > > 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. Sure, I'll go through the above momentarily. - Mike
