On Thu, 08 Jul 2010 10:56:39 +1000, Allan McRae wrote:

I will schedule this for the week starting August the 9th. This is after the KDE 4.5 release but before the first beta for GNOME 3.0. It will also give us plenty of time to clean out [testing] and perhaps get that [staging] repo running?

I would like to implement that...but I am really unsure if people want me to or not. Also we should try to get the package pool running before as we would benefit a lot from this for such large rebuilds. But I am quite sure I should have the final patches for dbscripts done by then. -- Pierre Schmitz, https://users.archlinux.de/~pierre

On Thu, Jul 8, 2010 at 5:35 AM, Allan McRae wrote:

On 08/07/10 18:34, Pierre Schmitz wrote:

...

On Thu, 08 Jul 2010 10:56:39 +1000, Allan McRae wrote:

...

I will schedule this for the week starting August the 9th.  This is after the KDE 4.5 release but before the first beta for GNOME 3.0.  It will also give us plenty of time to clean out [testing] and perhaps get that [staging] repo running?

I would like to implement that...but I am really unsure if people want me to or not.

I say go ahead and do it.  I work on the principle that if no-one speaks out against it, then it is a good idea...

I'll speak out against it- not super strongly, but still a -1. We had an unstable repo for ages and it was completely underused. Now we are establishing another repo that will probably always have to be enabled in lockstep with [testing] anyway. I guess I just think we could use [testing] more effectively rather than adding some new [staging] repo. -Dan

On Thu, Jul 8, 2010 at 7:30 AM, Pierre Schmitz wrote:

On Thu, 8 Jul 2010 07:25:32 -0500, Dan McGee wrote:

...

On Thu, Jul 8, 2010 at 5:35 AM, Allan McRae wrote:

...

On 08/07/10 18:34, Pierre Schmitz wrote:

...

On Thu, 08 Jul 2010 10:56:39 +1000, Allan McRae wrote:

...

I will schedule this for the week starting August the 9th.  This is after the KDE 4.5 release but before the first beta for GNOME 3.0.  It will also give us plenty of time to clean out [testing] and perhaps get that [staging] repo running?

I would like to implement that...but I am really unsure if people want me to or not.

I say go ahead and do it.  I work on the principle that if no-one speaks out against it, then it is a good idea...

I'll speak out against it- not super strongly, but still a -1. We had an unstable repo for ages and it was completely underused. Now we are establishing another repo that will probably always have to be enabled in lockstep with [testing] anyway. I guess I just think we could use [testing] more effectively rather than adding some new [staging] repo.

Please reread my proposal. It's completely different from the unstable repo and also includes a new policy for testing. Anyway; this wont work at all if not everybody will use it and just use testing as we do now. So for now I wont waste time on this idea as long as there was no decision.

Yes, part of the reason I hadn't responded before was that I didn't have time to read it back then, and it had slipped my mind. I will read it and attempt to give you more constructive feedback. -Dan

On Thursday 08 July 2010 02:56:39 Allan McRae wrote:

Well, no-one has mentioned anything... Sorry, but I've really few free time in these days.

I will schedule this for the week starting August the 9th. This is after the KDE 4.5 release but before the first beta for GNOME 3.0. It will also give us plenty of time to clean out [testing] and perhaps get that [staging] repo running? 9th August is fine for me. KDE should be released 4th, give me a couple of days and I'll put it in [testing] for someday, then I will move it out and we can start the build. Or we can use the [staging] repo and keep KDE in [testing] for a week. Anyway the RC1 is enough stable and this RC2 is still better; I could upload the RC2 in [testing] today and the stable release directly in [extra].

-- andreascarpino.it Arch Linux Developer

On Thu, Jul 8, 2010 at 1:41 PM, Andrea Scarpino wrote:

On Thursday 08 July 2010 02:56:39 Allan McRae wrote:

...

Well, no-one has mentioned anything... Sorry, but I've really few free time in these days.

...

I will schedule this for the week starting August the 9th.  This is after the KDE 4.5 release but before the first beta for GNOME 3.0.  It will also give us plenty of time to clean out [testing] and perhaps get that [staging] repo running? 9th August is fine for me. KDE should be released 4th, give me a couple of days and I'll put it in [testing] for someday, then I will move it out and we can start the build. Or we can use the [staging] repo and keep KDE in [testing] for a week. Anyway the RC1 is enough stable and this RC2 is still better; I could upload the RC2 in [testing] today and the stable release directly in [extra].

-- andreascarpino.it Arch Linux Developer

fyi, we should probably delay the python upgrade a bit as kde 4.5 has been retagged and postponed to August 10th. Ronald

On Thu, 2010-07-08 at 10:56 +1000, Allan McRae wrote:

I will schedule this for the week starting August the 9th. This is after the KDE 4.5 release but before the first beta for GNOME 3.0. It will also give us plenty of time to clean out [testing] and perhaps get that [staging] repo running?

As for GNOME 3.0: that isn't going to happen. Upstream decided to delay GNOME 3.0 to next year and make a GNOME 2.32 with lots of things wrecked out. Basically, GNOME 2.32 is just 2.30 with bugfixes and string/UI breaks. I don't even think that will go through testing if I take a look at expected changes.