after a few month of silence around yaacc, we are now back in charge! We are looking forward to finish the open tickets for release-1.1.5. If you are interested in yaacc, feel free to leave your comment, rating on SF.net or just mail us. We are also pleased about your bug reports…
That’s it for today.
Hi out there!
Right now we put out our new release 1.1.4 . It is already available at F-Droid and at SourceForge. This time there are some huge improvements at the server side and look’n feel.
We finally managed to get all the media at your device sorted in various ways, so browsing and organizing the local media store is way easier. Next to this we did a big step at showing album art while browsing. Now the player shows cover art (if available) and at the same condition out is shown while browsing.
Next to this two big hits we had many minor improvements and fixes. See our ticket list for some more detailed information. We encourage you to switch to the new version for a better (and more reliable) Yaacc experience, so grab it while it’s hot
Next we try to focus on everything you report to us. So may it be bugs, nice to haves or urgently needed features, please let us know via comment, forum post or mail. If you like our app please feel free to rate us at SourceForge! Right now this part of our website looks a little bit deserted…
Have fun with the new release!
Hello out there!
no new release today, but we wish you a happy new year!
Thank you very much for your feedback, suggestions and comments during the last year. We tried to put everything into our app to get you satisfied, as long as is useful in our opinion . So please keep up sending us mails, bug reports and comments.
Looking forward to get a year with many improvements, new features and some more time to spend on YAACC.
A few days before Christmas we brought to you a new yaacc release as a kind of Christmas present :-).
This release is a smaller one than the last. This is exactly the way we want to release new versions in future. Smaller releases can be developed in a shorter time and let you participate new features faster.
The new features of this version are:
* improved compatibility with other upnp devices
* autostart upnp server and renderer
* display of upnp device icons
* minor fixes and improvements
Thanks to the users of yaacc and many thanks for your feature requests and bug reports! Your feedback is helping us to continually improve yaacc.
The new release 184.108.40.206 is downloadable via yaacc.de, sourceforge.net and f-droid.org.
That’s all for today!
This is our birthday posting. Like you will have noticed our little project was getting one year old yesterday. And therefore we need a little present…unfortunately presents for software seem to be awkward, we decided to provide you a new version as a present for you ;).
From now on you can get YAACC in version 1.1.2 directly from Sourceforge and froid.org will follow soon.
Since our last version is right now three months old we have plenty of new features. The most interesting are (at least in my humble opinion):
- Streaming the same data to multiple receivers at once
- Providing thumbnails for browsing images
- Shuffling the streamed media
Next to the technical changes we also changed our way of releasing. Till now we were always providing a huge set of features for our releases ( or at least for this and the last one ). We switched this to having smaller releases but will provide them way more often. To prevent our version number from exploding we decided to use not just major and minor but also minimal fixing releases. Therefore we right now have a three parted version numbers.
Since this is version 1.1.2 you might ask where version 1.1.0 and 1.1.1 have gone. Actually you can still download them via Sourceforge but we needed to bury them as soon as we released them, due to some minor problems on our way through the GIT merging hell ;).
Have a nice first advent,
In order to unify our development environment we have setup a vagrant box.
Vagrant is a tool for easily create an identical development environment for a team
by using virtual os instances.
With Vagrant it will be possible to setup a shareable unified development, release and test environment.
Using an unified process let us create yaacc releases faster in future and setup a regression test environment.
If you are interested in the development environment take a look at our wiki
right now again two months since our last post have passed by.
Nevertheless we are working on our agenda to complete the last tasks for our next release (Like you might have seen here).
Since we published our first stable version 1.0 on Fdroid was quite a success (right now quite over 2k downloads) we will continue publishing on this channel. Next to this there still is bleeding edge version with some new shiny features like multicasting and picture thumbnails.
Currently we are working on simple vagrant setup for our development environment. OpenBit will give a little bit more detailed overview of this as soon as it’s ready. Unfortunately a small company decided to put a new sdk on the market that provides some issues to get integrated .
today we did another step forward! Since now you are also able to download YAACC via f-droid.org.
The F-Droid Repository is an easily-installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform.
Take a look there and install the YAACC release via the f-droid app.
That’s all for today!
Eyeless and me have finished the work on our first release!
Today I have build the release and deployed the apk to our project site at sf.net
Here is the direct link to the release: YAACC-1.0.apk
Now it’s time for cleanup the documentation…:-)
What’s in the release? Have a look at the features
Today I will not tell you something about our recent and fancy features, but our optimized building process. Till now we build script driven nightly-builds on our local machines. But since some days we switched to a Jenkins instance running on our server. This provides an easier and much more error proof way of building the app and pushing it towards SourceForge.
Right now every time somebody checks in some new sourcecode the Jenkins will try to build the app and send an error report to the corresponding developer if the build fails.
Once a day it also checks whether new code was added and built during the last 24 hours and it will tag it as a nightly-build and push it towards SourceForge.
Every time a new tag is created and pushed, our source documentation is also automatically updated.
In the future we are planning to add some features for code analysis to our automated build. But for now we are quite happy to do a step away from our home grown way of building nightly-builds.