[KPhotoAlbum] KPhotoAlbumFreezing up for release

[Jesper K. Pedersen]

Well I'd prefer not to do so, but given that it is trunk that the translators 
see, we would run the risk that someone did a translation while we did new 
development, and therefore the subsequence patch level releases would have 
broken translations.

I've asked several people about a better way, but never got an answer I'm 
afriad.

Cheers
Jesper.

On Wednesday 23 September 2009 18:35:38 Wes Hardaker wrote:
| >>>>> On Tue, 15 Sep 2009 09:01:55 +0200, "Jesper K. Pedersen"
| >>>>> <blackie at kde.org> said:
|
| JKP> Meanwhile, I'd like to get all of this summers coding out, so I've
| JKP> copied the devel branch over to trunk, and nuked the devel
| JKP> branch. If you have uncommitted changes there, simply do a svn
| JKP> switch or run a svn diff to get your changes into a patch you can
| JKP> apply on trunk.
|
| FYI, this is sort of annoying from a third-party tracking point of
| view.  I remotely track the SVN tree and have a local repository copy so
| I can commit my changes locally while still pulling in the upstream ones
| you guys submit.  Switching back and forth all the time makes it
| somewhat painful to do (unless I want to pull the whole kde tree, which
| I'd rather avoid).
|
| Is this common KDE practice?
|
| [most other KDE apps I've worked on have been simpler because I've
| frequently only had one patch or so to track.  I have many more
| outstanding patches to KPA that I'm tracking though]

-- 
Having trouble finding a given image in your collection containing
thousands of images?

http://www.kphotoalbum.org might be the answer.