[Pkg-parrot-devel] Parrot 4.0.0

[Dominique Dumont]

Le Saturday 7 April 2012 03:06:59, Allison Randal a écrit :
> > Given that this thread started 3 months ago, I think you should implement
> > your  ideas unless Allison replies within next week.
> 
> As long as we upload the parrot and rakudo packages at the same time, we
> should be fine. Strategies using Breaks are too fragile to be worth the
> complexity. (And, none of this would be necessary if Rakudo didn't poke
> so indiscriminately into Parrot internals.)

Your proposal is fine for unstable users. Unfortunately, migration to testing 
depends not only on delay, but also on serious or important bugs logged 
against a package. If a serious bugs is logged against rakudo, parrot will 
migrate to testing without rakudo, thus breaking old rakudo on testing 
machine. Specifying Breaks now will probably avoid dealing with bug reports 
later. (been there with libsdl and frozen-bubble)

Tell you what: let's do teamwork. If you're not comfortable with Breaks 
statement, let us split the work: you do the package internals, we deal with 
advanced package details. Well, since 4.0.0 is good to go, we just have to 
complete it with a Breaks statement. We'll see for next parrot version if such 
a statement is still necessary.

> Do any of you have DD status? I'm DM for Parrot, but can't actually
> upload the packages because libparrot is always "NEW". Like I said, the
> 4.0.0 packages are ready to go, they just need a sponsor.

Yes, Alessandro and I are both DD. (quite recently for Alessandro, congrats 
;-) ) . Alessandro, can you handle the small modif and the upload ?

All the best

Dominique