Good question. As far as I know, it was the Trunk in
SVN of
http://www.sf.net/projects/adempiere. There the ruling council there has allowed it to be transferred to
Mercurial HG repository of the same project space.
However the top coders namely Heng Sin has moved his project to
Kenai and Carlos also moved his to
kenai. So this makes 3 spots to look at and our eyes have to pay more attention to those Kenai space as there is where the real meat resides.
This is not good. Or easy for newbies.
So i asked Carlos why not he merged his work with Heng Sin's and worked under him. According to Carlos, that was his intention but Heng Sin preferred things remain in their own silos as its possible with GIT style versioning system as granted in HG Mercurial. He said that Heng Sin prefers him to take openly and apply his own patches in his (Carlos') own project space. Carlos also assured me that his is not a fork, and will be open and offered to the ADempierean Community at large. He will also assist the ruling council there to incorporate his work back to the trunk.
Looking at what Carlos Ruiz is all about all this while which is the careful application of patches and upgrading of the sourcecode as well as making stable official releases for the past 4 years of ADempiere, his has the characteristics:
1. It is more stable
2. It is more up to date
3. It is more production ready
4. It is updated more faster
5. It is more receptive to others' work
6. It maintains to be usable as main trunk
7. His support is more expert quality
8. He maintains best practice and documentation included
9. His is always community open source, with no parts hidden for commercial reasons
I thus will use his work as my reference trunk and also try to incorporate any enhancements or bug fixes i have to his project space. This is with the sincere hope that eventually his and Heng Sin's work become mainstream. In fact if we mostly refers to the plan here, that situation will be true!
The better side is that all 3 spaces are in hg mercurial platform and although it will get using to, ironically it is intended to try to avoid conflict within the commit members. And the way it does that is to allow the contributors to work in their own separate silos without bothering about what the others do!