[Pkg-ltsp-devel] pkg-ltsp bzr repository status and more.

Gustavo Franco gustavorfranco at gmail.com
Sat Jan 14 22:38:48 UTC 2006


Hi list,

There's a pkg-ltsp "official" repository being prepared right now to
host the branch(es) that we should use to do the upcoming ltsp Debian
package uploads.

We used mdz as a start point and it's already available[0], but you
*don't* want to branch out from that tree yet. claviola converted both
vagrant and pere repositories from baz to bzr and otavio merged them
over pkg-ltsp branch in a different location[1].

What needs to be done before the first pkg-ltsp upload:

* You can review [1] and let us if there's something weird there;

* Otavio will "replace" pkg-ltsp repository[0] content with [1], at
this point we will have mdz + pere +  vagrant in place. It will be the
pkg-ltsp start point in terms of repository;

* Time to branch out from pkg-ltsp, apply your changes and keep the
things going;

* We will be able to release the first pkg-ltsp upload here, after
keep the repository in shape and import back minor changes (if
needed);

Things to consider after the first ltsp upload under pkg-ltsp:

* ogra changes. We need to hear his feedback, and see what we can
merge back from his branches

* pqm[2]. Each person involved will maintain at least one branch and
we will have a central one at alioth, it would be good use a patch
queue manager. The main idea behind that, is ask for merges by mail,
and let the script handle some of the workload in the central
repository.

[0] = bzr get http://pkg-ltsp.alioth.debian.org/bzr/main
[1] = http://projetos.ossystems.com.br/~otavio/bzr/ltsp/for-merge
[2] = http://people.ubuntu.com/~robertc/pqm/trunk/

Please, reply this message with your suggestions, expectations,
whatever... I really want feedback, we're a team just starting up,
there are no dictators here. :)

--
Gustavo Franco



More information about the Pkg-ltsp-devel mailing list