Re: 4.2.0 Tagging?

2009-01-21 Thread Sebastian Kügler
On Monday 19 January 2009 14:27:17 Allen Winter wrote:
 I guess we are still on track for 4.2.0 tagging in the next couple days?
 There is the report of 1 possible show-stopper in KMail -- I will
 investigate what's happening with that.

 Dirk,  can you send a kde-cvs-announce message reminding people?

From the PR point of view, we're on schedule. The announcement is already 
being translated, Jos and I will be finishing and polishing the feature guide 
in the next two or three days.
-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9 

___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: 4.2.0 Tagging?

2009-01-20 Thread David Faure
On Tuesday 20 January 2009, Allen Winter wrote:
 On Monday 19 January 2009 1:50:25 pm Allen Winter wrote:
  On Monday 19 January 2009 8:27:17 am Allen Winter wrote:
   Howdy,
   
   I guess we are still on track for 4.2.0 tagging in the next couple days?
   There is the report of 1 possible show-stopper in KMail -- I will 
   investigate
   what's happening with that.
   
  Thomas says that he can fix bug 169166 until tomorrow afternoon.
  http://bugs.kde.org/show_bug.cgi?id=169166
  
  So I hereby request a little delay in the tagging.
  
 Thomas fixed the KMail showstopper in r913998.
 So kdepim is good to go for the tagging.
 
And I fixed the KDirModel crash and the lack of error checking in KDirWatch
 (use of uninitialized data).

I can't promise to stop fixing bugs now, but AFAICS kdelibs is good
for tagging -- except for that KLockFile issue which seems to really
annoy some users with smbmounted directories (156759), but discussions
Dirk taught me that I don't know enough about that stuff to fix it myself
in a safe way...

-- 
David Faure, fa...@kde.org, sponsored by Qt Software @ Nokia to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: 4.2.0 Tagging?

2009-01-20 Thread Dirk Mueller
On Monday 19 January 2009, Allen Winter wrote:

 I guess we are still on track for 4.2.0 tagging in the next couple days?
 There is the report of 1 possible show-stopper in KMail -- I will
 investigate what's happening with that.

 Dirk,  can you send a kde-cvs-announce message reminding people?

mail wasn't sent as I was busy the last two days and in addition had to figure 
out why suddenly dns lookups were all broken on my machine (glibc update + 
qt4.4, found a workaround now). as far as I can read the showstoppers other 
than klockfile are resolved. 

so I have two options:

a) create 4.2.0 and backport the klockfile fix in there
b) announce tagging delay by 1-2 days, which gives me time to sit down 
tomorrow and finalize this bit where I didn't have time so far

did anyone create a 4.2.0-blocker keyword in bugzilla yet and ask people to 
tag bugreports with them?

I'm leaning towards announcing a tagging delay by 1-2 days (option b)). I'm 
way too tired now to do anything productive (including tagging), so I'll start 
the sync now and will proceed with a) or b) on roughly 9 hours from now after 
some sleep. 

Opinions?

Greetings,
Dirk
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: 4.2.0 Tagging?

2009-01-20 Thread Allen Winter
On Tuesday 20 January 2009 6:30:10 pm Dirk Mueller wrote:
 On Monday 19 January 2009, Allen Winter wrote:
 
  I guess we are still on track for 4.2.0 tagging in the next couple days?
  There is the report of 1 possible show-stopper in KMail -- I will
  investigate what's happening with that.
 
  Dirk,  can you send a kde-cvs-announce message reminding people?
 
 mail wasn't sent as I was busy the last two days and in addition had to 
 figure 
 out why suddenly dns lookups were all broken on my machine (glibc update + 
 qt4.4, found a workaround now). as far as I can read the showstoppers other 
 than klockfile are resolved. 
 
 so I have two options:
 
 a) create 4.2.0 and backport the klockfile fix in there
 b) announce tagging delay by 1-2 days, which gives me time to sit down 
 tomorrow and finalize this bit where I didn't have time so far
 
 did anyone create a 4.2.0-blocker keyword in bugzilla yet and ask people to 
 tag bugreports with them?
 
 I'm leaning towards announcing a tagging delay by 1-2 days (option b)). I'm 
 way too tired now to do anything productive (including tagging), so I'll 
 start 
 the sync now and will proceed with a) or b) on roughly 9 hours from now after 
 some sleep. 
 
 Opinions?
 
Get some sleep.  Take all the time you need.

-Allen
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


Re: 4.2.0 Tagging?

2009-01-20 Thread Michael Pyne
On Tuesday 20 January 2009, Dirk Mueller wrote:
--\/
 did anyone create a 4.2.0-blocker keyword in bugzilla yet and ask people to
 tag bugreports with them?

Somehow I misread keyword as bug and opened bug 181447 
http://bugs.kde.org/show_bug.cgi?id=181447

I then tried adding the keyword but I don't have sufficient karma, so it will 
have to wait for someone else.

As I only know of the KLockFile bug (156759) in discussion for blocker that 
is all I have set against the tracker bug.

If someone would like to go ahead and setup a keyword and close the tracker 
bug that'd by fine by me.  Otherwise if you have a release blocker you can set 
it to block 181447.

Regards,
 - Michael Pyne


signature.asc
Description: This is a digitally signed message part.
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


4.2.0 Tagging?

2009-01-19 Thread Allen Winter
Howdy,

I guess we are still on track for 4.2.0 tagging in the next couple days?
There is the report of 1 possible show-stopper in KMail -- I will investigate
what's happening with that.

Dirk,  can you send a kde-cvs-announce message reminding people?

-Allen
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team