Publishing directly into an release

Please do not publish directly into the 3.0 repository it is NOT cooker and is
subject to QA discipline. This practice greatly increases the anount of work
QA has to do because we cannot trust in the fact the proper procedure has been
followed. The developer runs the risk of QA unintentionally publishing an
older version into the repository. I appreciate that sometimes packages are
published inadvertently but in this case please either notify QA so that they
can downgrade and clear any redundant packages in kahinah or mark them as
redundant yourself at the same place.
Thank you for your cooperation.


Could there be a way in ABF to block any packages coming in to a release repo unless it comes from Kahinah or has some kind of approval code?

1 Like