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 the emails correctly, there are changes to
XMLBeans that should be released first, so that POI can be updated to
use that new version before building a POI release candidate.  Is that
correct?

So, my questions, for timing and completeness, are:

1. what work remains before releasing a new XMLBeans?
2. How do I build, tag, and release XMLBeans?
3. What version numbers do we want to use?  These seem to be the next ones up:
   - XMLBeans 3.0.3
   - POI 4.1.0

I'm sure there will be more, not having driven a release before, and
experiencing a high "don't screw this up" quotient :)

Greg

On Mon, Mar 18, 2019 at 12:47 PM Andreas Beeker <[email protected]> wrote:
>
> 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 commons-openpgp - the current snapshot 
> version should be compatible to the current bouncycastle jar.
>
>
> Regarding XmlBeans:
>
> I've started to modify the build to include the maven pom on my branch,
> but for trunk you need to download a recent pom.xml and update the 
> information manually,
>
> @PJ: since 19.01.19 there's xmlbeans nexus upload lingering around - maybe 
> you want to drop it?
>
>
> For both projects, you should be able to access the nexus staging areas:
> http://repository.apache.org
> -> login with your Apache credentials
> -> Staging profiles : should contain xmlbeans and poi entries
>
> Andi
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to