Am 29.06.2014 19:12, schrieb Michael DePaulo: >> Let's get X2Go Client released by the end of the week. If the issue > gets solve by then, fine. If not, then we get a 4.0.2.2 released as soon > as this is fixed. > > Ok, let's do that.
Thank you, guys. @Mike#2: can you provide a test build (pre02 or somewhere separate) with Alex' changes from 2014-06-12 undone, so we can check if his initial change (the one that broke the nightlies) and his later patch to fix the nightlies introduced bug #525, or if that has a different cause? I'd volunteer to test that. If it *does* fix #525, I'd suggest reverting those commits for 4.0.2.1, and making the intended reason for Alex' changes a new bug, which blocks 4.0.2.2. That way, we'd have two goals for 4.0.2.2: - Bug #526 as reported by Nable - Bug #<new> to fix/add what Alex was originally trying to fix/add. If Alex' changes aren't the cause for Bug #525, we should ship 4.0.2.1 with Alex' latest changes included and #525 unfixed. In that case, 4.0.2.2 would be blocked by #525 and #526. -Stefan, wearing the X2Go-Releasemeister-in-training hat ;-) _______________________________________________ x2go-dev mailing list [email protected] http://lists.x2go.org/listinfo/x2go-dev
