appropriate options in the manual, and build it.
I have switched trixie's release-notes to this new theme, and the result
is now visible on www.debian.org/releases/trixie/release-notes.
I noticed, that the links to the previous and next chapter at the top
and the bottom of the pages are mi
[ Re-sending message; first attempt from smartphone dropped some recipients,
sorry ]
Am 24. November 2023 10:50:19 MEZ schrieb Laura Arjona Reina
:
>I've had a quick look at the theme
>inhttps://people.debian.org/~holgerw/sphinx-theme-for-debian/alabaster/release-notes/
> and l
Hello Holger
And since there has been a call for a Debian theme for Sphinx (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053549), a proposal
for that can be found at
https://people.debian.org/~holgerw/sphinx-theme-for-debian/alabaster/release-notes/
(for those, who are uncomfortable
Hi again,
Holger Wansing wrote (Mon, 13 Nov 2023 11:19:07 +0100):
> Time for a status update:
> Since the new release-notes itself are now being built on www-master (based
> on Sphinx), some changings were needed for the webpage (currently
> www.debian.org/releases/testing/
such that we can work from there (and see the results too [2]). Because
> in your worked we stopped making notes per architecture, we probably
> need to make further changes to the webmaster archive, but let's first
> build something.
Time for a status update:
Since the new rel
s
don't just work on pipewire while they do work with pulseaudio.
I think that this situation is something we can reasonably mention in
release-notes:
* There is a long transition from pulseaudio to pipewire ongoing and in
the bookworm release, users can choose with ease.
* If using gno
Hi Paul,
On Mon, May 29, 2023 at 02:36:22PM +0200, Paul Gevers wrote:
> Dear security team,
>
> I know it's a bit late, but are you aware of issues that are worth
> mentioning in the release notes from your point of view?
>
> We have updated the text about golang
Dear security team,
I know it's a bit late, but are you aware of issues that are worth
mentioning in the release notes from your point of view?
We have updated the text about golang and rustc in this cycle, chromium
got a mention about reduce support time wise and I updated the op
Package: release-notes
Hi Harald,
On 28-04-2023 16:38, Harald Dunkel wrote:
AFAIU the sssd cache becomes invalid on the upgrade to Bookworm due to a
new format. If you are using the company account to login on your laptop
you might get locked out at upgrade time. This affects FreeIPA and maybe
n.org/releases/testing/amd64/release-notes/ch-information.en.html.
Hopefully this is the right mailing list.
Regards
Harri
Dear all,
As I hope you are all aware, we are rapidly approaching of the release
of Debian 12 'bookworm'. This means that we also want to get the release
notes [1, 2] for bookworm into shape and translated.
Following the process that I proposed and used during the buster and
Hi,
Justin B Rye wrote (Sat, 1 May 2021 11:54:06 +0100):
> Holger Wansing wrote:
> > I would suggest this change:
> >
> >
> > By subscribing to the Debian announcement mailing list, you will receive
> > a
>
> I don't much like this, though I'm not sure it matters: pedantically,
> you don't
Holger Wansing wrote:
> I would suggest this change:
>
>
> By subscribing to the Debian announcement mailing list, you will receive a
I don't much like this, though I'm not sure it matters: pedantically,
you don't receive notifications by subscribing, you receive them by
being/remaining subsc
Hi,
chapter 4.3. "Preparing APT source-list files"
https://www.debian.org/releases/testing/amd64/release-notes/ch-upgrading.en.html#upgrade-process
reads:
"Debian provides two announcement mailing lists to help you stay up to date on
relevant information related to Debia
Dear all,
As I hope you are all aware, we are in the final phase of the Debian 11
'bullseye' release. This means that we also want to get the release
notes [1] for bullseye into shape and translated.
Following the process that I proposed and used during the buster
release, I p
On Mon, Mar 01, 2021 at 05:01:21PM +0200, Faidon Liambotis wrote:
>
>(I think #720989, #797342 and #819664 are probably broad enough that
>capture these concerns as well, but if folks disagree I'd be happy to
>file another bug for this.)
My hope with #819664 was to *definitely* have some pages tal
ailability in the release notes, but it's not entirely clear where it
> should go.
>
> [...]
>
> In a similar vein, Debian container base images are quite popular, and
> it would be nice to mention their availability. While they don't
> currently meet req
ailability in the release notes, but it's not entirely clear where it
> should go.
I would also like to point to
https://lists.debian.org/debian-cloud/2018/10/msg00083.html
It would make sense to discuss and publish a timeline in near future.
Best regards,
Martin
--
Martin Zobe
On 01/03/21 at 13:00 +0100, Thomas Lange wrote:
> Hi Noah,
>
> I think Ch. 3 is a good idea also adding a new section 3.2. I would
> also vote for an entry in the What's new part and adding a note for
> the Docker images. Our users want to find information about cloud and
> docker images, so we s
Hi Noah,
I think Ch. 3 is a good idea also adding a new section 3.2. I would
also vote for an entry in the What's new part and adding a note for
the Docker images. Our users want to find information about cloud and
docker images, so we should not focus on saying "we do not have
official docker im
We should be publishing release images for OpenStack and at least two
commercial cloud services approximately simultaneously with the bullseye
release. I'd like to include a short notice about cloud image
availability in the release notes, but it's not entirely clear where it
Paul Gevers wrote:
> Minor changes have been done in installing.dbk (mostly dropping text)
> and one addition in release-notes.dbk. I think we can consider this
> frozen now.
I was going to say "wait, a couple more things" - but it looks as if
all the low-priority checks I had on my TODO-list have
about.dbk, installing.dbk, moreinfo.dbk and
> release-notes.dbk have close to zero changed or added text, so if the
> previous release notes were acceptable, those files are fine already.
[...]
Minor changes have been done in installing.dbk (mostly dropping text)
and one addition in release-notes.d
On Fri, Apr 26, 2019 at 10:29:58AM +, Holger Levsen wrote:
> Also, I believe this bug should be cloned and reassigned to
> src:debian-security-support as well, so it's also documented there. Will
> do so once the bug arrives back.
done, #928027 it is.
--
tschau,
Holger
package: release-notes
x-debbugs-cc: j...@inutil.org, elb...@debian.org, t...@security.debian.org,
release-no...@packages.debian.org, debian-release@lists.debian.org
On Sat, Apr 20, 2019 at 11:07:34PM +0200, Moritz Mühlenhoff wrote:
> > Are there other concerns or warnings and
> >
Hi all,
Paul Gevers (2019-04-25):
> On 25-04-2019 08:11, Holger Wansing wrote:
> > Paul Gevers wrote:
> > First, I wonder why you ask personally me for this.
>
> Because the task was originally self-assigned to kibi and was
> documented on the wiki [1] as "ask Holger".
Right, this is entirely
aller,
> and thus is not properly documented in the installation-guide.
> However, the guide is still release-ready despite this, if you ask me.
Good to know. Thanks.
> When it comes to the release-notes, I mailed a short proposal for this to
> debian-boot weeks ago, but got no answer.
[Adding debian-boot, kibi, steve to the loop]
Hi,
Paul Gevers wrote:
> Hi Holger,
>
> We're getting closer and closer to the release of buster. We can't
> properly release without the installation guide and the Debian-installer
> release notes. To see where we stand o
help to coordinate this release's
> release-notes. In most release-notes in the past, there have been words
> about the kernel. For buster, is there anything that is worth mentioning
> in the notes?
>
> We already mention that AppArmor is pulled in via Recommends. In case
> y
Hi Holger,
We're getting closer and closer to the release of buster. We can't
properly release without the installation guide and the Debian-installer
release notes. To see where we stand on this front, I am asking you what
the status is of those documents. And just to state the obv
Hi,
> I am reaching out to you to align on the security support that users can
> expect during the lifetime of buster and how this is covered in the
> release notes.
>
> The release notes currently contain a section on "Limitations in
> security support", whic
me of buster and how this is covered in the
> release notes.
>
> The release notes currently contain a section on "Limitations in
> security support", which currently covers:
> * web browsers and their rendering engines
> * ecosystem around libv8 and Node.js
>
&
Dear kernel team,
I am reaching out to you as I help to coordinate this release's
release-notes. In most release-notes in the past, there have been words
about the kernel. For buster, is there anything that is worth mentioning
in the notes?
We already mention that AppArmor is pulled i
source packages and the concern applies to all packages shipping
- them. The concern also extends to web rendering engines not explicitely
+ them. The concern also extends to web rendering engines not explicitly
Spelling. (Also: if we're going to expect users to know that, e.g.,
Kon
s during the releasing process, so the other files make more sense
>> to check first.
>
> I had noticed some paragraphs of issues.dbk that could be improved,
> but nothing very dramatic.
>
>> The about.dbk, installing.dbk, moreinfo.dbk and
>> release-notes.dbk have clo
e more sense
> to check first.
I had noticed some paragraphs of issues.dbk that could be improved,
but nothing very dramatic.
> The about.dbk, installing.dbk, moreinfo.dbk and
> release-notes.dbk have close to zero changed or added text, so if the
> previous release notes were acc
Dear all,
As I hope you are all aware, we are in the final phase of the Debian 10
'buster' release. This means that we also want to get the release notes
for buster into shape and translated.
This is the first time that *I* am trying to coordinate this a bit, so
help me out. Hinted by
Dear release team,
I am reaching out to you to align on the security support that users can
expect during the lifetime of buster and how this is covered in the
release notes.
The release notes currently contain a section on "Limitations in
security support", which currently cove
Hello again
El 12/2/19 a las 19:35, Niels Thykier escribió:
> Niels Thykier:
> Hi,
>
> I got a reply on IRC and have now created a MR request here:
>
> https://salsa.debian.org/webmaster-team/cron/merge_requests/2
>
Merged, thanks!
I'll check the result of the next builds and when I see every
Hi
El 12 de febrero de 2019 19:16:00 CET, Niels Thykier
escribió:
>Baptiste Jammet:
>> Hello all,
>> (adding -release to Cc since they are "in charge" for the release
>notes)
>>
>> Dixit Martin Michlmayr, le 12/02/2019 :
>>
>>> Since the
Dixit Niels Thykier, le 12/02/2019 :
>Ack, lets move along with using master for buster. I have pushed a
>stretch branch now, so it can be used for the job.
Thanks.
>
>> In any case, -www should be asked to update cron/parts/7release-notes
>> to add the build for the website.
>Is there a salsa r
Niels Thykier:
> Baptiste Jammet:
>> Hello all,
>> (adding -release to Cc since they are "in charge" for the release notes)
>>
>> Dixit Martin Michlmayr, le 12/02/2019 :
>>
>>> Since the freeze has started, are there plans to get the release
Baptiste Jammet:
> Hello all,
> (adding -release to Cc since they are "in charge" for the release notes)
>
> Dixit Martin Michlmayr, le 12/02/2019 :
>
>> Since the freeze has started, are there plans to get the release notes
>> for buster published (even
Hello all,
(adding -release to Cc since they are "in charge" for the release notes)
Dixit Martin Michlmayr, le 12/02/2019 :
>Since the freeze has started, are there plans to get the release notes
>for buster published (even if only a draft)?
I think we are still trying to find
Package: release-notes
Severity: important
X-Debbugs-Cc: debian-release@lists.debian.org
Dear release team & release notes editors,
I recently received a bug report from a person using the 'iscsitarget',
which was dropped in Stretch, as it hasn't seen any update upstream
s
Baptiste Jammet:
> Hi,
> Le 05/06/2017 09:23, Niels Thykier a écrit :
>
>> Probably done:
>> ==
>> * chapter 3 (?)
> See #864231
>
>> * chapter 4
> See #864227
>
Thanks, I have merged them now. Apologies for the delay.
With this
Hi,
Le 05/06/2017 09:23, Niels Thykier a écrit :
Probably done:
==
* chapter 3 (?)
See #864231
* chapter 4
See #864227
Let me know if you disagree with any of these.
English review done:
[...]
Timeline:
=
[...]
Thank you for handling this
Dear Niels,
El 5 jun. 2017 9:23 a. m., "Niels Thykier" escribió:
I admit it is not a lot of time to finish. But it should get us a lot
of the way while hopefully leaving enough time for everyone to do their
part.
Thank you for providing a plan for both proofreading, reviews and
translations
Hi,
Sorry for being a late with this.
The release notes are not quite done yet. Lets summaries this as:
Still opening:
==
We still expect changes to these chapters (in order of expected
frequencies of changes)
* chapter 5
* chapter 2
Probably done:
==
List of
Hi,
Frans Spiesschaert wrote:
> Please find attached an updated issues.po and whats-new.po for Dutch.
Thanks, just committed:
https://anonscm.debian.org/viewvc/ddp?view=revision&revision=11522
> I tested a local make of the Dutch release notes and it built
> successfully.
>
Baptiste Jammet:
> Hello,
>
> Dixit Niels Thykier, le 03/04/2017 :
>
>> Please let reply to this thread once the changes have been done, so I
>> can mark them as done in my checklist. :)
> Doing so, see
> https://lists.debian.org/debian-boot/2017/04/msg00336.html
> and
> https://lists.debian.or
Hello,
Dixit Niels Thykier, le 03/04/2017 :
>Please let reply to this thread once the changes have been done, so I
>can mark them as done in my checklist. :)
Doing so, see
https://lists.debian.org/debian-boot/2017/04/msg00336.html
and
https://lists.debian.org/debian-doc/2017/05/msg00012.html
>
On Mon, May 1, 2017 at 15:14:10 +0200, Florian Weimer wrote:
> * Julien Cristau:
>
> > The current state for the release notes is actually at
> > https://www.debian.org/releases/stretch/releasenotes
>
> It's not clear based on the architecture list in this docume
* Julien Cristau:
> On Mon, Apr 3, 2017 at 20:43:08 +0200, Florian Weimer wrote:
>
>> * Niels Thykier:
>>
>> > There is a security team related item in the release checklist where we
>> > need input from the you[1]:
>> >
>> > Items are:
On Mon, Apr 3, 2017 at 20:43:08 +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > There is a security team related item in the release checklist where we
> > need input from the you[1]:
> >
> > Items are:
> > * release-notes: Security Team
Holger Wansing:
> Hi,
>
> [...]
>
> After Samuel's commits
> https://anonscm.debian.org/viewvc/d-i?view=revision&revision=70661
> and
> https://anonscm.debian.org/viewvc/d-i?view=revision&revision=70695
> this issue is now done.
>
>
> Holger
>
>
Thanks for the follow up and thanks to Samuel
Hi,
Niels Thykier wrote:
> Samuel Thibault:
> > Holger Wansing, on dim. 26 mars 2017 19:16:00 +0200, wrote:
> >> Niels Thykier wrote:
> >>> There are two d-i related items in the release checklist that we need
> >>> input from the d-i team[1]
> >>>
> >>> Items are:
> >>> * Installation Guide sh
On Wed, Apr 19, 2017 at 09:44:00AM +, Niels Thykier wrote:
>Steve McIntyre:
>> Tried to commit this directly, but permission problems. I guess I
>> don't have write access?
>>
>> [...]
>
>Thanks, I have applied it.
>
>For commit access, you need to talk with the -doc team as I recall.
Ah, m
Steve McIntyre:
> Tried to commit this directly, but permission problems. I guess I
> don't have write access?
>
> [...]
>
>
Thanks, I have applied it.
For commit access, you need to talk with the -doc team as I recall.
Thanks,
~Niels
Tried to commit this directly, but permission problems. I guess I
don't have write access?
Index: en/whats-new.dbk
===
--- en/whats-new.dbk(revision 11433)
+++ en/whats-new.dbk(working copy)
@@ -396,23 +396,22 @@
CDs, DVDs,
* Niels Thykier:
> There is a security team related item in the release checklist where we
> need input from the you[1]:
>
> Items are:
> * release-notes: Security Team signoff for lower supported packages
>
> Please review the release notes and file bugs for the missing ite
Baptiste Jammet:
> Hi,
>
> Dixit Niels Thykier, le 03/04/2017 :
>
>>> * release-notes: d-i team signoff for specials with this update
>>> (check esp. if old versions of d-i should be purged if new versions
>>> enter $suite's d-i area)
>>>
Hi,
Dixit Niels Thykier, le 03/04/2017 :
>> * release-notes: d-i team signoff for specials with this update
>> (check esp. if old versions of d-i should be purged if new versions
>> enter $suite's d-i area)
>>
>
>I haven't heard anything about this ite
Hi,
There is a kernel team related item in the release checklist where we
need input from the you[1]:
Items are:
* release-notes: KernelTeam signoff for specials with the Kernel
Please review the release notes and file bugs for the missing items (if
any) and let us know once this has been done
Hi,
There is a security team related item in the release checklist where we
need input from the you[1]:
Items are:
* release-notes: Security Team signoff for lower supported packages
Please review the release notes and file bugs for the missing items (if
any) and let us know once this has been
ything else missing here
(https://lists.debian.org/debian-boot/2017/01/msg00369.html).
Does this mean that we are good to go once the above is fixed?
> * release-notes: d-i team signoff for specials with this update (check
>esp. if old versions of d-i should be purged if new versions enter
Samuel Thibault:
> Holger Wansing, on dim. 26 mars 2017 19:16:00 +0200, wrote:
>> Niels Thykier wrote:
>>> There are two d-i related items in the release checklist that we need
>>> input from the d-i team[1]
>>>
>>> Items are:
>>> * Installation Guide should be up-to-date
>>
>> There's one thread
re:
> > * Installation Guide should be up-to-date
> > * release-notes: d-i team signoff for specials with this update (check
> >esp. if old versions of d-i should be purged if new versions enter
> > $suite's d-i area)
>
> Please note, that the pdf varian
stallation Guide should be up-to-date
>> * release-notes: d-i team signoff for specials with this update (check
>>esp. if old versions of d-i should be purged if new versions enter
>> $suite's d-i area)
>
> Please note, that the pdf variants of the release-no
Holger Wansing, on dim. 26 mars 2017 19:16:00 +0200, wrote:
> Niels Thykier wrote:
> > There are two d-i related items in the release checklist that we need
> > input from the d-i team[1]
> >
> > Items are:
> > * Installation Guide should be up-to-date
>
> There's one thread coming to my mind:
[ Not an d-i issue, thus skipping debian-boot from the loop ]
Niels Thykier wrote:
> Hi,
>
> There are two d-i related items in the release checklist that we need
> input from the d-i team[1]
>
> Items are:
> * Installation Guide should be up-to-date
> * release-not
Hi,
Niels Thykier wrote:
> Hi,
>
> There are two d-i related items in the release checklist that we need
> input from the d-i team[1]
>
> Items are:
> * Installation Guide should be up-to-date
There's one thread coming to my mind:
https://lists.debian.org/debian-boot/2017/01/msg00369.html
H
Hi,
There are two d-i related items in the release checklist that we need
input from the d-i team[1]
Items are:
* Installation Guide should be up-to-date
* release-notes: d-i team signoff for specials with this update (check
esp. if old versions of d-i should be purged if new versions enter
Hi Holger,
> the machine www- master, which builds the release-notes, is running
> Jessie (at least for some months, until DSA has upgraded all machines
> to Stretch), and when the release-notes trunk was not fixed before, the
> pdfs are crippled again.
Ahh --- I see. Sorry for
Hi Norbert,
Am Mi. Feb. 24 01:08:41 2016 GMT+0100 schrieb Norbert Preining:
> Hi Holger,
>
> >Beside this, the same bug has to be fixed in the trunk branch of
> >release-notes as well, to make sure the problem does not re-occur after
> >the release of Stretch.
>
&g
Hi,
Julien Cristau wrote:
> On Sun, Feb 21, 2016 at 14:45:17 +0900, Norbert Preining wrote:
>
> > Hi Julien,
> >
> > > > > provide a patch against the release notes, I'd happily apply that.
> > > >
> > > > Sure enough, can you pl
Hi Julien,
> Thanks! I've applied your variant2 patch and installed fonts-sil-charis
> on www-master.
Ok, not optimal, but not too bad. Maybe we should discuss proper font
selection before the next release.
If there are any further problems, please don't hesitate to contact me!
All the best
N
On Sun, Feb 21, 2016 at 14:45:17 +0900, Norbert Preining wrote:
> Hi Julien,
>
> > > > provide a patch against the release notes, I'd happily apply that.
> > >
> > > Sure enough, can you please tell me where to get the sources that
>
> Here we
Hi Julien,
> > > provide a patch against the release notes, I'd happily apply that.
> >
> > Sure enough, can you please tell me where to get the sources that
Here we go.
There are several options - both boil down to changing the fonts to
opentype/truetype fonts. In
Hi,
Julien Cristau wrote:
> On Sat, Feb 20, 2016 at 21:53:00 +0900, Norbert Preining wrote:
>
> > Hi Julien,
> >
> > > That sounds like a reasonable workaround to me. Even better if you can
> > > provide a patch against the release notes, I'd happily
On Sat, Feb 20, 2016 at 21:53:00 +0900, Norbert Preining wrote:
> Hi Julien,
>
> > That sounds like a reasonable workaround to me. Even better if you can
> > provide a patch against the release notes, I'd happily apply that.
>
> Sure enough, can you please tell me
Hi Julien,
> That sounds like a reasonable workaround to me. Even better if you can
> provide a patch against the release notes, I'd happily apply that.
Sure enough, can you please tell me where to get the sources that
are responsible for the build of the broken release notes on
De
d this to the Russian reporter and done it myself
> for all release notes. It is damned easy to choose a different font.
>
That sounds like a reasonable workaround to me. Even better if you can
provide a patch against the release notes, I'd happily apply that.
Thanks,
Julien
Hi Adam,
> I have to admit that I'm not really keen on approving an update which
> consists of "add this tar to the source package". I'm also still not
Understandable.
> sure why the suggestion is to add the changes via such a binary update
> rather than a patch - I appreciate that the changes m
> So, could this bug now be planned to be fixed in 8.4?
I forgot to add - even if we do *NOT* want to fix dvipdfmx, there is
an easy way around, do not use type1 but otf/ttf fonts.
I have advised this to the Russian reporter and done it myself
for all release notes. It is damned easy to choos
On Sat, 2016-02-13 at 10:45 +0100, Holger Wansing wrote:
> Hi,
>
> Norbert Preining wrote:
> > Hi everyone, esp release managers
> >
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787759
> >
> > There are two bugs, one is the broken fonts, one is the
> > broken dvipdfmx for t1 fonts.
[
Hi,
Norbert Preining wrote:
> Hi everyone, esp release managers
>
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787759
>
> There are two bugs, one is the broken fonts, one is the
> broken dvipdfmx for t1 fonts.
>
> > This mail made me think about the status of this ...
>
> I asked rel
Hi everyone, esp release managers
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787759
There are two bugs, one is the broken fonts, one is the
broken dvipdfmx for t1 fonts.
> This mail made me think about the status of this ...
I asked release managers quite some time ago:
https://lists.d
On Sat, May 11, 2013 at 09:18:03PM +0200, Sune Vuorela wrote:
> [recipients trimmed]
> > I recommend applying the patch from bug #639300 in a stable update, instead
> > of leaving akonadi/virtuoso un-coinstallable with all ODBC drivers in
> > wheezy. Attached is an updated patch for this issue.
>
[recipients trimmed]
> I recommend applying the patch from bug #639300 in a stable update, instead
> of leaving akonadi/virtuoso un-coinstallable with all ODBC drivers in
> wheezy. Attached is an updated patch for this issue.
My recommendation is to have unixodbc drop the useless and broken Break
On Sat, May 11, 2013 at 02:26:22PM +0200, Bill Allombert wrote:
> > On Wed, May 8, 2013 at 16:45:09 -0500, Lukasz Szybalski wrote:
> > > The following packages have unmet dependencies:
> > > odbcinst1debian2 : Breaks: tdsodbc (< 0.82-8) but 0.82-7 is to be
> > > installed
> > > E: Error, pkgPro
On Sat, 2013-04-27 at 22:28 +0100, Ben Hutchings wrote:
> Since the 686 flavour has been removed, change the example to use the
> amd64 flavour and for i386 include a link back to the information about
> replacement of the 686 flavour.
Committed, thanks. (fwiw, the maintainer of the RN is -doc; th
Since the 686 flavour has been removed, change the example to use the
amd64 flavour and for i386 include a link back to the information about
replacement of the 686 flavour.
--- a/release-notes/en/upgrading.dbk
+++ b/release-notes/en/upgrading.dbk
@@ -836,7 +836,7 @@
-
+
Kernel flavour
lder releases over the
> > previous release cycles.
> >
> > Chromium - while build upon the Webkit codebase - is a leaf package, i.e.
> > if backporting becomes no longer feasible, there's still the possibility of
> > upgrading to a later upstream release (w
On Wed, Feb 2, 2011 at 21:01:44 +0100, Moritz Mühlenhoff wrote:
> Slightly modified (including the fact that there's in fact a LTS branch
> by Collabora and Red Hat):
>
Thanks, committed.
Cheers,
Julien
signature.asc
Description: Digital signature
ng becomes no longer feasible, there's still the possibility of
> upgrading to a later upstream release (which is not possible for the
> webkit library itself).
>
Should I include this in the release notes then, or does the webkit part
need changes?
Cheers,
Julien
signature.asc
Description: Digital signature
A rough overview of commits seems to show that only 5 translation
teams or individuals are keeping up with updates.
That's not a lot..:)
(please forgive me in advance if I forget about one language...and
feel free to correct this assumption)
signature.asc
Description: Digital signature
On Mon, Jan 10, 2011 at 06:47:21PM -0500, Michael Gilbert wrote:
> On Tue, 11 Jan 2011 00:40:42 +0100, Moritz Muehlenhoff wrote:
> > On Mon, Jan 10, 2011 at 11:12:39PM +0100, Josselin Mouette wrote:
> > > Heya,
> > >
> > > Le lundi 10 janvier 2011 à 20:56 +0100, Moritz Muehlenhoff a écrit :
> > >
On Wed, Jan 12, 2011 at 08:50:13PM +0100, Moritz Mühlenhoff wrote:
> On Mon, Jan 10, 2011 at 06:47:21PM -0500, Michael Gilbert wrote:
> > On Tue, 11 Jan 2011 00:40:42 +0100, Moritz Muehlenhoff wrote:
> > > On Mon, Jan 10, 2011 at 11:12:39PM +0100, Josselin Mouette wrote:
> > > > Heya,
> > > >
> >
On Mon, 2011-01-10 at 18:47 -0500, Michael Gilbert wrote:
> Also http://webkitgtk.org/?page=download. 1.2.6 is now available
> there (vice 1.2.5 in squeeze/sid), and I was going to look at packaging
> it. Not sure if it would be accepted for squeeze at this point though.
> However, it does look li
1 - 100 of 393 matches
Mail list logo
