[Digikam-devel] DigikamImagePlugins ready to release to 0.8.1...

[Tom Albers]

Hi Sebastian,

Op dinsdag 7 februari 2006 02:21, schreef Sebastian Röder:
> Salut Gilles,
>
> > > > You can start to release DigikamImagePlugins to 0.8.1. Gerhard have
> > > > commited a patch to fix all .rc files and others stuff...
>
> Did you do the commit to SVN? I am asking cause the ChangeLog only shows
> commits done by you on 2006-02-05. Just to be sure.
>
> > No need to relase DigikamImagePlugins doc tarball for 0.8.1. There is no
> > changes between 0.8.0 and 0.8.1... but you can do it in your computer to
> > test. At the next 0.9.0 release, the documention will be very updated...
>
> OK, I will do it for testing once I have a little more freetime ...

Please note, you will need an evening to fetch the translation. So 
s/little/mucho/

> > > Now I have to investigate the two ruby scripts that actualy create the
> > > tarballs a little cause it looks like they need a SVN account ... what
> > > I would not quite understand. In case I can not work that out I will
> > > ask qustions on IRC or the list - stay tuned ;-)
>
> OK, here is what I found out. The normal tarball preparation works like
> that: 1. Adjusting some files to reflect the new release number and such.
> 2. Commit the changes to SVN. Update the ChangeLog. Commit the updated
> ChangeLog to SVN. 3. Run the ruby script to do fresh checkouts (with your
> SVN account data) and do some magic to finaly provide you with the tarball.

Note that the ruby script needs to run in a temporary, empty folder outsite 
the co folder.

> Now since I do not have a SVN account this is a little bit more complicated
> and I have to adjust the whole process to work with anonsvn.
>
> I will sent you and Toma a SVN Diff that reflects all the changes I have
> made. I only want to do this once so my changes to filles is NOT reflected
> in the ChangeLog of the tarball (that doesn't harm I guess, and all changes
> till 2005-02-05 are listed in the updated ChangeLog of the tarball). Hope
> you can understand my explanation cause I am not quite sure whether I
> managed to explain it in English.

I changed the .lsm and changelog, so the release date is the 11th. We dont 
have to release that day, but I prefer it to be close to the actual release 
date.

> I have changed the following path variables in the ruby script.
>
> This are the original values from 0.8.0 used by toma:
>
> svnbase    = "https://toma@svn.kde.org/home/kde"
> svnroot    = "#{svnbase}/trunk"
> adminroot  = "#{svnbase}/branches/KDE/3.5"
>
> And this is what it looks like now after my changes:
>
> svnbase	   = "svn://anonsvn.kde.org/home/kde"
> svnroot    = "#{svnbase}/branches/stable"
> adminroot  = "#{svnbase}/branches/KDE/3.5"

That is fine.

> > Ok. Not sure to find me on IRC this week. I'm a little bit sick...
>
> J' espere que tu n'est pas trop malade! :-)
>
> if I did a mistake here then this has to be adjusted on SVN. If everything
> is fine then please commit the attached svn-diff to SVN and I will build
> the tarball. I also send you the PACKAGE file that I adopted from digikam
> for digikamimageplugins and I think it's a good idea to put them into
> digikamimageplugins as well. However this file doesn't show up in the
> svndiff so I sent it this way.

Committed. I edited the ruby script to delete the PACKAGING file btw.

Toma
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20060208/63daa8b1/attachment.sig>