is there any info abount which git tag/ Freeswitch release is stable?
Guys, here is a little bit of critics, There is no info - what version of freeswitch should be used in production. the wiki pages http://wiki.freeswitch.org/wiki/Installation_Guide http://wiki.freeswitch.org/wiki/Installation_Guide#Linux_and_Unix says that latest GIT is "very" stable, but in 5 pulls i did, 2 times I immediately hit regressions: first time - non working DNS resolver in mod_sofia second - broken ESL outbound (as of this night) at the same time, it's mentioned that 1.0.6 is not the "latest stable" anymore, but in files, there is only 1.0.6 so it would be very helpful if there is some way to find out, what is the latest GIT tag or release could be downloaded to be usable, it's just not possible while in development, to have GIT always stable. None can do it, so there really should be atleast "testing" tag/brunch, which is known working over serveral weeks (debian testing can be an example) Hope this piece of critics not insults anyone, FS is a great stuff, Regards, Anton.
regarding the broken ESL - it was my bug, my apologies. As for stable, or pre-stable version/tag/branch... question persists...
I don't think it's impossible - just difficult. My view is based on my experience where we "almost" continuously deploy our web sites to our live environment; we continuously deploy after every check in (waiting 15 minutes for a quiescent period) to stage and then manually push to live weekly (it used to be ad hoc, now it's every week, I hope soon it will be every day). To do this we've needed key unit tests (not full coverage by any means) and automated regression testing. And, most importantly, a change in developer mind set (we now know that as soon as we check in some code it's going to wind itself up on a live machine with live customers without any QA team to rely on). We're building a new solution with FS (on Windows) and ideally would like to adopt the same strategy. Ideally I don't want a "stable release" I want to always pull the latest version and run that in production. Right now for our FS project we've got the build process deploying to our stage environment (no live customers yet) using some Powershell scripts and Microsoft Web Deploy. We intend to build on this over the next 4 to 6 weeks. The plan is to pull from GIT, apply our own regression tests and if they pass push out to live (automatically). Currently we have plans to test only the functionality which we actually use - but depending on how things go I'm up for increasing the coverage and providing the results of our tests publicly. Perhaps this will provide a useful guide to the current state of the build and help provide what you're asking for (but I can only do this on Windows.) I'll keep you posted with our progress, (and I'll also be at the next ClueCon conference - if you're going then perhaps we can have a little brainstorm then.) Daniel -----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anton VG Sent: 07 May 2011 08:13 To: freeswitch-dev@lists.freeswitch.org Subject: [Freeswitch-dev] is there any info abount which git tag/ Freeswitch release is stable? Guys, here is a little bit of critics, There is no info - what version of freeswitch should be used in production. the wiki pages http://wiki.freeswitch.org/wiki/Installation_Guide http://wiki.freeswitch.org/wiki/Installation_Guide#Linux_and_Unix says that latest GIT is "very" stable, but in 5 pulls i did, 2 times I immediately hit regressions: first time - non working DNS resolver in mod_sofia second - broken ESL outbound (as of this night) at the same time, it's mentioned that 1.0.6 is not the "latest stable" anymore, but in files, there is only 1.0.6 so it would be very helpful if there is some way to find out, what is the latest GIT tag or release could be downloaded to be usable, it's just not possible while in development, to have GIT always stable. None can do it, so there really should be atleast "testing" tag/brunch, which is known working over serveral weeks (debian testing can be an example) Hope this piece of critics not insults anyone, FS is a great stuff, Regards, Anton. _______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer.
current HEAD is a candidate for a stable branch. On Sat, May 7, 2011 at 4:47 PM, Daniel Bryars <daniel.bryars@aeriandi.com> wrote:
I don't think it's impossible - just difficult. My view is based on my experience where we "almost" continuously deploy our web sites to our live environment; we continuously deploy after every check in (waiting 15 minutes for a quiescent period) to stage and then manually push to live weekly (it used to be ad hoc, now it's every week, I hope soon it will be every day). To do this we've needed key unit tests (not full coverage by any means) and automated regression testing. And, most importantly, a change in developer mind set (we now know that as soon as we check in some code it's going to wind itself up on a live machine with live customers without any QA team to rely on).
We're building a new solution with FS (on Windows) and ideally would like to adopt the same strategy. Ideally I don't want a "stable release" I want to always pull the latest version and run that in production.
Right now for our FS project we've got the build process deploying to our stage environment (no live customers yet) using some Powershell scripts and Microsoft Web Deploy. We intend to build on this over the next 4 to 6 weeks. The plan is to pull from GIT, apply our own regression tests and if they pass push out to live (automatically).
Currently we have plans to test only the functionality which we actually use - but depending on how things go I'm up for increasing the coverage and providing the results of our tests publicly. Perhaps this will provide a useful guide to the current state of the build and help provide what you're asking for (but I can only do this on Windows.)
I'll keep you posted with our progress, (and I'll also be at the next ClueCon conference - if you're going then perhaps we can have a little brainstorm then.)
Daniel
-----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anton VG Sent: 07 May 2011 08:13 To: freeswitch-dev@lists.freeswitch.org Subject: [Freeswitch-dev] is there any info abount which git tag/ Freeswitch release is stable?
Guys, here is a little bit of critics,
There is no info - what version of freeswitch should be used in production. the wiki pages
http://wiki.freeswitch.org/wiki/Installation_Guide http://wiki.freeswitch.org/wiki/Installation_Guide#Linux_and_Unix
says that latest GIT is "very" stable, but in 5 pulls i did, 2 times I immediately hit regressions: first time - non working DNS resolver in mod_sofia second - broken ESL outbound (as of this night)
at the same time, it's mentioned that 1.0.6 is not the "latest stable" anymore, but in files, there is only 1.0.6
so it would be very helpful if there is some way to find out, what is the latest GIT tag or release could be downloaded to be usable, it's just not possible while in development, to have GIT always stable. None can do it, so there really should be atleast "testing" tag/brunch, which is known working over serveral weeks (debian testing can be an example)
Hope this piece of critics not insults anyone, FS is a great stuff, Regards, Anton.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Anton, I consider myself a part of this community as well as an active contributor. Whoever knows me personally or has spoken to me for more then 5 minutes is able to tell the passion that I hold for OSS and, of course, FreeSWITCH. Maybe this passion is too blindly but I believe that there are some importants points being overseen here by most of those who write these types of email I see pop up on the mailing list every now and again. 1. FreeSWITCH's core is developed mainly by 3 or 4 guys. We are talking about less then *5 *people where one of them is the person who has made over 60% of the code in there. 2. FreeSWITCH does not generate direct profit for anyone who has been actively contributing that I know of. We all add a twist to the product and that is where our value added lies on. 3. No one is working for no one, this is one of the things that makes it a community instead of a company. My point is that it can be a little offending when I see those comments that are almost demanding and that doesn't have a proposition to go with. I don't want to make any enemies and don't intend to offend either, but instead of making a short response to this critic, I would think that we can all benefit from more ppl helping on the project. Maybe the right question could have been, who is the tester on the project and how can I help test to get a stable branch? I am really sorry if I seem aggressive, it is not the intention. I simply took the opportunity of this email to write about my feelings towards emails like those and not yours exclusively. I hope my critics do not offend anyone. :-) Regards, João Mesquita On Sat, May 7, 2011 at 6:57 PM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
current HEAD is a candidate for a stable branch.
On Sat, May 7, 2011 at 4:47 PM, Daniel Bryars <daniel.bryars@aeriandi.com> wrote:
I don't think it's impossible - just difficult. My view is based on my experience where we "almost" continuously deploy our web sites to our live environment; we continuously deploy after every check in (waiting 15 minutes for a quiescent period) to stage and then manually push to live weekly (it used to be ad hoc, now it's every week, I hope soon it will be every day). To do this we've needed key unit tests (not full coverage by any means) and automated regression testing. And, most importantly, a change in developer mind set (we now know that as soon as we check in some code it's going to wind itself up on a live machine with live customers without any QA team to rely on).
We're building a new solution with FS (on Windows) and ideally would like to adopt the same strategy. Ideally I don't want a "stable release" I want to always pull the latest version and run that in production.
Right now for our FS project we've got the build process deploying to our stage environment (no live customers yet) using some Powershell scripts and Microsoft Web Deploy. We intend to build on this over the next 4 to 6 weeks. The plan is to pull from GIT, apply our own regression tests and if they pass push out to live (automatically).
Currently we have plans to test only the functionality which we actually use - but depending on how things go I'm up for increasing the coverage and providing the results of our tests publicly. Perhaps this will provide a useful guide to the current state of the build and help provide what you're asking for (but I can only do this on Windows.)
I'll keep you posted with our progress, (and I'll also be at the next ClueCon conference - if you're going then perhaps we can have a little brainstorm then.)
Daniel
-----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto: freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anton VG Sent: 07 May 2011 08:13 To: freeswitch-dev@lists.freeswitch.org Subject: [Freeswitch-dev] is there any info abount which git tag/ Freeswitch release is stable?
Guys, here is a little bit of critics,
There is no info - what version of freeswitch should be used in production. the wiki pages
http://wiki.freeswitch.org/wiki/Installation_Guide http://wiki.freeswitch.org/wiki/Installation_Guide#Linux_and_Unix
says that latest GIT is "very" stable, but in 5 pulls i did, 2 times I immediately hit regressions: first time - non working DNS resolver in mod_sofia second - broken ESL outbound (as of this night)
at the same time, it's mentioned that 1.0.6 is not the "latest stable" anymore, but in files, there is only 1.0.6
so it would be very helpful if there is some way to find out, what is the latest GIT tag or release could be downloaded to be usable, it's just not possible while in development, to have GIT always stable. None can do it, so there really should be atleast "testing" tag/brunch, which is known working over serveral weeks (debian testing can be an example)
Hope this piece of critics not insults anyone, FS is a great stuff, Regards, Anton.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
João, your point is clear, and for sure it is very impressive, what work can be done by that modest number of developers. Don't get me wrong, there was no intention to sound "demanding", just thoughts. I myself watching FS progress from the moment Anthony have announced it. FS do not have backing company as some other, this makes some things a little more difficult But I trust it would be in a great benefit for FS to gain bigger community, and little more organization would not bother... Though it requires men power, which seems is just not enough for the moment. BTW, somehow strange, FS is not included to Debian distro, not even in UNSTABLE, although, FS support a debian build out of GIT with no extra work. Just Debian is one of the most recognized distro for servers, and having FS included would add to it's popularity quite sufficiently. Is there no willing maintainer or some other reason? BR, Anton. 2011/5/8 João Mesquita <jmesquita@freeswitch.org>:
Anton, I consider myself a part of this community as well as an active contributor. Whoever knows me personally or has spoken to me for more then 5 minutes is able to tell the passion that I hold for OSS and, of course, FreeSWITCH. Maybe this passion is too blindly but I believe that there are some importants points being overseen here by most of those who write these types of email I see pop up on the mailing list every now and again. 1. FreeSWITCH's core is developed mainly by 3 or 4 guys. We are talking about less then 5 people where one of them is the person who has made over 60% of the code in there. 2. FreeSWITCH does not generate direct profit for anyone who has been actively contributing that I know of. We all add a twist to the product and that is where our value added lies on. 3. No one is working for no one, this is one of the things that makes it a community instead of a company. My point is that it can be a little offending when I see those comments that are almost demanding and that doesn't have a proposition to go with. I don't want to make any enemies and don't intend to offend either, but instead of making a short response to this critic, I would think that we can all benefit from more ppl helping on the project. Maybe the right question could have been, who is the tester on the project and how can I help test to get a stable branch?
I am really sorry if I seem aggressive, it is not the intention. I simply took the opportunity of this email to write about my feelings towards emails like those and not yours exclusively.
I hope my critics do not offend anyone. :-) Regards, João Mesquita
On Sat, May 7, 2011 at 6:57 PM, Anthony Minessale <anthony.minessale@gmail.com> wrote:
current HEAD is a candidate for a stable branch.
On Sat, May 7, 2011 at 4:47 PM, Daniel Bryars <daniel.bryars@aeriandi.com> wrote:
I don't think it's impossible - just difficult. My view is based on my experience where we "almost" continuously deploy our web sites to our live environment; we continuously deploy after every check in (waiting 15 minutes for a quiescent period) to stage and then manually push to live weekly (it used to be ad hoc, now it's every week, I hope soon it will be every day). To do this we've needed key unit tests (not full coverage by any means) and automated regression testing. And, most importantly, a change in developer mind set (we now know that as soon as we check in some code it's going to wind itself up on a live machine with live customers without any QA team to rely on).
We're building a new solution with FS (on Windows) and ideally would like to adopt the same strategy. Ideally I don't want a "stable release" I want to always pull the latest version and run that in production.
Right now for our FS project we've got the build process deploying to our stage environment (no live customers yet) using some Powershell scripts and Microsoft Web Deploy. We intend to build on this over the next 4 to 6 weeks. The plan is to pull from GIT, apply our own regression tests and if they pass push out to live (automatically).
Currently we have plans to test only the functionality which we actually use - but depending on how things go I'm up for increasing the coverage and providing the results of our tests publicly. Perhaps this will provide a useful guide to the current state of the build and help provide what you're asking for (but I can only do this on Windows.)
I'll keep you posted with our progress, (and I'll also be at the next ClueCon conference - if you're going then perhaps we can have a little brainstorm then.)
Daniel
-----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Anton VG Sent: 07 May 2011 08:13 To: freeswitch-dev@lists.freeswitch.org Subject: [Freeswitch-dev] is there any info abount which git tag/ Freeswitch release is stable?
Guys, here is a little bit of critics,
There is no info - what version of freeswitch should be used in production. the wiki pages
http://wiki.freeswitch.org/wiki/Installation_Guide http://wiki.freeswitch.org/wiki/Installation_Guide#Linux_and_Unix
says that latest GIT is "very" stable, but in 5 pulls i did, 2 times I immediately hit regressions: first time - non working DNS resolver in mod_sofia second - broken ESL outbound (as of this night)
at the same time, it's mentioned that 1.0.6 is not the "latest stable" anymore, but in files, there is only 1.0.6
so it would be very helpful if there is some way to find out, what is the latest GIT tag or release could be downloaded to be usable, it's just not possible while in development, to have GIT always stable. None can do it, so there really should be atleast "testing" tag/brunch, which is known working over serveral weeks (debian testing can be an example)
Hope this piece of critics not insults anyone, FS is a great stuff, Regards, Anton.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer.
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ FreeSWITCH-dev mailing list FreeSWITCH-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
BTW, somehow strange, FS is not included to Debian distro, not even in UNSTABLE, although, FS support a debian build out of GIT with no extra work. Just Debian is one of the most recognized distro for servers, and having FS included would add to it's popularity quite sufficiently. Is there no willing maintainer or some other reason?
Bingo! We need help for this kind of thing. If you or someone you know is
in a position to be the maintainer then that would be a great help for the project. Thanks, MC
participants (5)
-
Anthony Minessale
-
Anton VG
-
Daniel Bryars
-
João Mesquita
-
Michael Collins