[Debian-olpc-devel] How _should_ we import new changes into git?
dr at jones.dk
Tue Jan 13 22:20:25 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, Jan 13, 2009 at 04:52:55PM -0500, Luke Faraone wrote:
>On Tue, Jan 13, 2009 at 12:06 PM, Jonas Smedegaard <dr at jones.dk> wrote:
>> Or do you propose that we, if following only a single branch, follow
>> the newest upstream branch no matter if that is stable or unstable?
>I think at that point sugar is "stable enough" for Debian
>unstable/testing, assuming we are able to package an even release
>number by the time testing becomes the new stable.
Please note that the distro branches "unstable" and "testing" do not
hint at the quality of each package but of the distro. Each package
should be release quality at any time. Software known not to be release
quality should instead be packaged for "experimental" branch.
...which means we (at the source level at least) would need to support
multiple branches, which I do not feel ready to do yet.
I still feel that we should not currently package unstable upstream
releases. Feel free to keep throwing arguments for the opposite at me
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Debian-olpc-devel