Hi,
the ooxml-lite module is currently not filtering correctly.
I need to fix that first before continuing with preparing the release candidate.
Andi.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional
Hi,
I'm now working on the release - please stop committing.
Andi
On 01.09.21 10:14, Sayi wrote:
Hi,
a) It’s time to release a new version and the new version solves many serious
bugs.
c) My opinion is that 5.1.0 is better.
Best regards,
Sayi
在 2021-09-01 04:28:34，"Dominik
Hi,
a) It’s time to release a new version and the new version solves many serious
bugs.
c) My opinion is that 5.1.0 is better.
Best regards,
Sayi
在 2021-09-01 04:28:34，"Dominik Stadler" 写道：
>Similar for me,
>
>a) good time roll the next release
>
>b) whatever is easier right
Similar for me,
a) good time roll the next release
b) whatever is easier right now, we can also use Ant once again if Gradle
needs a bit more work
c) I'd also opt for 5.1.0, it does not feel like big enough changes for a
major release
Dominik.
On Tue, Aug 31, 2021 at 5:08 PM Alain FAGOT
Hi,
a) many changes deserve to be released
b) up to you to estimate the benefits or the burden
c) I don't think we introduced API breaking changes, so 5.1.0 would encompass
the logging changes
Best regards,
Alain FAGOT BÉAREZ
Obter o BlueMail para Android
Em 29 de ago de 2021 21:11, em
Hi Andi,
a) I think we need a new release
b) I don't think we need to solve all the build issues before the next release
c) I'd prefer to call the next release 6.0.0 or failing that 5.1.0. The log4j
change makes calling next release 5.0.1 problematic for me.
On Sunday 29 August 2021,
Hi Devs,
a) what's your opinion about rolling the next release?
From my side, only the distsource build is not implemented in gradle and a few
of the release task need to be done manually.
b) Now that the gradle dist plugin picks up all the dependencies, how important
is the distsource
Hi,
The first link actually compared current 4.1.0 to "4.0.2-SNAPSHOT", i.e.
some intermediate version. I have now re-run the comparison against 4.0.1
(called 4.0.1RC2 in my database), results are similar, but not fully equal.
The new comparison is available at the following links:
-
When was the previous regression run?
Some of the formula errors mention invalid sheet names, including
empty strings. The fix for #60460 committed Dec. 30 handled null
sheet names in SheetNameEvaluator, but perhaps that change should also
check and handle empty strings?
I've never actually
A first run of the regression tests for Apache POI is done. It still uses
XMLBeans 3.0.2, I will re-run a 2nd time later when we have XmlBeans 3.0.3
final available.
There are new failures with a high amount of failing documents compared to
4.0.x, however these are caused by the addition of a
Hi Greg,
> 1. what work remains before releasing a new XMLBeans?
I'm not committing to trunk currently, but to a branch. I'm not planning to
include my changes in the current release, as I haven't tested them yet
thoroughly.
> 2. How do I build, tag, and release XMLBeans?
tag: via svn
OK, I think I'm reasonably familiar now with the POI release build
process, thank you to all who have contributed to the detailed
release-guide.txt.
However, there is no such document I can find for XMLBeans, and it
sounds like there may be an open question or two there?
Further, if I'm reading
I've dropped the xmlbeans staging jars.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail:
On 18.03.19 06:11, Greg Woolsey wrote:
> I've not done a release yet, but I'd be willing to read the docs and
> take a stab at it if no one else has time.
Regarding POI:
After setting up the environment - its merely calling the release-prep* scripts.
I haven't yet updated the link to
che_xmlbeans to a real package and being
> compatible to former releases - and it gives me a bit of a hard time.
>
> But nevertheless we might want push the next release for POI and XmlBeans.
>
> I'm busy next week, but could take care about the releases the week
> afterwards.
>
&
tible to former releases - and it gives me a bit of a hard time.
> >
> > But nevertheless we might want push the next release for POI and
> XmlBeans.
> >
> > I'm busy next week, but could take care about the releases the week
> afterwards.
> >
> > How is everyon
resources from /schemaorg_apache_xmlbeans to a real package and being
> compatible to former releases - and it gives me a bit of a hard time.
>
> But nevertheless we might want push the next release for POI and XmlBeans.
>
> I'm busy next week, but could take care about the releases t
17 matches
Mail list logo
