[Foresight-devel] Re: FL3 label structure

2012-09-16 Thread Michael K. Johnson
On Tue, Sep 11, 2012 at 10:22:09PM +0200, Tomas Forsman wrote: > We will still be using devel, qa and stable stages? > Feels like we can go down to devel and stable only. But that's only my > thought about it. Well, there are several reasons we're only using two now. Among them: * An ancient (

[Foresight-devel] Re: FL3 label structure

2012-09-14 Thread Mark Trompell
Sounds reasonable too me, and as Antonio gave a +1 too, itseems to be really reasonable, given that you 2 know conary pretty well. I hope all this helps us to get rolling again. On Mon, Sep 10, 2012 at 6:53 PM, Michael K. Johnson wrote: > One of the design goals in Conary's "promote" process is t

[Foresight-devel] Re: FL3 label structure

2012-09-13 Thread António Meireles
On Mon, Sep 10, 2012 at 12:53 PM, Michael K. Johnson mailto:johns...@danlj.org>> wrote: One of the design goals in Conary's "promote" process is to rewrite all trove references as if they existed on the target label, where that makes sense, in order to avoid references that expose t

[Foresight-devel] Re: FL3 label structure

2012-09-11 Thread Tomas Forsman
2012-09-10 18:53, Michael K. Johnson skrev: > One of the design goals in Conary's "promote" process is to rewrite > all trove references as if they existed on the target label, where > that makes sense, in order to avoid references that expose the > development process. This was really designed fo