Making a 3.2.2 release

[Roger Leigh]

Hi folks,

Since the 3.2.1 release on the 1st of March there have been a few changes:

- documentation of a security advisory
- explicit export of ArrayJanitor templates
- addition of an optional C++11 mutex manager
- restoring the use of a resource file when building Windows DLLs
- a couple of minor cmake build fixes
- removing fixed CURL timeout

https://issues.apache.org/jira/projects/XERCESC/versions/12342890

Would it be appropriate to make a new point release at this time to
publish these accumulated fixes? Are there any other outstanding issues
which also need addressing for 3.2.2?


Thanks,
Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org

[Cantor, Scott]

Post by Roger Leigh
Would it be appropriate to make a new point release at this time to
publish these accumulated fixes? Are there any other outstanding issues
which also need addressing for 3.2.2?

Generally speaking my time is limited to issues necessary to support my project, but given that I don't even need to actually ship this version if you need my "access" to get the release uploaded (I can't recall exactly what part I had to take on for 3.2.1), I should be able to find enough time for that.

If you don't have access to the dev dist repo, I can generate a release and stage it there if you get the docs and version numbers all updated.

-- Scott


B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB��[��X��ܚX�KK[XZ[��Y]�][��X��ܚX�P\��\˘\X�K�ܙ�B��܈Y][ۘ[��[X[��K[

[Roger Leigh]

Post by Cantor, Scott

Post by Roger Leigh
Would it be appropriate to make a new point release at this time to
publish these accumulated fixes? Are there any other outstanding issues
which also need addressing for 3.2.2?

Generally speaking my time is limited to issues necessary to support my project, but given that I don't even need to actually ship this version if you need my "access" to get the release uploaded (I can't recall exactly what part I had to take on for 3.2.1), I should be able to find enough time for that.
If you don't have access to the dev dist repo, I can generate a release and stage it there if you get the docs and version numbers all updated.

I'm not sure if I do or do not have access. I'm not familiar with the
steps to take to actually make a release, I'm afraid. (But I'm happy to
learn if it would help.)

I have made the necessary changes for 3.2.2 in SVN r1840430. I don't
think any additional changes need making, but if you could have a check
over it that would certainly be appreciated.


Thanks,
Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org

[Cantor, Scott]

Post by Roger Leigh
I'm not sure if I do or do not have access. I'm not familiar with the
steps to take to actually make a release, I'm afraid. (But I'm happy to
learn if it would help.)

http://svn.apache.org/viewvc/xerces/c/admin/release-procedure.txt

Some of it's out of date again because of the additional version handling you added, but you could probably update that file.

I doubt you have access to these repos, but you could do a quick test commit to check:

https://svn.apache.org/repos/asf/xerces/site/trunk/production/xerces-c

https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/

https://dist.apache.org/repos/dist/release/xerces/c/3/sources/

Post by Roger Leigh
I have made the necessary changes for 3.2.2 in SVN r1840430. I don't
think any additional changes need making, but if you could have a check
over it that would certainly be appreciated.

I believe you'll need to update the release information pages inside the site. Build the site from your sandbox and grep for 3.2.1 and you'll find the pages I think.

I will build a RC and upload it to dist/dev for a vote.

-- Scott



---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-m

[Roger Leigh]

Post by Cantor, Scott

Post by Roger Leigh
I'm not sure if I do or do not have access. I'm not familiar with the
steps to take to actually make a release, I'm afraid. (But I'm happy to
learn if it would help.)

http://svn.apache.org/viewvc/xerces/c/admin/release-procedure.txt
Some of it's out of date again because of the additional version handling you added, but you could probably update that file.

Done. I've dropped the files which required updating, but which are now
automatically generated or no longer needed. And I've updated the
documentation generation instructions which are now done via regular
build targets rather than a shell script.

Post by Cantor, Scott
https://svn.apache.org/repos/asf/xerces/site/trunk/production/xerces-c

I have access to this one.

Post by Cantor, Scott
https://dist.apache.org/repos/dist/dev/xerces/c/3/sources > https://dist.apache.org/repos/dist/release/xerces/c/3/sources/

I have no access to these two.

Post by Cantor, Scott

Post by Roger Leigh
I have made the necessary changes for 3.2.2 in SVN r1840430. I don't
think any additional changes need making, but if you could have a check
over it that would certainly be appreciated.

I believe you'll need to update the release information pages inside the site. Build the site from your sandbox and grep for 3.2.1 and you'll find the pages I think.

So the procedure here is to copy doc/html/* to site/ and then commit the
changes?

According to the release procedure, this should be done last of all?
Looks like I could potentially do this step, but should wait on approval
and completion of the other release steps before doing so?


Regards,
Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org

[Cantor, Scott]

Post by Roger Leigh
So the procedure here is to copy doc/html/* to site/ and then commit the
changes?

Yes, that's the final step since that updates the download links and such.

Post by Roger Leigh
According to the release procedure, this should be done last of all?
Looks like I could potentially do this step, but should wait on approval
and completion of the other release steps before doing so?

Yes, I can upload the sources once they're voted out.

If you have the site files more or less correct I can do a build this afternoon. I'm going to make one change to the doxygen files, I want to add a warning to a method that's not implemented correctly that is confusing a number of people.

-- Scott



---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-m

[Roger Leigh]

Post by Cantor, Scott

Post by Roger Leigh
So the procedure here is to copy doc/html/* to site/ and then commit the
changes?

Yes, that's the final step since that updates the download links and such.

Post by Roger Leigh
According to the release procedure, this should be done last of all?
Looks like I could potentially do this step, but should wait on approval
and completion of the other release steps before doing so?

Yes, I can upload the sources once they're voted out.
If you have the site files more or less correct I can do a build this afternoon. I'm going to make one change to the doxygen files, I want to add a warning to a method that's not implemented correctly that is confusing a number of people.

I don't have any further changes to make. I think all the changes of
version information and release information in parts (1) and (2) of the
release procedure are complete. I've tested (3) and (4).


Regards,
Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org

[Cantor, Scott]

Didn't get to it until tonight.

https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/

If that looks good, I'll call for a vote tomorrow.

-- Scott



---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-m

[Roger Leigh]

Post by Cantor, Scott
Didn't get to it until tonight.
https://dist.apache.org/repos/dist/dev/xerces/c/3/sources/
If that looks good, I'll call for a vote tomorrow.

I found a missing file which wasn't included in EXTRA_DIST, which broke
building on Windows from the release zip (version.rc.cmake.in). I've
included it, tested locally with VS2017, and commited to SVN. If you
could recreate the dev release files, I'll retest again.


Regards,
Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org

[Cantor, Scott]

I've uploaded an RC2 build (named appropriately this time) for eval, same spot.

-- Scott




---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-m

[Roger Leigh]

Post by Cantor, Scott
I've uploaded an RC2 build (named appropriately this time) for eval, same spot.

Thanks. I've given this one a test on Windows, and it's now building
fine.

I've also now been able to fix XERCESC-2153 which was minor but
annoying. If you could possibly make an RC3 with this included, that
should be the last thing from me for the release, and it should be ready
to go.

Thanks,
Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org

[Cantor, Scott]

RC3 is now up. I'll wait a bit for any final checks and then call a vote.

-- Scott


Т���������������������������������������������������������������������ХF�V�7V'67&�&R�R���â2�FWb�V�7V'67&�&T�W&6W2�6�R��&pФf�"FF�F����6����G2�R�

[Roger Leigh]

Post by Cantor, Scott
RC3 is now up. I'll wait a bit for any final checks and then call a vote.

Thanks. I've tested these with:

Linux (Ubuntu 18.04)

autotools / make (pass)
cmake / make (pass)
cmake / ninja (pass)

Windows (10 x64, VS2017)

cmake / ninja debug (pass)
cmake / msbuild release (pass)
cmake / msbuild debug (pass)

Where a pass is building and passing all the tests. Tests also run in
parallel across the board with no problems.

All GPG signatures are OK as well.

No problems seen on my side, so I think this rc3 is fine.


Regards,
Roger

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-***@xerces.apache.org
For additional commands, e-mail: c-dev-***@xerces.apache.org