figured out gtk dll issues and continued working on upgrading the
Windows dependencies

Paul:

worked on auto-fill code; ui is mostly there, but still working on
the functionality

Geoffrey:

worked on usability issues

worked on improvements to sharing

Jonas:

worked on WinSparkle integration

Janet:

worked on regression tests; adding new ones; augmenting existing
ones

worked on update testing

Ben:

worked on hybrid view mode; pushed the branch to g.p.o.; it's sort
of a proof-of-concept right now but looking good

Kaz:

worked on metadata extraction and storage

Order of business:

filename type overhaul: We should override FilenameType and
PlatformFilenameType so they throw errors when used. That'll make
it easier to find issues.

Jonas is working on getting Miro to use WinSparkle, so we talked
about how we use Sparkle on OSX and how we get the appcast file and
move the data around to make it happy in Sparkle. We also talked
about how to tweak the installer so that Miro passes to winsparkle
which kicks off the installer and shuts down Miro. Then the
installer shows a progress bar and kicks off the new Miro.

Miro is developed by a community of people including you! If you
can't contribute your time and work to development, testing, and
translations, please consider contributing funding by donating. Your money goes directly to
ongoing development of Miro and related projects like Miro
Community and Universal Subtitles. See
http://pculture.org/about/ for more details on these projects.

Did you know there's a Miro User Manual? If you haven't looked at
it yet, it's worth taking a look at. You can find it at
http://manual.getmiro.com/ .

Talked about the things we want to refactor during this dev cycle.
We can't refactor everything, so we talked about what's in the
refactoring queue that affect things we're already working on for
4.1 and working on those.

We need to figure out a better way to test translations for
bogosity. We need to balance fragility of whatever it is we
do with usefulness and effort it takes to implement/maintain.
Janet will think about this.

Miro is developed by a community of people including you! If you
can't contribute your time and work to development, testing, and
translations, please consider contributing funding by donating. Your money goes directly to
ongoing development of Miro and related projects like Miro
Community and Universal Subtitles. See
http://pculture.org/about/ for more details on these projects.

Did you know there's a Miro User Manual? If you haven't looked at
it yet, it's worth taking a look at. You can find it at
http://manual.getmiro.com/ .

A couple of days ago while I was on vacation, the team finished up the
changes for Miro 4.0.2.

There was a problem with the original 4.0.2 builds for people who were
running Miro for the first time which we fixed yesterday. Thus, I
re-tagged v4.0.2 and built a new set of 4.0.2 builds. The new set
are identical to the old set except that the new set doesn't have the
first time startup bug and it also has updated translations.

If you have the original Miro 4.0.2 and Miro starts up, then you
don't need to "upgrade" to the new Miro 4.0.2 build.

If you don't know which version of Miro 4.0.2 you have, launch Miro,
go to Help -> About in the menu and if the sha is e1cafdd1 (the v4.0.2
tag) or be096d8e (the rev in the Miro-4.0 branch that the v4.0.2 tag
points to), then you've got the most recent v4.0.2.

Working on regression tests and testing bug fixes that have been
going in over the last couple of weeks.

Will:

Moving along on the Windows overhaul. Took a step back to make sure
I had all my ducks in a row in regards to knowing exactly the
situation I'm in and what the options are.

Spent some time looking at issues people were having.

Paul:

On vacation last week.

Worked on speed issues with device support.

Worked on Miro Community bits.

Geoffrey:

Worked on issues for 4.0.2.

Kaz:

Worked on support for MusicBrainz/EchoNest.

Jonas:

Worked on gzip support for feeds.

Worked on some other things for 4.0.2.

Order of business:

Talked about the 4.0.2 timeline.

Talked about specifics of some issues people were having.

Talked about MusicBrainz/EchoNest support.

Miro is developed by a community of people including you! If you
can't contribute your time and work to development, testing, and
translations, please consider contributing funding by donating. Your money goes directly to
ongoing development of Miro and related projects like Miro
Community and Universal Subtitles. See
http://pculture.org/about/ for more details on these projects.

Did you know there's a Miro User Manual? If you haven't looked at
it yet, it's worth taking a look at. You can find it at
http://manual.getmiro.com/ .

4.0.2 is going pretty well. There are still a few blockers, but
most things are in a nearly done state.

Jonas:

worked on improvements to sidebar and continuous playback support.

worked on gzip/deflate support for feeds

going to switch to 4.1 development

Geoffrey:

worked on fixing a series of nits for 4.0.2

Kaz:

worked on unit tests for metadata

Janet:

worked on 4.0.2 testing

continuing to work on regression testing and updating test systems

Will:

finished Miro User Manual updates

almost done overhauling our Ubuntu packaging to make it easier to
be easier to deal with

sent Steven a contributor assignment form

started working on the overhaul of Miro on Windows

Order of business:

4.0.2: Fix anything important, but this is probably our last point
release for the 4 series. We're pretty close to having blockers
finished.

4.1: We have a lot of clean-up work that we want to do, but probably
can only work through some of it for 4.1. So we talked about doing
theme-focused clean-up similar to what we've done on previous
releases and clean up things related to things we're working on.

Miro is developed by a community of people including you! If you
can't contribute your time and work to development, testing, and
translations, please consider contributing funding by donating. Your money goes directly to
ongoing development of Miro and related projects like Miro
Community and Universal Subtitles. See
http://pculture.org/about/ for more details on these projects.

