Release 1.10.2 #133
Release 1.10.2 #133
Conversation
Disable generate-app-package, install-node, install-appdmg and exec-appdmg executions.
It was already commented out, see d706242
- org.apache.felix.main 5.6.2 - org.apache.felix.src 2.0.8 In addition, org.osgi.enterprise has been updated to 5.0.0 in framework BoM. This seems to have fixed the launch issue daisy/pipeline-mod-braille#135.
Essentially:
As said above, one for each major OS (using the assembly profiles).
I would upload directly to GitHub. If/when we want to tests it before, I'd simply ask people to build their own packages with the assembly (the fixed versions are staged, so it should be the same package as you build).
If it's a proper public RC, yes. And I'd publish as a GitHub release with a "pre-release" flag. If it's just for our own internal tests, I'd do as described above.
I think I did both ways in the past (i.e. with the release plugin or manually). But in any case I don't push the artifacts to Maven Central (I may have added POM code to disable pushing these, not sure).
I don't think we had the case already. I wouldn't update the descriptor for the RC. |
bertfrees
force-pushed
the
release/1.10.2
branch
from
16e4caa
to
8e13174
Compare
bertfrees
force-pushed
the
release/1.10.2
branch
from
8e13174
to
bd92f57
Compare
src/main/resources/README.txt
Outdated
| - daisy202-validator | ||
| - [FIX] Attribute "shape" not allowed here | ||
| - Braille modules | ||
| - Improve launch-time stability |
There was a problem hiding this comment.
This makes it look like it was a problem in the braille modules. The problem was indeed noticed only in the braille modules for some reason, but the fix had nothing to do with the braille modules.
There was a problem hiding this comment.
Right. Moved that under the "Framework" section.
src/main/resources/README.txt
Outdated
| ### Modules | ||
|
|
||
| - Add basic tests for all scripts | ||
| - Re-enable all XSpec and and XProcSpec tests |
There was a problem hiding this comment.
These two are not relevant for users, maybe move to the maintainer section below?
There was a problem hiding this comment.
OK, moved that in the "build maintenance" section.
There was a problem hiding this comment.
OK. But I meant also the line above ;)
There was a problem hiding this comment.
yeah, not quite sure. Knowing that there are tests is useful and reassuring for users. Knowing that they're in XSpec and XProcSpec is more a developer things... 🤔
src/main/resources/README.txt
Outdated
| - [FIX] problem finding lame | ||
| - Utility modules | ||
| - [fileset-utils] change the actual base URI of documents in `px:fileset-load` | ||
| - [FIX] Circular dependency between `fileset-utils` and `mediatype-utils` |
There was a problem hiding this comment.
Same comment regarding relevancy to users.
There was a problem hiding this comment.
I removed the line, since it can be seen as part of the "Cleanup dependencies" entry.
| - [FIX] The "assert validity" option on dtbook-to-epub3 does not seem to work | ||
| - daisy202-validator | ||
| - [FIX] Attribute "shape" not allowed here | ||
| - Braille modules |
There was a problem hiding this comment.
Much more has happened since v1.10.0, but you probably didn't find all of the changes because not all of them have pull requests. By the way also things have happened between v1.10.0 and v1.9.16 of the braille modules which aren't in the release notes. (EDIT: Actually not much has happened between v1.9.16 and v1.10.0 after all, only documentation.)
There was a problem hiding this comment.
I'll create the release notes for the braille modules.
There was a problem hiding this comment.
Took me a while to find out what all the changes were about again and to summarize them. I'm more or less finished now but will push it somewhere tomorrow.
|
Merged in master. |
@rdeltour All the artifacts are staged. What is left to do now is to build the various packages. What is usually your workflow for that? Which packages do you build? Where do you upload a RC? Do you give the RC a non-snapshot version? Do you use the release plugin for the assembly? Do you update the release descriptor for the updater also for the RC?
These instructions could also go into the "super release script" I have made.
I have built the Windows ZIP, the EXE, the Mac OS ZIP, the DMG, the Linux ZIP, and the DEB.
This can definitely be made easier. Building them all at the same time is not possible, but when you try to build them one by one you end up building things more than once. This is part of #75.
I hope I got everything right. You normally do this, and different machines may give different results. But I guess we'll find out when testing.
Depends on: