[pkg-bacula-devel] Workflow questions

[Luca Capello]

Hi Alexander!

On Mon, 14 May 2012 12:20:20 +0200, Alexander Golovko wrote:
> I have some questions about rules to work together better.

Please see my workflow here:

  <mid:871umxpm38.fsf at gismo.pca.it>
  <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/2012-May/000172.html>

> 1. Who and when merge patches into git master branch?
> Should i merge part of changes from dev branch into master branch or
> wait for somebody to review changes?

Everyone who is part of the pkg-bacula Alioth group has commit access to
the Git master branch.  If you feel OK with committing something, go on,
but you take responsibility of that.  Reviewing changes is also fine,
but please note that we are all volunteers and this could take some
time.

> 2. What we do with bugs, fixed in git, but not yet uploaded into
> distribution?
> Mark it as pending?

Yes, also providing a hint to the testing/temporary packages that fix
the bug, see:

  <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612352#12>

> 3. When and how new package version uploaded into distribution?

Whenever we want.  Basically, I would like to incorporate Hauke's work
as much as possible before any new upload, but it seems that we should
upload a new version soon to fix:

- #639466, postgresql-9.1, everything already in master already
- #658326, non-free SHA-1, I will reply to your last patch
- #672765, mysql-5.5, patch provided, but it could be useless if we move
           to multi-arch anyway (just to avoid double-work)

Basically, I think that we need a new plan different from:

  <mid:87zkbtd5o5.fsf at gismo.pca.it>
  <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/2012-March/000149.html>

1) keep bacula out of testing, thus out of wheezy (the two serious bugs
   #658326 and #672765 should do this)
2) import Hauke's changes ASAP
3) upload a version that fixes the more important stuff
4) upgrade to the latest upstream version
5) upload this later version after having tested *migrations*
6) finish the work (import from Ubuntu & Co.)

This is to do stuff in a proper way, the other option being simply to
ignore Hauke's commits and start from scratch, which I do not like.

> 4. I see, that we have build problem on mipsel arch.
> Are debian build farm can be used only automatic after package
> uploading?
> I can't find info about debian build farm for testing purpose, so
> where i can build package for mipsel or other arch?

Everything is on db.debian.org, specifically:

  <https://db.debian.org/machines.cgi>
  <https://db.debian.org/machines.cgi?host=eder>

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20120514/b67abc15/attachment.pgp>