Did you know there's a Miro User Manual? If you haven't looked at
it yet, it's worth taking a look at. You can find it at
http://manual.getmiro.com/ .

we're going to release Miro 4.0.1.1 in the next day or two to fix
bug #17539

we're going to release Miro 4.0.2 on June 6th

we're going to continue working on some minor issues for a 4.0.3 at
some point

we're also going to start work on Miro 4.1, but that hasn't been
planned out, yet

Janet:

tested Universal Subtitles

worked on sikuli automated tests for Miro on Windows

working on other ways to have more comprehensive testing with Miro
on Windows

Ben:

fixed some issues with 4.0.1

managing 4.0.2

Will:

tracking downloads (147K downloads)

built the ubuntu packages --- had problems with some issues

working on updating the manual

fixed a few bugs for 4.0.2

Paul:

worked on Miro Community, Miro Guide and Miro stuff

Kaz:

wrote some unit tests

worked on some encoding issues

Jonas:

worked on continuous playback options

added an option for default list view

Order of business:

Talked about bug #17593. We're going to do 4.0.1.1 just for Windows
with that one fix.

Going to do a 4.0.2 really soon.

Bumping a few things to 4.0.3 and then everything else gets bumped
to 4.1.

Miro is developed by a community of people including you! If you
can't contribute your time and work to development, testing, and
translations, please consider contributing funding by donating. Your money goes directly to
ongoing development of Miro and related projects like Miro
Community and Universal Subtitles. See
http://pculture.org/about/ for more details on these projects.

Did you know there's a Miro User Manual? If you haven't looked at
it yet, it's worth taking a look at. You can find it at
http://manual.getmiro.com/ .

I tagged Miro v4.0 yesterday and did the final set of builds for
source, Windows and OSX. It was a pretty monumental moment for me.

I think we started working on 4.0 back in October, though it might
have been earlier. The feature set for 4.0 was really aggressive and
we added a few new people to the Miro dev team. Also, I became a
new dad in November.

The dev cycle was intense all the way through. I was pretty much
working all available hours for the last few months or so including
nights and weekends.

Now Miro 4 is released. Also, my baby is 6 months old. It's arguable
which of these two monumentally life-changing events took more time,
energy and patience. I honestly feel like a father of both projects.

We've already started working on a Miro 4.0.1 to address issues with
4.0 that were either impossible for us to get good data on or were things
we had to defer in order to hit the May 23rd release date. I think
the plan is to push 4.0.1 in a couple of weeks.

If you have problems, either write up a bug report or send me an email
(willkg at bluesock dot org) with the specifics of your problem. I'll
try to respond in a day or two.

On May 20th, we released Miro 4.0 rc2. This has a few known issues, but
we've fixed a ton of stuff since rc1. We're 2 days away from tagging
a final build. Please upgrade to rc2 and help us test it out.

Specifically, we need your help testing:

using Miro to sync media between Miro and your Android device

using Miro to stream through DAAP to other DAAP clients on
your network

Miro on Windows

Miro 4.0 rc2 builds are located on the
nightlies page
in the Sticky Files section.

Note that this is not a final release release! There are still some problems
and tweaks we're working on.

Also, we really need help with translations. If you know multiple languages,
please help us translate. On Launchpad, there's a Miro section for translations.

Also, if you help with testing and translation, please let me know
so I can gleefully add you to the credits where you rightfully belong!

If you haven't helped before, now is a good chance to jump in and make
your mark! Only 2 days left!

A while back, Ned Batchelder wrote about poxx.py
which he wrote that generates a completely translated .po file to help
find strings in his apps that weren't being translated.

We on the Miro dev team had a similar need. Additionally, we have the
problem where in some languages, the translated string is longer than
the English version and that creates some sizing issues in the ui code.

I took Ned's poxx.py, fixed some issues I had with it, then rewrote
the transform to do something reminiscent of what the Swedish Chef would
say. The transform has the following properties:

the output is vaguely readable

the output is longer than the input which helps us find ui issues

the output is clearly distinguished from English which helps us find
strings that aren't getting translated

the output is mildly amusing which is sometimes important in dark
times

I threw it together in an hour. It's not a beautiful transform and it
doesn't add any "bork bork bork". I might tweak it some rainy day.

6 bugs, some of them pretty icky, some should block and some shouldn't

Kaz:

4 bugs, 3 hours of work or so

Geoffrey:

1 bug, waiting for more information, shouldn't block an rc2

working on OSX Lion support, looks like it might be fine without
too many issues

Jonas:

1 bug, but it shouldn't block rc2

Will:

0 bugs, working on Miro User Manual updates and end-of-dev cycle
stuff, will pick up P1 bugs as needed

Paul:

0 bugs, will pick up P1 bugs as needed

working on MiroGuide stuff

Order of business:

rc2 today

Miro is developed by a community of people including you! If you
can't contribute your time and work to development, testing, and
translations, please consider contributing funding by donating. Your money goes directly to
ongoing development of Miro and related projects like Miro
Community and Universal Subtitles. See
http://pculture.org/about/ for more details on these projects.

Did you know there's a Miro User Manual? If you haven't looked at
it yet, it's worth taking a look at. You can find it at
http://manual.getmiro.com/ .