Who should test 3.7 when a download is not possible?
http://www.igniterealtime.org/downloads/source.jsp contains links to Openfire and Smack nightly builds - both pages contain no or outdated links. Any plans to create weekly builds or should one remove these pages?
no, should I’ve read it? It’s very small, within “[…]” and likely unimportant (;
I expect that teamcity will be installed on the new hardware, so it may take some days or months.
One should create archive files for additional download (libs/* and resources/database/* for Openfire; and plugins/*) to allow one to test Openfire 3.7 without too much upgrade problems. Do you think that this is possible?
The Ignite Realtime community is being migrated from Jive software servers to deticated servers for the Ignite Realtime community. Until that migration is complete, new releases can’t be built, as the servers to build them aren’t prepared to do so yet.
When the new hardware is finished being migrated to, it is only a matter of a few days (Hours? Minutes?) to build and publish new releases and betas.
I’m not really concerned when the next official release is. I’ve been using trunk for a couple of months now without any problems. I was just trying to clarify for church. I do look forward to the next official release though, as some of my associates don’t like the risk associated with using trunk.
I am looking forward to this release. Openfire and Spark keeps disconnecting every 30 minutes for me and, believe me, I have tried everythign in the book to resolve this issue. Maybe the next Openfire will fix it.