On 04/08/2012 03:13 PM, Gerardo Exequiel Pozzi wrote:

On 04/08/2012 01:02 PM, Dieter Plaetinck wrote:

...

http://releng.archlinux.org/isos/2012.04.08_15-47-01-testing/

the testbuild versions will now also have the suffix -testing if they were built with testing enabled.

Dieter

Ok.

then I push the patch to support boot via "El Torito" (EFI) in archiso (master)?

I think that can be a good idea to make a new branch in archiso named "testing" that must be used when [testing] repo is enabled. Many times, I made patches for changes due new packages, but I not pushed to master branch until these packages hits [core]/[extra]. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

On 04/08/2012 06:57 PM, Dieter Plaetinck wrote:

On Sun, 08 Apr 2012 15:22:59 -0300 Gerardo Exequiel Pozzi wrote:

...

On 04/08/2012 03:13 PM, Gerardo Exequiel Pozzi wrote:

...

On 04/08/2012 01:02 PM, Dieter Plaetinck wrote:

...

http://releng.archlinux.org/isos/2012.04.08_15-47-01-testing/

the testbuild versions will now also have the suffix -testing if they were built with testing enabled.

Dieter

Ok.

then I push the patch to support boot via "El Torito" (EFI) in archiso (master)?

I think that can be a good idea to make a new branch in archiso named "testing" that must be used when [testing] repo is enabled.

Many times, I made patches for changes due new packages, but I not pushed to master branch until these packages hits [core]/[extra].

I'm wondering what the simplest approach is to achive our goals. Maybe what you said, but I would name the branch "develop" (aif also uses that). whatever(?) Dieter

Well, the thing is that "develop" name does not reflect what I want: stable patches for use in with [testing] repo to avoid broken things (for example, the last commit [#1]) I normally push my patches to github on "djgera" branch, patches they needs [testing], and will go to master very soon. (in other words this branch will become "testing" in main git repo (projects.archlinux.org) My branch "experimental" (github) is re-based on "djgera", and this is what you call "develop", this branch many times includes things that needs building packages yourself (mostly mkinitcpio in old days, but in these days mkinitcpio has a fast release-cycle). Other branchs can exists on github (like now "efi_stub" [#2], and in the past has been "pxe_curl", "dm_snapshot", etc...) but that is another history, they are re-re-re-based until gets nice "shape". [#1] https://projects.archlinux.org/archiso.git/commit/?id=fbb6272b86b06888a1a82b... [#2] https://github.com/djgera/archiso/compare/master...efi_stub -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

On Mon, 9 Apr 2012 09:29:28 +0200 Dieter Plaetinck wrote:

On Sun, 08 Apr 2012 20:14:04 -0300 Gerardo Exequiel Pozzi wrote:

...

On 04/08/2012 06:57 PM, Dieter Plaetinck wrote:

...

On Sun, 08 Apr 2012 15:22:59 -0300 Gerardo Exequiel Pozzi wrote:

...

On 04/08/2012 03:13 PM, Gerardo Exequiel Pozzi wrote:

...

On 04/08/2012 01:02 PM, Dieter Plaetinck wrote:

...

http://releng.archlinux.org/isos/2012.04.08_15-47-01-testing/

the testbuild versions will now also have the suffix -testing if they were built with testing enabled.

Dieter

Ok.

then I push the patch to support boot via "El Torito" (EFI) in archiso (master)?

I think that can be a good idea to make a new branch in archiso named "testing" that must be used when [testing] repo is enabled.

Many times, I made patches for changes due new packages, but I not pushed to master branch until these packages hits [core]/[extra].

I'm wondering what the simplest approach is to achive our goals. Maybe what you said, but I would name the branch "develop" (aif also uses that). whatever(?) Dieter

Well, the thing is that "develop" name does not reflect what I want: stable patches for use in with [testing] repo to avoid broken things (for example, the last commit [#1])

I normally push my patches to github on "djgera" branch, patches they needs [testing], and will go to master very soon. (in other words this branch will become "testing" in main git repo (projects.archlinux.org) My branch "experimental" (github) is re-based on "djgera", and this is what you call "develop", this branch many times includes things that needs building packages yourself (mostly mkinitcpio in old days, but in these days mkinitcpio has a fast release-cycle). Other branchs can exists on github (like now "efi_stub" [#2], and in the past has been "pxe_curl", "dm_snapshot", etc...) but that is another history, they are re-re-re-based until gets nice "shape".

[#1] https://projects.archlinux.org/archiso.git/commit/?id=fbb6272b86b06888a1a82b... [#2] https://github.com/djgera/archiso/compare/master...efi_stub

makes sense. do what you think makes most sense. but make sure there's one location that has all branches/patches (testing,experimental,...) so that i can easily switch between branches. (with aif, i always push to both github and projects.archlinux.org)

also, the arch releng environment should probably always use the experimental (develop) branch, so we can quickly test new features before declaring them stable (moving to master) just as i do with aif and libui-sh. in that case a 'testing' branch won't be very useful, but an experimental-testing would (new experimental features, and aimed for testing packages) you can then always rebase experimental-testing on experimental.