<p>Having a current branch in git only (not having it visible to the website) will help to have preparations done for the upcoming releases. Although not all maintainers will not be able to keep it current, it would be useful to reduce load on the sbo team when new releases are pushed.</p>
<p><blockquote type="cite">On May 28, 2010 12:03 PM, "Ozan Türkyılmaz" <<a href="mailto:ozan.turkyilmaz@gmail.com">ozan.turkyilmaz@gmail.com</a>> wrote:<br><br>2010/5/28 Grissiom <<a href="mailto:chaos.proton@gmail.com">chaos.proton@gmail.com</a>>:<br>
<p><font color="#500050">> Hello all,<br>> It's exciting to hear and see that SBo team have a public git repo now(You<br>> have SCM...</font></p>if there will be a repo for current, i won't able to maintain any package for it<br>
on grounds of lack of time. current changes too much too fast, and keeping<br>
track of it is itself a big job.<br>
<font color="#888888"><br>
--<br>
Ozan<br>
_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
</font></blockquote></p>