there's no reason to tag and release versions if the answer to any issue is 'make current', and support is not available unless that's been done. Far better to either have meaningful releases with stable and devel branches, or not to have releases at all. Well, the response on a stable version about a bug report that's been already fixed would be: "apply this patch and retest, come back to us if problem persists" Isn't that exactly what make current does? This way of developing may be not broken-trunk-proof, but from your comment I think an easier way to approach Lon's suggestion would be making a more understandable way for simple users (not fs devs) to check what modules have been altered from their version to the latest, in order to check if an issue has been solved or not, as of those clients that only want "released versions", that's the hard part. ps: hmmm Anthony's message makes my post outdated but i spent a lil bit of thought on it so i post anyways ^^ -Milena 2010/2/19 Michael Giagnocavo <mgg@giagnocavo.net>
Maybe something that could work is a simple way for people to record the SVN number and config they’re using. It might encourage people to not get so stuck up on a released version number. And once they’re more comfortable with SVN, perhaps they’ll try head more often.
-Michael
*From:* freeswitch-users-bounces@lists.freeswitch.org [mailto: freeswitch-users-bounces@lists.freeswitch.org] *On Behalf Of *Michael Jerris *Sent:* Friday, February 19, 2010 12:18 AM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] 1.0.4 vs. trunk vs. bugs
This seems a good time to note that we are still looking for volunteers to assist in maintaining a stable branch. I can not do this without additional volunteer resources. We have asked several times recently to fairly silent response. If anyone is interested in assisting with this effort, please contact me offlist and we can discuss further.
Mike
On Feb 18, 2010, at 11:16 PM, Brian West <brian@freeswitch.org> wrote:
OK so I can sign you up for the stable team? ;) As per my previous email i'm 100% sure we would do a stable release if we had people tending to issues. The only problem is you would have to be on IRC tending to issues because if tony sees someone asking about a problem he'll be diving in to fix it before they can say "I have this one". This also means working in a similar manner we do already. Our process is very chaotic at times but it has served us well so far.
The goal is to leave Anthony alone so he can move forward and let the stable team manage the jira's and issues on the list related to stable.
/b
On Feb 18, 2010, at 10:10 PM, David Knell wrote:
Lon Baker <lon@kickasspixels.com> wrote:
The development branch is where feature requests and non-critical bugs
reports would be filed for the next production release.
The current process leaves a gap between production ready and
development code that may become greater over time.
Going against the grain here, I agree with you. The current way of doing things is, in my opinion, not well thought through - there's no reason to tag and release versions if the answer to any issue is 'make current', and support is not available unless that's been done. Far better to either have meaningful releases with stable and devel branches, or not to have releases at all.
--Dave
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org