Re: [AD] 4.2.2 schedule

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


Phew!  Allegro releases and versioning is all very complex!

On 19/06/2007, you wrote:
> 
>> Ok.  So I guess you will put it under the 4.2.1 branch for now?
>
> 4.2.1 is a release, not a branch, so no.  I think the options are:
>
> - If we plan to make a 4.2.3 release with the Amiga port:
>
>     (1) You commit your changes and continue to work in the 4.2 branch.
>     If your changes are not disruptive (which they shouldn't be), there
>     may be code for an Amiga port ending up in the 4.2.2 release, but
>     that's okay.
>
>     (2) Create a branch for making the 4.2.2 release ('release
>     engineering').  Meanwhile you work on the 4.2 trunk.  Once 4.2.2 is
>     released, we merge back.
>
>     (3) As in (2) but the other way around.
>
> - If we don't plan to make a 4.2.3 release with the Amiga port:
>
>     (4) Create the 4.3 branch now.  You commit your work into the 4.3
>     branch, and we merge from 4.2 to 4.3 later.
>
>     (5) Wait until 4.2.2 is released, then create the 4.3 branch.  It
>     saves a tiny bit of merging work but you have to wait.
>
> I think we have to let the 4.2 branch die after 4.2.2, otherwise bug
> fixes will need to be committed to three branches at once.  And I think
> very few people will care about an Amiga port, so it'll be fine if they
> have to download an "unstable" 4.3.x release if they want to try it in
> the near future.  So, (4) or (5).  It's up to you.  I'd pick (4).

Ok, given that the Amiga port is 90% done but probably won't make a 4.2.2 or
4.2.3 release, I would be inclined to release a 4.3 release (which if I
understand is 4.2 + Allegro GL backported?).  And I see that you are still
working on the 4.2 trunk.  Given that the Amiga port is quite unobtrusive
(really at this point it is just the contents of the src/amiga directory) I
would be inclined to just add that to svn, and then I can submit a couple
of small patches required.

If when you release 4.2.2 etc. the Amiga port is finished then great, it's
supported.  Otherwise it's just some bonus code in src/amiga.  But in the
meantime I don't think its a big enough deal to be creating branches for.

Comments?

-- 
/-------------------------------------------------------------------\
[Hitman/Code HQ - 6502/z80/68000/604e/80x86/ARM coder - Amiga rulez!]
[VZ-200/VIC-20/MZ-700/c16/c64*10/c128*8/Plus-4/CPC464/CD32/500*2    ]
[600/1000/1200*2/A4000/SNES/N64/Dreamcast/Athlon 1100/AmigaOne      ]
[Assembly Language: The most fun you can have with your clothes on! ]
\-------------------------------------------------------------------/





Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/