"Eric Y. Kow" <[EMAIL PROTECTED]> writes: > 3) Patches will typically flow from unstable into stable. However, if > Eric feels that patch is obvious and not likely to require > discussion, he will apply it directly to stable. For the moment, > Eric only considers code comments, documentation and test suite > modifications to be obvious. > > 4) The stable repository will be tightly kept in synch with unstable > repository. Patches should make it from unstable to stable within > the same day unless either David or Eric feel they are not yet > ready for stable.
Have you considered automatic, or near-automatic, migration of patches from unstable to stable? I'm thinking by analogy of how Debian package updates automatically migrate from Unstable to Testing based on a number of conditions (its priority, if it introduces a critical bug, &c). > 7) Darcs will now be switching to a new time-based release model > with new releases coming out every six months. The first > release in this cycle will be in January 2009. In the meantime, > we will work towards getting an intermediary release out to > fix bugs in 2.0.2 and to provide some performance improvements > through http pipelining. I presume releases will be made from the stable repository? _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
