Discussion:
Bug#932853: please someone "git checkout -b bullseye && git push"
Add Reply
Tomas Pospisek
2019-07-23 22:40:01 UTC
Reply
Permalink
Package: release-notes
Severity: wishlist

I have considered forking and branching via Salsa, and then sending the
pull request, but that's not less work. So I'm very kindly asking, if
someone with commit rights could please do a

git checkout -b bullseye && git push

So other then can maybe start forking on that branch and sending
patches/pull requests for already coming in bullseye changes:

#841666, #931785, #932580

Gracias,
*t

-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_CH.utf8, LC_CTYPE=de_CH.utf8 (charmap=UTF-8), LANGUAGE=de_CH:de (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Paul Gevers
2019-07-24 06:30:01 UTC
Reply
Permalink
Control: owner -1 !

Hi Tomas,

Thanks a lot that you already want to start working on the bullseye
release-notes.
Post by Tomas Pospisek
I have considered forking and branching via Salsa, and then sending the
pull request, but that's not less work. So I'm very kindly asking, if
someone with commit rights could please do a
git checkout -b bullseye && git push
So other then can maybe start forking on that branch and sending
#841666, #931785, #932580
I would wait with bugs like 841666 until it's clear that we actually
want that (at that time). And for bug 932580 it's too early to know what
should be in the text, so we should really defer that to later in the cycle.

That said, I want to prepare a proper branch (with some reworking and
some pruning), so I'll do just this, but not right *now* (there's other
stuff higher on my TODO list). Please, feel free to already propose
text, as that is the hardest part of nearly all release-note bugs.

Paul
Andrei POPESCU
2019-07-24 19:40:01 UTC
Reply
Permalink
Post by Paul Gevers
That said, I want to prepare a proper branch (with some reworking and
some pruning), so I'll do just this, but not right *now* (there's other
stuff higher on my TODO list). Please, feel free to already propose
text, as that is the hardest part of nearly all release-note bugs.
I would like to use this opportunity to propose that for bullseye the
Release Notes should be switched from DocBookXML to reStructuredText.

Reasons:

1. Easier to write due to the lighter markup

2. Easier to translate due to the lighter markup

There are entire strings where translators have to navigate between
the markup.

3. Modern toolchain

4. Transition recently done by Debian Policy and Developer's Reference

While the Release Notes do have significantly more translations,
large parts of it are not reusable between releases.


Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Paul Gevers
2019-07-24 20:10:01 UTC
Reply
Permalink
Hi,
Post by Andrei POPESCU
I would like to use this opportunity to propose that for bullseye the
Release Notes should be switched from DocBookXML to reStructuredText.
I don't think I disagree, as I though about this myself already, but I
don't have the energy to drive this. However, if there are volunteers, I
*think* I welcome this. (As long as translations are saved as much as
possible).

Paul
Andrei POPESCU
2019-07-25 06:50:01 UTC
Reply
Permalink
Control: clone -1 -2
Control: severity -2 wishlist
Control: retitle -2 Please migrate Release Notes to reStructuredText
Post by Paul Gevers
Hi,
Post by Andrei POPESCU
I would like to use this opportunity to propose that for bullseye the
Release Notes should be switched from DocBookXML to reStructuredText.
I don't think I disagree, as I though about this myself already, but I
don't have the energy to drive this. However, if there are volunteers, I
*think* I welcome this. (As long as translations are saved as much as
possible).
Ok, I'll have a look at it, though I wouldn't mind if someone is faster
;)

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Osamu Aoki
2019-07-25 13:50:01 UTC
Reply
Permalink
Hi,
Post by Andrei POPESCU
Control: clone -1 -2
Control: severity -2 wishlist
Control: retitle -2 Please migrate Release Notes to reStructuredText
Post by Paul Gevers
Hi,
Post by Andrei POPESCU
I would like to use this opportunity to propose that for bullseye the
Release Notes should be switched from DocBookXML to reStructuredText.
I don't think I disagree, as I though about this myself already, but I
don't have the energy to drive this. However, if there are volunteers, I
*think* I welcome this. (As long as translations are saved as much as
possible).
Yes. It can be done. I just converted developers-reference and someone
merged it ti main ;-)

If you follow my commit history, all tools and tricks are there.

https://salsa.debian.org/debian/developers-reference

I will work on build script more to make web page looks better. But
source conversion was possible though it is non-trivial.
Post by Andrei POPESCU
Ok, I'll have a look at it, though I wouldn't mind if someone is faster
;)
https://salsa.debian.org/debian/developers-reference/blob/1b0940a5c2879a5be3100b0e0f2bee6c5de58bdf/README.rst

This describes general tasks involved.

If someone makes broken PO file by copying some msgstr from random
msgstr, then conversion doesn't work well and it may be cryptic to
debug.

Regards,

Osamu
Paul Gevers
2019-12-01 19:40:02 UTC
Reply
Permalink
Hi Andrei,
Post by Osamu Aoki
Yes. It can be done. I just converted developers-reference and someone
merged it ti main ;-)
If you follow my commit history, all tools and tricks are there.
https://salsa.debian.org/debian/developers-reference
I will work on build script more to make web page looks better. But
source conversion was possible though it is non-trivial.
Post by Andrei POPESCU
Ok, I'll have a look at it, though I wouldn't mind if someone is faster
;)
https://salsa.debian.org/debian/developers-reference/blob/1b0940a5c2879a5be3100b0e0f2bee6c5de58bdf/README.rst
This describes general tasks involved.
If someone makes broken PO file by copying some msgstr from random
msgstr, then conversion doesn't work well and it may be cryptic to
debug.
Are you still upto doing this change? I'm not expecting you worked on
this recently, but now is a good time to get this on the rails. Should
we first branch bullseye (bug #932853), make the relatively small fixes
there and then work on that branch or do you have a different proposal?

Paul
Andrei POPESCU
2019-12-01 23:40:02 UTC
Reply
Permalink
Post by Paul Gevers
Hi Andrei,
Post by Osamu Aoki
Yes. It can be done. I just converted developers-reference and someone
merged it ti main ;-)
If you follow my commit history, all tools and tricks are there.
https://salsa.debian.org/debian/developers-reference
I will work on build script more to make web page looks better. But
source conversion was possible though it is non-trivial.
Post by Andrei POPESCU
Ok, I'll have a look at it, though I wouldn't mind if someone is faster
;)
https://salsa.debian.org/debian/developers-reference/blob/1b0940a5c2879a5be3100b0e0f2bee6c5de58bdf/README.rst
This describes general tasks involved.
If someone makes broken PO file by copying some msgstr from random
msgstr, then conversion doesn't work well and it may be cryptic to
debug.
Are you still upto doing this change? I'm not expecting you worked on
this recently, but now is a good time to get this on the rails. Should
we first branch bullseye (bug #932853), make the relatively small fixes
there and then work on that branch or do you have a different proposal?
As mentioned before, this is something I would be interested to work on,
assuming I find the time for it.

In any case, if someone else is interested please go for it.

Regarding branches, wouldn't it make more sense to create a buster
branch and continue work on master? Just asking, I'm fine either way.

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Paul Gevers
2019-12-03 20:40:02 UTC
Reply
Permalink
Hi Andrei,
Post by Andrei POPESCU
As mentioned before, this is something I would be interested to work on,
assuming I find the time for it.
Ack.
Post by Andrei POPESCU
In any case, if someone else is interested please go for it.
Regarding branches, wouldn't it make more sense to create a buster
branch and continue work on master? Just asking, I'm fine either way.
Of course, that's what I meant. I did that in the mean time and master
is now free to start working on this transition to reStructeredText.

Paul

Paul Gevers
2019-12-02 21:20:02 UTC
Reply
Permalink
Control: tags -1 pending

Hi,
Post by Tomas Pospisek
Package: release-notes
Severity: wishlist
I have considered forking and branching via Salsa, and then sending the
pull request, but that's not less work. So I'm very kindly asking, if
someone with commit rights could please do a
git checkout -b bullseye && git push
So other then can maybe start forking on that branch and sending
#841666, #931785, #932580
I have requested [1] the webmaster-team to start building the buster
release notes from the buster branch I just created and pushed. Please
wait with making bullseye changes to the master branch until the request
is merged. I intent to upload the first changes with some clean-up,
which is hopefully helpful for the restructuring as there should be less
to restructure.

Paul

[1] https://salsa.debian.org/webmaster-team/cron/merge_requests/4
Loading...