3.10.0 release

[Ken Murchison]

On 4/11/21 4:53 PM, Allen Winter wrote:
> On Sunday, April 4, 2021 11:32:11 AM EDT Allen Winter wrote:
>> Any objections if I release 3.10.0 in the next few days?
>>
> Since the 3.0 is a mess  I gave up in there and started a new branch 3.0.10
>
> I believe 3.0.10 now contains all the appropriate commit except these:
> 6c7dab5e33824170f8b0af9007f7f0c3a3ce10f icalrecur.c: reorder the rrule parts when creating the string
> 45119708f25633ad5dcf8f17e79a59321b240ac5 regression.c: fixed tests to use new ordering of RRULE parts
> 98761e2709de98d16f229dbeed05f119c61f0a6e icalrecur.c: fix placement of ';' following RSCALE/SKIP
> e976e4bcca85d37ade3279428476e0b7d1f28fa2 icalrecur.c: order BY* parts per the processing order in Section
> 05d275332673abc624b645541d86ddb3a979f6bd  src/test/libical-glib/comprehensive.py - fix parameter order
>
> these changes to icalrecur would not apply cleanly and will need some by-hand attention.
> they contain new symbols as well, which I would rather not have at this late stage in 3.0
>
> @Ken: could you look in the 3.0.10 branch and see what you can do about implementing these
> changes to the RRULE stuff?  if not critical, we could consider not including them in the 3.0.10 release


The ordering of the RRULE parts is not critical.  I only reordered them 
for mostly aesthetic reasons, and to help me compare VTIMEZONE when 
diagnosing the icaltzutil issues generating VTIMEZONE.

That said, I'm attending the virtual CalConnect conference this week, 
but will take a look at 3.10.0 during some breaks.


>
> Once we clean up the icalrecur changes I will roll back the 3.0 branch to the last tag and then merge 3.0.10
>
> @all: I would appreciate any testing you can do in the 3.0.10 branch
>
> -Allen
>
>
>
>
>
>
>
>
> _______________________________________________
> libical-devel mailing list
> libical-devel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/libical-devel

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC