[task #15698] Queue for adding new software

[Mohammadreza Khellat]

Follow-up Comment #5, task #15698 (project reproduce):

Placing/testing package updates through a separate fork and then merging them
when the number of updates reaches a specific number through single commit
with a popping-out title starting with CAPS is very very good idea and
practice which would make things nicely organized.

Of course, in this crazy world, we really do not have *reliable* software.

https://users.ece.cmu.edu/~koopman/des_s99/sw_reliability/
https://en.wikipedia.org/wiki/Software_reliability_testing

Loss of reliability is the price that is easily paid to ship software to
wide-range of consumers. Yet, I think with opensource, a fair share of the
responsibility of making the software work for YOU is with YOU. 

In my opinion, our share of reliability responsibility is to first refrain
from adding unnecessary software to the main branch and secondly as you
mentioned have a separate fork for adding new necessary software and testing
upcoming updates. Then when we have 10 _rather reliable_ software updates, the
fork will be rebased.

    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15698>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/