Hi Kevin, > As the person who's trying to maintain his o-matic scripts (and trying to > get out v3.0 at some point), I'm getting confused. > > It's recently been suggested to me that the git repo at > https://github.com/neutrinolabs/xrdp is the one to use for my scripts.
The official git for xrdp is still FreeRDP/xrdp. LK and I have moved our bleeding edge development to neutrinolabs/xrdp so we don't break thinks as much. I regualary do pushes from neutrinolabs/xrdp to FreeRDP/xrdp but I try to do it when it is stable. We told Gustavo to use neutrinolabs/xrdp because he wanted to use the bleeding edge drive redirection bits. The official git location may change in the furture but I will make an anouncment first. > I've been assuming that the FreeRDP repo is the canonical one. > > Also - and this is a bit of a flame but it's due to frustration - the > release management is a very confusing mess. > > On the FreeRDP github repo, there are 3 branches; "master", "v0.7", and > "license_and_coding_style_changes". v0.7 was made before the licence change and license_and_coding_style_changes can get deleted. The original plan was to release 0.7 as the last GPL version and the 1.0 would be the first Apache version. I'm not sure about that and I would like to hear suggestions. Most people don't care about the license change and just want features so maybe current master should become 0.7. > There is no use of Git tagging. > > This makes it very difficult for me to maintain/release the next version of > my o-matic tools. I if I clone from the master branch, it'll be a moving > target, and it's inevitable that changes to "master" will throw a spanner in > the works to o-matic. > > If I stick to "v0.7", that's hopefully a static release, but it'll also be > hopelessly out of date source, with none of the improvements and > enhancements being made to "master". > > I bet this isn't just me getting confused either. If I were to place myself > in the shoes of a potential user of the source code, I'd be confused at > which branch to use - there is still no definitive "devel" branch. It seems > to me that "master" == "devel" at the moment, and I don't think that's a > very good idea. > > What I'd really, REALLY love for you to do is to start at least Tagging the > master branch at each known-to-be-good point. It'd also be helpful to start > deciding - and keeping a static branch - and also decide that "this snapshot > of the code is working great, is stable, and should be tagged as 'v0.7a' or > 'v0.8'", or whatever you think is a good release versioning system. > > I still think that you should have a "devel" branch to which changes are > made, and only push changes to "master" once you are ready to make a new > static release with a new version number - and TAG it at the same time! :) > https://lists.sourceforge.net/lists/listinfo/xrdp-devel Lets use tags in FreeRDP/xrdp plus LK and I will work out of neutrinordp/xrdp and do pull requests. Of course maybe others have some ideas. I know it frustrating working from an ever changing foreign repro. Part of the problem is that we didn't know and felt free the break anything anytime. Kevin, I've been using your tool more and more(thanks to Gustavo for pushing me). I think it would really be nice if get it into the main tree. Then I can help maintain it. What do you think? Jay ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
