On Tue, Nov 28, 2017 at 7:03 PM, Mike Jumper <[email protected]> wrote:
> On Tue, Nov 28, 2017 at 1:46 PM, Nick Couchman <[email protected]> wrote: > >> On Tue, Nov 28, 2017 at 1:18 PM, Mike Jumper <[email protected]> >> wrote: >> >> > On Tue, Nov 28, 2017 at 10:12 AM, Nick Couchman <[email protected]> >> wrote: >> > >> > > ... >> > > >> > > It seems preferable to wait and see if they can get it done. I can >> jump >> > in >> > > the INFRA HipChat room and ping them about it if that would help - >> I've >> > > been in there a few times before just to see what goes on in that >> room, >> > and >> > > it seems like they have people in there periodically asking about >> stuff >> > > like that. I'm not sure if there's a specific protocol for that or >> > not... >> > > >> > > >> > Sure, that sounds like good idea. Maybe that will get things moving >> forward >> > (or at least give us an idea of where things stand). >> > >> > - Mike >> > >> >> Chatted with them real quick - Daniel (@pono) said they are running behind >> on TLD graduation tasks, and they expect to clear out the backlog this >> week. >> >> -Nick >> > > It looks like most of the graduation tasks have now been completed, > including the repository rename. Things definitely got moving quickly. > > IMPORTANT: The links for some release downloads, mainly checksums, are now > broken. This is due to the dist area rename from "incubator/guacamole/" to > "guacamole/". I've opened a pull request to correct this: > > https://github.com/apache/guacamole-website/pull/51 > > When anyone gets a chance, please review - things are slightly broken > until then. > > Things look in order now. Everything has been renamed, and the GitHub mirrors have been resynced so that the branch renames have taken effect, too. Beware that: 1) Everyone with currently cloned copies of the repository will need to update their remotes accordingly, removing the "incubator-" prefix, or pushing and fetching will not work. 2) Anyone with outstanding pull requests against "staging/0.9.14-incubating" branches probably just had their PR automatically closed once the branch was deleted. If GitHub allows you to edit the PR to change the merge base to "staging/0.9.14" and reopen, please do so. If not, you'll need to simply create a new PR with the same changes but against "staging/0.9.14". - Mike
