The most important thing is to choose a way that works that disturbs me the least.<div>I am open to work it out and you are welcome to participate but my basic principles need to stand.</div><div><br></div><div>Beliefs I want to stick with:</div>
<div><br></div><div>1) The first number is the project version number, i.e. 1 since its the first complete implementation of a particular strategy.</div><div> I would never see that version reach 2 unless I did a complete rewrite or changed my attack angle.</div>
<div> apache 1.x is forking philosophy and 2.x is threading.</div><div><br></div><div>2) The second number is the major release number, each time it goes up its a new milestone.</div><div> FreeSWITCH 1.0 was dubbed "Phoenix" because it was a new era being born.</div>
<div> FreeSWITCH 1.2 will be "Dragon" since I am sticking with mythical beings as it seems. </div><div><br></div><div>Since FreeSWITCH 1.2 might make drastic changes that other people do not want to endure, I want to permanently branch 1.x as a stable branch where small bugs can still be fixed and possibly pushed up.<br>
<br>3) I want to release branches of GIT rather than just tarballs because we need to be able to deploy quickly. I'm ok with rolling a tarball but people tend to get stuck on them and then we have to fight to get people to test new versions and we get all of our bug reports after its too late rather than before we mark it stable.</div>
<div><br></div><div><br></div><div>4) I do a huge portion of the coding on the project all by myself. So I don't have tons of resources to devote to anything too complicated. I have had volunteers in the past but nobody really seems to fully commit or stick around long enough so I need to make sure I do not let people implement their ideas then disappear and leave us stuck with it. </div>
<div><br></div><div>You might want to hang out on IRC <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch #freeswitch-dev or visit our weekly conf call <a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a> every Wednesday 12-Npm CST</div>
<div><br></div><div> </div><div><br><br><br><div class="gmail_quote">On Thu, Nov 10, 2011 at 11:25 PM, Dalei Liu <span dir="ltr"><<a href="mailto:daleiliu@gmail.com">daleiliu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks for the reply. Here are some thoughts might be useful:<br>
<br>
1. Create/update a wiki page about the definition of the version system;<br>
2. Create wiki pages for the goals of each planned version, including<br>
stable and dev version, like 1.2, 1.3;<br>
3. Tag the current master to be 1.0.8-rc1 or 1.1-rc1, and set an<br>
initial release date for the stable release, e.g Nov 30;<br>
4. Create a branch only if we have to merge master with a major<br>
feature not on the goal list of the stable version;<br>
<br>
The goal for each version can be changed and the release date can be<br>
delayed. More RC versions can be released before the formal one. But<br>
the most important thing is, the users will have a version to test, to<br>
discuss and to fix.<br>
<br>
About the next release, I feel v1.1 is better than v1.0.8 because it<br>
saves a digit for all the following versions (v1.1.3 vs v1.0.8.3,<br>
etc).<br>
<br>
Personally, I'm not a big fan to the odd/even number style. I think<br>
all the features in master should be tested and stable enough for<br>
integration (otherwise it'd better stay in a branch as branching is<br>
very cheap in git). It just needs several beta and RC versions to<br>
make it stable. Using a whole minor number for testing is a waste.<br>
<br>
Again, if you think it worths the time, I would like to start<br>
contributing on wiki pages.<br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<div><div></div><div class="h5"><br>
FreeSWITCH-dev mailing list<br>
<a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900<br>
</div>