Hi guys,
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.
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".
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! :)
Best regards,
Kevin Cave.
------------------------------------------------------------------------------
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