RFC: Cleaning up Trunk

Nikolaj Hald Nielsen nhnfreespirit at gmail.com
Tue Sep 4 13:02:56 CEST 2007


I'd say go for it!

As you say, this should make the most pressing needs very visible

On 9/4/07, Seb Ruiz <ruiz at kde.org> wrote:
> Hi Devs,
>
> I'm wondering if it would be worthwhile to rip out all of the old 1.4
> amarokisms from trunk. By this, I mean everything which hasn't been
> ported yet.
> eg:
>  - Playlist
>  - PlaylistItem
>  - MetaBundle
>
> etc etc.
>
> I know, it's a HUGE amount of work, but maybe it would help us in
> clearing out the codebase and understanding the new development
> techniques we are using. Another advantage is that it would help make
> obvious the giant holes we have in trunk.
>
> Obvious disadvantages would be that we would need to keep an older
> revision checked out locally to do any comparisons etc.
>
> We have at least a start on most of the major components of Amarok 2:
> Interface, Context, Playlist, Collections, Collection browser,
> Playlist browser, services.
>
> I don't imagine that the rest of the components would be refactored,
> but probably written again from scratch (with previous knowledge or
> referencing 1.4 code).
>
> Comments?
>
> Cheers,
> Seb
>
> --
> http://www.sebruiz.net/
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>


More information about the Amarok-devel mailing list