Code names for the Amarok 2.2 series

[Ian Monroe]

On Sat, Aug 8, 2009 at 9:19 AM, Nikolaj Hald
Nielsen<nhnfreespirit at gmail.com> wrote:
> I subscribe to the "choose one good name and stick with it" school of
> though. "Fast Forward" was a very strong and visible brand, and many
> people knew it because it stayed around for so long.
>
> I guess it really depends on how we choose to do releases going
> forward. Personally I think that one or two bugfix releases per major
> release it a bit low. Especially with git branches, if people _really_
> have an urge to go hack on stuff that id definitely 2.3 material, then
> fine, but overall I would like to see at least 4-5 time based updates
> to 2.2. This would also make the release name stay current for longer
> as it would apply to more releases.

This probably warrants a whole discussion, but one technique is to
actually fix all bugs in the stable release and then forward port the
fix into trunk. Especially with git, forwarding porting is easier then
backporting. I believe.

Cause yea I agree, especially now that working with multiple branches
is trivial and doesn't take a whole new checkout, we should keep
fixing the stable branch right up to the next major release.

Ian