Hello I have make same thoughts about slink version by time and by goals. We have say: We make all X months a new version. And I think goals are good things. Goals give the distribution a direction. With this all I make this proposal: We make all X months (X=3-5) a new distribution. In this distribution are alle packages, that least one month in the distribution (frozen-time) and have no big bugs. All packages with big bugs are remove (and if possible, replace with an old stable version of the package) We make goals for slink to. Nice little goals. (this is all normal, but now my part:) In the frozen time, we don't make uploads in frozen. Only for Base packages. o If we distribut slink by time, we use the version-number 2.0.1 for the new stable. By all new distributions by time we increase the third number in the version-number. o But if we distribut slink serving one or more new goals, we use the first time 2.1.0. By all new distribution serving new goals we increase the second number in the version-number. We must automate the release by time on a large scale. (like a cron-job) Comments? Grisu
Attachment:
pgp2nokhb7Qmd.pgp
Description: PGP signature