XMLBeans 3.1.0 candidate build

[Greg Woolsey <gr...@gmail.com>]

I have pushed xmlbeans 3.1.0 release candidate to:

https://repository.apache.org/content/repositories/staging/org/apache/xmlbeans/xmlbeans/3.1.0/

https://dist.apache.org/repos/dist/dev/poi/xmlbeans/bin
https://dist.apache.org/repos/dist/dev/poi/xmlbeans/src

This has discussed version # changes, updates to various text files that
were out of date, and packaging modifications to make it less of a change
from previous releases while still adjusting naming and folder conventions
to be more in line with POI's naming.

Should we do a formal vote, say 3 days?  If this looks good, I can release
on Monday, then later next week, once Maven artifacts are available, I can
work on a POI 4.1.0 candidate.

Greg

Re: XMLBeans 3.1.0 candidate build

[Greg Woolsey <gr...@gmail.com>]

>
>
> > It's ok, but not nice to have the bin directory in the src dist
> duplicated in (/bin, /src/shell) - we can change that on the next release.
> I still think it's better to have the shell scripts not under /bin in the
> source tree.
>
> +1
>

I agree, I didn't like it in /bin, but that's where it has been
historically for this project, and it was noted as missing when it moved to
/src/shell, so I put it back in the build.  In the next version we can make
that a prominent "feature" noted in the release docs and move it from
/bin.  Probably not used very often these days anyway.


> > I don't like to have the javadocs in the src dist, but rather would like
> to see them in bin dist.
>
> +1
>

They are in the bin dist as a JAR file.  Again these were noted as missing
from the src package, so I put them in.  I don't have a strong opinion
either way.  I don't generally use them directly, relying on IDE
integrations to display relevant docs.


> >
> > In my view, the src dist is a copy of the trunk whereas the bin dist
> contains all the compiled/generated artifacts.
>
> +1
>

Makes sense.  This particular project appears to have been a bit muddied in
it's far distant past in that regard.


> >
> > The pgp signature (*.asc) doesn't need to be check-summed - for Nexus,
> I'm not sure if they are automatically created on uploading the signature
> files.
>
> +1, it doesn’t serve any purpose I’ve only ever seen it on a single
> project in the incubator and at least on Apache dist they should be removed.
>

I agree.  I have no explanation or excuse for why I did that.  Probably a
misreading of something as I attempted to build release instructions from
scratch and crib much of the info from the POI release-guide.txt.  Will
remove them before moving to the release folder.

>
> > - the KEYS file: I'd like to have one merged KEYS file for both projects
> and use svn externals to link to the one place.
>
> Since they are both in the same dist area in on Apache then they must be
> merged or the main one has all the keys.
>
> There is one place on dist and never inside a release.
>

Yes, Dominik and I have corresponded over that a bit, as his key in
production was out of date or listed twice, depending on the file.
Something to do for the next release for sure.

Greg

Re: XMLBeans 3.1.0 candidate build

[Dave Fisher <da...@comcast.net>]

Sent from my iPhone

> On Mar 24, 2019, at 3:31 PM, Andreas Beeker <ki...@apache.org> wrote:
> 
> Hi Greg,
> 
> First of all, thank you Greg for taking the release manager role - I know it's time consuming especially in the beginning.
> 
> It's ok, but not nice to have the bin directory in the src dist duplicated in (/bin, /src/shell) - we can change that on the next release. I still think it's better to have the shell scripts not under /bin in the source tree.

+1
> I don't like to have the javadocs in the src dist, but rather would like to see them in bin dist.

+1
> 
> In my view, the src dist is a copy of the trunk whereas the bin dist contains all the compiled/generated artifacts.

+1
> 
> The pgp signature (*.asc) doesn't need to be check-summed - for Nexus, I'm not sure if they are automatically created on uploading the signature files.

+1, it doesn’t serve any purpose I’ve only ever seen it on a single project in the incubator and at least on Apache dist they should be removed.

> 
> Sorry for my late response - I've followed the discussions about the release, but was too busy/tired for a timely follow-up.
> 
> - project structure / modularization (xmlbean_xpath.jar, xmlpublic.jar, xbeans.jar, ...):
>   the source is full of modules, reflection calls and references to xbeans.jar - I feel the urge to clean up that (in my view) mess. Basically we should provide a xmlbeans.jar which contains everything and minimize reflections.
> 
> - the KEYS file: I'd like to have one merged KEYS file for both projects and use svn externals to link to the one place.

Since they are both in the same dist area in on Apache then they must be merged or the main one has all the keys.

There is one place on dist and never inside a release.

Regards,
Dave

> 
> Andi.
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org

Re: XMLBeans 3.1.0 candidate build

[Andreas Beeker <ki...@apache.org>]

Hi Greg,

First of all, thank you Greg for taking the release manager role - I know it's time consuming especially in the beginning.

It's ok, but not nice to have the bin directory in the src dist duplicated in (/bin, /src/shell) - we can change that on the next release. I still think it's better to have the shell scripts not under /bin in the source tree.

I don't like to have the javadocs in the src dist, but rather would like to see them in bin dist.

In my view, the src dist is a copy of the trunk whereas the bin dist contains all the compiled/generated artifacts.

The pgp signature (*.asc) doesn't need to be check-summed - for Nexus, I'm not sure if they are automatically created on uploading the signature files.

Sorry for my late response - I've followed the discussions about the release, but was too busy/tired for a timely follow-up.

- project structure / modularization (xmlbean_xpath.jar, xmlpublic.jar, xbeans.jar, ...):
  the source is full of modules, reflection calls and references to xbeans.jar - I feel the urge to clean up that (in my view) mess. Basically we should provide a xmlbeans.jar which contains everything and minimize reflections.

- the KEYS file: I'd like to have one merged KEYS file for both projects and use svn externals to link to the one place.

Andi.

Re: XMLBeans 3.1.0 candidate build

[Dominik Stadler <do...@gmx.at>]

Hi Greg,

thanks a lot for the work here, hopefully we can keep the structure in
place now with only minor modifications so that future releases require
much less work.

The comparison of 3.0.2 and 3.1.0 archives now looks good, I saw one small
glitch in the doap_XMLBeans.rdf: it contains 3.0.1 twice and is missing
3.0.2, but I don't think we need to respin the release just because of this.

Yes, please call a formal vote with [VOTE] in the subject for the release
to be officially signed off by the POI PMC.

Thanks... Dominik.

On Fri, Mar 22, 2019 at 11:39 PM Greg Woolsey <gr...@gmail.com>
wrote:

> I have pushed xmlbeans 3.1.0 release candidate to:
>
>
> https://repository.apache.org/content/repositories/staging/org/apache/xmlbeans/xmlbeans/3.1.0/
>
> https://dist.apache.org/repos/dist/dev/poi/xmlbeans/bin
> https://dist.apache.org/repos/dist/dev/poi/xmlbeans/src
>
> This has discussed version # changes, updates to various text files that
> were out of date, and packaging modifications to make it less of a change
> from previous releases while still adjusting naming and folder conventions
> to be more in line with POI's naming.
>
> Should we do a formal vote, say 3 days?  If this looks good, I can release
> on Monday, then later next week, once Maven artifacts are available, I can
> work on a POI 4.1.0 candidate.
>
> Greg
>