bzr 1.3rc1 today/tomorrow, final next week

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> Just a (belated) reminder that I will make bzr1.3rc1 either tonight or
> tomorrow, and plan on 1.3 final next week.  It is scheduled for
> Friday, but since I will be away that day I would like to do it on
> Thursday instead.
> 
> There are two bugs currently marked critical:
> 
> https://bugs.edge.launchpad.net/bzr/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed
> 
> 181945  	 bzr pull lp:upstart fails
> 
> The problem has been localized by James, and Aaron has posted a patch
> which makes it easier to fix but does not fix it.  I think this one
> would not be too hard.

Don't we also need to do some stuff to be officially Gnu Bazaar? At the
very least the website needs updating. I thought we would certainly
include it in NEWS or README or something in the project as well. I
don't know what was planned/requested. I just realize that nothing
actually occurred.

> 
> (critical) 	197429 	bzr gui tools are too slow with old/large
> repositories 	branch 	Critical 	Incomplete
> 
> The main remaining thing is to improve the speed of annotate on packs,
> which is very important and John's focus now.  We should land the
> patches he has done on this, but not stall 1.3 waiting for more.
> 

I had 2 specific patches for this, which have now been submitted (since
I finally was able to get decent net access at pycon). I'm still working
on it, and I'm planning on sending a email for us to discuss it.

> jml has asked for us to fix
> 
>  https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/148087/comments/12
> 
> https://bugs.edge.launchpad.net/bzr/+bug/141172
> interrupting bzr does not kill ssh child process

We explicitly set " signal.signal(signal.SIGINT, signal.SIG_IGN)" for
the ssh subprocess. I mentioned it a bit in the other bug.

But basically, we did it because SSH would die before we would get a
chance to clean up. Now it doesn't die when we are done, and I'm not
sure why.

> 
> https://bugs.edge.launchpad.net/bzr/+bug/172392
> interrupting a client waiting for a lock over bzr+ssh leaves process on server
> 
> If someone could look at them that would be very good.
> 
> If there is anything else that you think _must_ be (not "would like")
> done for 1.3, or any patches currently up that we should prioritize
> reviewing, please reply here (and if possible make sure they have bug
> numbers.)
> 

And I agree with Aaron that the weekly emails were good for keeping
everyone on track. I realize with all the sprints and everything all of
our schedules got a bit out of whack, but maybe we can get back in sync.
(Of course, for the next release I'll be on vacation...)

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH2p5HJdeBCYSNAAMRAif/AJ9Nj2cSe42uZMh91OyAKt5Au99SegCdELQV
egHeYemDb2vak+k4vkWopUs=
=UCRn
-----END PGP SIGNATURE-----