On Fri, Feb 10, 2017 at 11:32 AM, Mike Jumper <[email protected]> wrote:
> Hello all, > > With quite a lot of coding merged since 0.9.11, I'd like to begin the > discussion of scope for 0.9.12. Issues currently tagged for 0.9.12 can be > found here: > > https://issues.apache.org/jira/issues/?jql=project%20% > 3D%20Guacamole%20AND%20fixVersion%20%3D%200.9.12-incubating > > The code already merged for 0.9.12 currently amounts to roughly 10-15K > lines of changes. > > Currently underway on my end are a fix for RDP printing (connections can > hang if GhostScript blocks) and support for per-connection guacd's: > > https://issues.apache.org/jira/browse/GUACAMOLE-189 > https://issues.apache.org/jira/browse/GUACAMOLE-200 > > In the interest of keeping scope minimal, I assume we probably don't want > to go forward with the great merge of the experimental X.Org driver yet > (which no doubt needs cleanup anyway). Similarly, the several > authentication extensions under review from Nick should be after-0.9.12, > IMHO, again for sake of scope. > > Beyond the above, I'm not aware of any issues which should block release, > but I'm ready to be wrong on this. > > Thoughts? > > Thanks, > > - Mike > > The "staging/0.9.12-incubating" branches have now been created for incubator-guacamole-client, incubator-guacamole-server, and incubator-guacamole-manual: https://git1-us-west.apache.org/repos/asf?p=incubator-guacamole-client.git;a=shortlog;h=refs/heads/staging/0.9.12-incubating https://git1-us-west.apache.org/repos/asf?p=incubator-guacamole-server.git;a=shortlog;h=refs/heads/staging/0.9.12-incubating https://git1-us-west.apache.org/repos/asf?p=incubator-guacamole-manual.git;a=shortlog;h=refs/heads/staging/0.9.12-incubating Unfortunately, the branches haven't yet shown up in the GitHub mirrors, and incubator-guacamole-server has yet to reflect the past deletion of "staging/0.9.11-incubating". If the branches don't appear on their own in the next day or so, I'll ping Infra... based on past issues with the automated sync to GitHub [1] [2] [3], I would bet a manual resync is needed. - Mike [1] https://issues.apache.org/jira/browse/INFRA-12699 [2] https://issues.apache.org/jira/browse/INFRA-13229 [3] https://issues.apache.org/jira/browse/INFRA-13293
