Jay, why don't you tag releases on each branches? I raised Japan xrdp Users Group more than six months ago and sought how can we make xrdp itself and its community better. One of the issue is release tags.
xrdp users in Japan are confused which is the officially released source and which version is recommended to use. Of course I know about releases but that is not user-friendly. It prevents me from introducing xrdp to others. AFAIK, these commit hashes are officially released, right? Let's tag them! v0.6.0 don't know v0.6.1 5d5375873 v0.7.0 no official releases v0.8.0 86eb45c7a You should tag other releases, too, if you can. -- `whois vmeta.jp | nkf -w` meta <m...@vmeta.jp> ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ xrdp-devel mailing list xrdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xrdp-devel
