Re: [sdcc-devel] 3.2.0 release schedule proposal

[Borut R. <bor...@gm...>]

I agree to have a release, but I'm afraid that the schedule is too tight:
- normally we have 2 weeks between RC1 and RC2 and 1 week between RC2 and
the release
- many snapshot build regression tests are failing. I think all regtests
should pass (or be excluded) before the release
- s08 and  r3ka ports are not even mentioned in the documentation
 (sdccman) and on the sdcc web pages.
- it would be fine to have a gputils release before the sdcc release in
order to avoid the problems with pic devices which are supported by sdcc
but not supported by gputils. I'll take a look to the remaining gputils
issues and make the release ASAP
- it would be also nice if someone would take a look to the bug tracker and
see if there are critical bugs which should be fixed before the release

If we are able to manage all this items (and probably also the ones that I
forgot to mention), then I would still shift the RC2 and the final release
for 1 week:

RC1: 17. Jun.
RC2: 01. Jul.
Release: 08. Jul

I agree to postpone the suggested items from SDCC 3.2.0 Tasks. What about
the others?

Borut


On Thu, May 31, 2012 at 11:34 AM, Philipp Klaus Krause <pk...@sp...> wrote:

> Dear sdcc developers,
>
> due to the many changes in sdcc since the previous release I suggest
> doing another release soon. I suggest the following schedule:
>
> Light freeze (features / optimizations require mailing list approval,
> fixes don't): 3. Jun.
> Freeze (changes require mailing list approval): 15. Jun.
> RC1: 18. Jun.
> RC2: 25. Jun.
> Release: 30. Jun.
>
> For the items currently at
> https://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.2.0%20Release
> I suggest to postpone the following if not closed by 3. Jun.:
> 2870755 Accessing the stack
> sdas merge with asxxxx 5.0
> 1710546 struct: aggregate assignment
> 674638 structures cannot be passed as function parameters
> 3326880 float classification macros
>
> Philipp
>