after 12h uptime with the new misdn-modules - everything still fine :-) no more oops, no more 99%-cpueaters, stable asterisk-voiping - it looks that i don't have to go back to the bristuff-mess
p. Christian wrote: > Dear mISDN community :) > > i know that some of you where upset of the hfcpci bug that was > introduced with the mISDN_1_1_3 Release a few days ago. There was > another bug, that was hit by only a few users of the NT Mode of mISDN > (in mISDNuser) that was also introduced in the 1_1_3 Release. > > Until now, we had no Release branch for mISDNuser. Now we have a release > branch in git, so we can avoid problems like that. ( A new feature makes > Application unstable, in Releases branches we should only put bugixes). > > > Since we have not a big Testing Lab @ beroNet we require the community > to make some tests. Since now we have right away made a release when we > fixed a major bug, but as you all can imagine this is not the way we > should go on. > > I would like to establish some sort of pre-release cycles and beta > testing environment. For mISDN, mISDNuser and maybe even chan_misdn. > > I started now with putting mISDN-1_1_4-pre.tar.gz and > mISDNuser-1_1_4-pre.tar.gz on www.misdn.org/downloads/pre-releases/ > > I would be happy if you download these files and make some tests, if it > works for you i can rename them to 1.1.4 and finish the release. > > > Thoughts and Ideas are Welcome. > > PS: Maybe there is some sort of Release Cycle / Project Management > Software which we should consider to setup, where the progress of > releases can be viewed > > _______________________________________________ > isdn4linux mailing list > [EMAIL PROTECTED] > https://www.isdn4linux.de/mailman/listinfo/isdn4linux > _______________________________________________ Misdn-asterisk mailing list [email protected] http://lists.beronet.com/cgi-bin/mailman/listinfo/misdn-asterisk
