----- Original Message ----- > Dan Mashal <dan.mashal@xxxxxxxxx> writes: > > > > The Feature page still belongs to the FeaturePageIncomplete category. > > > > I feel a somewhat similar way about boost and it would be nice if > > there was some more detailed descriptions here. > > Frankly, my biannual filing of Feature/Change page is mostly > cargo-culting. It's just rebase, really, even though there are 250 > dependers. I like how the Change process forces me to think and argue > through some implicit assumptions, but I've been doing this for some > time now, and more or less know the drill. That was the idea of the new template - to force owners to think about it. For Boost - I think the most important thing is that we can schedule mass rebuild based on the change page, I already added it to the mass rebuilds tracking ticket. So it work more like "ping, possible mass rebuild is needed or otherwise, we will need side tag, there could be breakage, we can go back" etc. So what we want is actually more proposals than less, as otherwise you'll always forgot about something :) > In the end we simply need to > patch our way out of any build failures, one way or another. > > So if the consensus is that Boost rebases don't need this sort of > paperwork, I'll simply not do it the next time around. I'd say after years, it's routine paperwork, mostly copy pasting - so shouldn't be difficult/time consuming, but as I said above - it helps planning - so I still think it's worth of it. Jaroslav > Thanks, > PM > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
