I think the goal would be to never manually sync weekly. To achieve this, would mean leaving packages in limbo longer before moving to main .... then longer in main, before moving to weekly.
Not hammering on pixbuf, just a example. I installed the updates from limbo as soon as they were available, I had the issue. I was busy and could not reply to this ml until the next morning. While putting together a report for this list, the next morning, gathering logs, trying different things to correct the problem on my own. The updates had already hit main repo's. People were coming in the irc channel with the issue, and being reported on the forums. In this case, leaving updates in limbo longer could have avoided the problem for users. Thank you Fabio for fixing the issue as fast as you did, In this case a manual sync of weekly should also be done so everyone got the new update. The revised update was released to main just after the weekly sync, means weekly would have to wait a full week to get them. On a side note, if updates are pushed to main the day before a weekly sync, they get no time in main to be tested. Which is why I say sabayon has the tools, maybe not using them to be as effective as they could be. Is it written somewhere that weekly has to be synced weekly? Maybe every two weeks is more stable and practical for testing.... maybe once a month? I believe wolfdens point is, if there were guide lines that updates stay in a repo for a certain period of time, before being pushed to the next ... weekly would be ultimate in stability and never need a manual sync, users would be happy. On Sun, Oct 9, 2011 at 11:55 AM, Fabio Erculiani <[email protected]> wrote: > I can setup a devel-announce (push-only) mailing list and have entropy > server issue an email update there (this would require 1-2h coding to > make possible to attach post-commit hooks, that's not a problem btw). > > So the data flow would be like this: every time a new repo is pushed, > a hook will read what's been removed/added and push an email to > devel-announce ML. > > Could that work? > Even though, I think this overlaps a bit the purpose of the ChangeLog > file available into remote repository database dirs (the same > containing packages.db.*). Wouldn't that be enough? > > sabayon-weekly is automatically generated from sabayonlinux.org in a > @weekly cronjob. > The alternative is to sync it manually, which would add more burden. > > -- > Fabio Erculiani > >
