Path to release - Githubissues

jperon / lyluatex

Alternative à lilypond-book pour lualatex

MIT License

58 stars 12 forks source link

Path to release #143

Closed uliska closed 6 years ago

uliska commented 6 years ago

I think we are nearly at the point of preparing a release (supposing there will be no major issues with #142).

How are we going to proceed? My suggestion is a three-step path (after merging of that PR):

Ask people to test from Github, with particular focus also on the manual (that it is understandable, complete and consistent with the actual behaviour).
This can be requested on mailing lists, and I'd suggest to ask some people personally
When that is complete make a "1.0 beta" release on CTAN
After some time make a 1.0 release on CTAN

jperon commented 6 years ago

OK for me, but after merging #142, I'd like to make some optimizations I had in mind, but I delayed to avoid merge conflicts.

uliska commented 6 years ago

I think now that I found my mistake responsible for #174 we're at the point where we can ask the community for review and testing, isn't it? The only thing that should be added to the manual IMHO is #168, but that can easily be done at some point before uploading to CTAN.

uliska commented 6 years ago

Mailing lists to be notified:

[x] lilypond-user
[x] tex-music
[x] tex-live
[ ] MEI (only for release info)
[ ] Tex-D-L (no idea, was a friend's suggestion)
[ ] DANTE
[x] texhax

Please add to the list and "register" before writing a post to a list.

jperon commented 6 years ago

@uliska Would you mind making the notifications ? I'm very busy at work ATM, so it will be quite complicated for me.

uliska commented 6 years ago

Ok, I'll do so for the lists I'm subscribed to and ask (or rather allow) the friend to forward to the remaining two.

uliska commented 6 years ago

https://github.com/jperon/lyluatex/issues/177 (as a link to be included in mailing list posts)

uliska commented 6 years ago

We didn't receive any confirmations but also no objections. So I think we could now prepare the upload to CTAN. I think #168 can be investigated between the beta and the final release, we should just fix the "issue" with straight quotes in the manual (as commented in #177).

What do you think, @jperon ? Does the Makefil have to be updated for this? Would you do that?

jperon commented 6 years ago

That's now ready in #179.