> Am 10.05.2022 um 12:16 schrieb Miroslav Suchý :
>
> The workflow exists:
>
> The Change proposal guide you how to suggest release notes. E.g. I have one
> change in this release and I wrote
Yes, I know that. But, as far as I oversee, it’s not a (publication) workflow.
Dne 10. 05. 22 v 11:40 Peter Boy napsal(a):
Additionally, as fas as I see, docs team has no ==contentwise== workflow either
(and can’t provide one because it doesn’t govern the process). There is a
technical workflow, though, to ensure there is a file to be the next release
notes and a way to
our workflow
> are not discussed here.
Additionally, as fas as I see, docs team has no ==contentwise== workflow either
(and can’t provide one because it doesn’t govern the process). There is a
technical workflow, though, to ensure there is a file to be the next release
notes and a way to add cont
On Mon, May 9, 2022 at 11:17 PM Ben Cotton wrote:
>
> The #docs tag on Fedora Discussion is a better place to ask this
> question
Noted. It's quite confusing to me to see that parts of our workflow
are not discussed here.
> but the F36 docs will be published to the website prior to
> the release
The #docs tag on Fedora Discussion is a better place to ask this
question, but the F36 docs will be published to the website prior to
the release tomorrow. In the meantime, I've added them to the config
for docs.stg.fedoraproject.org, so you'll be able to see them there
after the next rebuild:
http
Hello.
I have recently contributed to the Fedora 36 Release Notes [1] and I need to be
able to link to that page.
However, despite the release in less than a day, I still see no Fedora 36
Release Notes at https://docs.fedoraproject.org
Is this a thing that is tracked and will happen when
I've decided to update to that in Fedora 36.
However, I do think this is worthy of a release note somewhere (not sure
what section). Can this still be done? How? Do I file a PR here
https://pagure.io/fedora-docs/release-notes ?
Hi Orion,
what's the status here, did this get some
t in Fedora 36.
> However, I do think this is worthy of a release note somewhere (not sure
> what section). Can this still be done? How? Do I file a PR here
> https://pagure.io/fedora-docs/release-notes ?
Hi Orion,
what's the status here, did this g
(not sure what section). Can this still be done? How? Do I
file a PR here https://pagure.io/fedora-docs/release-notes ?
Thanks.
--
Orion Poplawski
he/him/his - surely the least important thing about me
IT Systems Manager 720-772-5637
NWRA, Boulder/CoRA Office
On Thu, Sep 12, 2019 at 8:01 PM Miroslav Suchý wrote:
> Dne 02. 09. 19 v 13:57 Brian (bex) Exelbierd napsal(a):
> > Closing the loop: This package has been retired via `fedpkg retire` in
> f31 and rawhide.
>
> Can you add it to fedora-obsolete-packages? Otherwise the old version will
> remain on
Dne 02. 09. 19 v 13:57 Brian (bex) Exelbierd napsal(a):
> Closing the loop: This package has been retired via `fedpkg retire` in f31
> and rawhide.
Can you add it to fedora-obsolete-packages? Otherwise the old version will
remain on every Fedora machine.
--
Miroslav Suchy, RHCA
Red Hat, Associ
On Monday, August 5, 2019 4:42:31 AM MST Martin Kolman wrote:
> On Sat, 2019-08-03 at 03:45 -0400, Neal Gompa wrote:
>
> > On Sat, Aug 3, 2019 at 3:10 AM Brian (bex) Exelbierd
> > wrote:
> >
> > > Hi All,
> > >
> > > Barring objecti
Closing the loop: This package has been retired via `fedpkg retire` in f31
and rawhide.
regards,
bex
On Thu, Aug 1, 2019 at 10:43 PM Brian (bex) Exelbierd
wrote:
> Hi All,
>
> Barring objection, I plan to retire the release notes package from
> Fedora on or after August 9, 2019.
3:10 AM Brian (bex) Exelbierd
> > > > wrote:
> > > > > Hi All,
> > > > >
> > > > > Barring objection, I plan to retire the release notes package from
> > > > > Fedora on or after August 9, 2019. The package has not been
> updated
>
; > > >
> > > > Barring objection, I plan to retire the release notes package from
> > > > Fedora on or after August 9, 2019. The package has not been updated
> > > > since F28. Despite the fact that we have literally shipped a package
> > > &
On Mon, Aug 5, 2019 at 8:43 PM Martin Kolman wrote:
>
> On Sat, 2019-08-03 at 03:45 -0400, Neal Gompa wrote:
> > On Sat, Aug 3, 2019 at 3:10 AM Brian (bex) Exelbierd
> > wrote:
> > > Hi All,
> > >
> > > Barring objection, I plan to retire the releas
On Sat, 2019-08-03 at 03:45 -0400, Neal Gompa wrote:
> On Sat, Aug 3, 2019 at 3:10 AM Brian (bex) Exelbierd
> wrote:
> > Hi All,
> >
> > Barring objection, I plan to retire the release notes package from
> > Fedora on or after August 9, 2019. The package has
On Sat, Aug 3, 2019 at 3:10 AM Brian (bex) Exelbierd
wrote:
>
> Hi All,
>
> Barring objection, I plan to retire the release notes package from
> Fedora on or after August 9, 2019. The package has not been updated
> since F28. Despite the fact that we have literally
Hi All,
Barring objection, I plan to retire the release notes package from
Fedora on or after August 9, 2019. The package has not been updated
since F28. Despite the fact that we have literally shipped a package
containing the F28 release notes in F29 and F30, there have been no
comments. This
odhi and whatever other tooling
The changelog in the spec file could serve that purpose if we could get
rid of all the "rebuilt" entries. I would rather write the release notes
in the spec file than in a separate file. If the requirement for a new
changelog entry for every build cou
On Wed, Feb 14, 2018 at 10:00:18AM +0100, nicolas.mail...@laposte.net wrote:
> Actually, the problem is we're all talking about changelogs, when users ask
> for release notes.
> That's not exactly the same thing.
Yes! Thanks, that puts nicely what I'm trying to say. R
For a long time we have an issue with readiness of Release notes for a
release. To solve this issue me and @bex met and we came up with a
proposal for a Changes Policy [2] addendum. As I would like to have
people from different teams (Devel, QA, Doc, Trans, ...) to review
this proposal and I do
Hello Fedora packagers,
During each release cycle, the Fedora Release Notes are drafted on the
wiki[0]. This public draft space allows contributors to easily share
info on their work for the upcoming release. Later in the release
cycle, these wiki pages are frozen and converted into Docbook XML
Hello Fedora,
The Fedora 22 release cycle is in full swing, and beats have been opened
for the F22 Releasae Notes. Over the coming weeks, the release notes
for the next version of Fedora will be assembled by Docs team writers,
packageers, developers, and community members of all forms.
Yeah
/wiki/FundingRequest
Help with the F22 release notes
---
Fedora 22 is almost at the beta stage, with the final release slated
for May. That means it’s time to start writing the release notes, and
Fedora Documentation Project Lead Pete Travis put out a call for
volunteers
On Tue, Jul 16, 2013 at 12:45:43PM -0600, Pete Travis wrote:
>
> Yes, it is too late to change this. I might take time away from other work
> for outright factual errors and such, but not for an aesthetic
> reorganization.
By the way, there is one of those: the same entry mentions
/etc/system/ne
On Jul 16, 2013 11:22 AM, "Andrew McNabb" wrote:
>
> Fedora 19 has gone through yet another change to how network interfaces
> are renamed (biosdevname, etc.). This isn't mentioned in the "Changes
> in Fedora for System Administrators" section of the Release
Fedora 19 has gone through yet another change to how network interfaces
are renamed (biosdevname, etc.). This isn't mentioned in the "Changes
in Fedora for System Administrators" section of the Release Notes,
though it does seem to be in the Changes for Desktop Users section.
Is t
On Wed, May 15, 2013 at 12:04 AM, Dan Mashal wrote:
> On Mon, May 13, 2013 at 12:52 PM, John J. McDonough
> wrote:
> > We had a short discussion of this at this morning's meeting but felt a
> > broader discussion here was warranted.
> >
> > When preparing
On Mon, May 13, 2013 at 12:52 PM, John J. McDonough wrote:
> We had a short discussion of this at this morning's meeting but felt a
> broader discussion here was warranted.
>
> When preparing the Release Notes, we often ask the developers for wiki
> input, and generally come u
We had a short discussion of this at this morning's meeting but felt a
broader discussion here was warranted.
When preparing the Release Notes, we often ask the developers for wiki
input, and generally come up dry. More recently, we look though the
repos for changes, but the upstream re
From the docs@ list, FYI, in case someone has some time in which they
can contribute to release notes for desktop, system daemons, web
servers, or for that matter any other existing beats:
- Forwarded message from "John J. McDonough" -
On Tue, 2012-03-20 at 23:27 -0400, Chr
This release we seem to have gotten quite a few timely bugs, some of
them quite subtle. I thank all of you who took the time to pore over
the beta notes and submit bugs. Many of these subtleties the Docs
writers really can't pick up on, and your effort makes the release notes
that much b
Hi,
The release notes section in the feature pages are supposed to help with
writing the release notes and release announcement. However this is not
being taken seriously and feature owners just write something very brief
and useless most of the time.To highlight the problem, refer to
some
Pursuant to a conversation on the Docs team list, the
fedora-release-notes package is going to change ownership hands to its
true and rightful owner, jjmcd (John McDonough). He's really been
taking care of this package for some time so this is a formality.
There are a number of other peop
I will be converting the remaining beats tomorrow. If there are any
last minute additions, get them in now.
--McD
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
We are behind schedule on Release Notes. Most of the wiki beats have
been updated, at least for key features.
If you have been working on a beat, please review it and set the "Wiki
Good" indicator to 1 if you think it is OK on
https://fedoraproject.org/wiki/Category:Documentation_bea
On Tue, Sep 07, 2010 at 09:01:40AM -0400, John J. McDonough wrote:
> Certainly we would welcome more detail. You should feel free to provide
> it on the wiki.
> https://fedoraproject.org/wiki/Docs/Beats/Boot
*nod*
> I'm less sure about moving it. Since there were no other significant
> changes
rly before committing the changes.
If you can get the changes committed before 0337Z, then they will show
up in the overnight POTs and draft build.
The POT update runs fairly quickly, so L10N should have those well
before 0400Z each day. The draft build starts later and takes a while,
so the updated
On Tue, 2010-09-07 at 00:14 -0400, Matthew Miller wrote:
> On Mon, Sep 06, 2010 at 11:45:53AM -0400, John J. McDonough wrote:
> > A number of beats were blank, and some of them probably should be, but I
> > left them in the document for now as a reminder in case you are aware of
> > something that
On Mon, Sep 06, 2010 at 11:45:53AM -0400, John J. McDonough wrote:
> A number of beats were blank, and some of them probably should be, but I
> left them in the document for now as a reminder in case you are aware of
> something that is missing. I will get rid of them tomorrow.
Systemd needs more
On Tue, 2010-09-07 at 01:23 +0200, Jonathan MERCIER wrote:
> Le lundi 06 septembre 2010 à 11:45 -0400, John J. McDonough a écrit :
> > The wiki has been converted and a draft of the release notes is
> > available at
[clip]
> Why i do not see D programming ?
>
It's th
Le lundi 06 septembre 2010 à 11:45 -0400, John J. McDonough a écrit :
> The wiki has been converted and a draft of the release notes is
> available at
>
> http://jjmcd.fedorapeople.org/Download/Release_Notes/
>
> for your review. The sources are up to date in git, but the tr
The wiki has been converted and a draft of the release notes is
available at
http://jjmcd.fedorapeople.org/Download/Release_Notes/
for your review. The sources are up to date in git, but the translation
branch is not yet complete. I will go ahead and do that this afternoon.
If you could
One week from today we will begin preparing the Alpha Release Notes.
If you have an application you think should be mentioned in the Alpha
Notes please be sure your Feature page is concise and compelling.
The Alpha Release Notes are quite succinct, so not every new feature
will be mentioned, in
On Thu, Apr 15, 2010 at 4:21 PM, Paul W. Frields wrote:
> On Wed, Apr 14, 2010 at 06:33:38PM +0200, drago01 wrote:
>> On Wed, Apr 14, 2010 at 5:52 PM, Michael Cronenworth wrote:
>> > drago01 wrote:
>> >> PPC is no longer a primary arch, so the wording about supporting it
>> >> should be removed.
On Wed, Apr 14, 2010 at 11:47:50AM -0700, Adam Williamson wrote:
> On Wed, 2010-04-14 at 10:20 -0400, Paul W. Frields wrote:
> > The Documentation team has prepared and posted a draft of the Fedora
> > 13 Release Notes for the Beta release:
> >
> > http://docs.fe
On Wed, Apr 14, 2010 at 06:33:38PM +0200, drago01 wrote:
> On Wed, Apr 14, 2010 at 5:52 PM, Michael Cronenworth wrote:
> > drago01 wrote:
> >> PPC is no longer a primary arch, so the wording about supporting it
> >> should be removed.
> >
> > Sony recently removed "Other OS" support from all PS3 u
On Wed, 2010-04-14 at 10:20 -0400, Paul W. Frields wrote:
> The Documentation team has prepared and posted a draft of the Fedora
> 13 Release Notes for the Beta release:
>
> http://docs.fedoraproject.org/drafts.html
Thanks for updating the system requirements. However, this looks
On Wed, Apr 14, 2010 at 5:52 PM, Michael Cronenworth wrote:
> drago01 wrote:
>> PPC is no longer a primary arch, so the wording about supporting it
>> should be removed.
>
> Sony recently removed "Other OS" support from all PS3 units. Should the
> Playstation line be removed as well?
The Playstat
drago01 wrote:
> PPC is no longer a primary arch, so the wording about supporting it
> should be removed.
Sony recently removed "Other OS" support from all PS3 units. Should the
Playstation line be removed as well?
(I haven't updated my PS3 yet so I can still use Fedora)
--
devel mailing list
On Wed, Apr 14, 2010 at 4:20 PM, Paul W. Frields wrote:
> The Documentation team has prepared and posted a draft of the Fedora
> 13 Release Notes for the Beta release:
>
> http://docs.fedoraproject.org/drafts.html
PPC is no longer a primary arch, so the wording about supporting
On Wed, Apr 14, 2010 at 10:20:32 -0400,
"Paul W. Frields" wrote:
> The Documentation team has prepared and posted a draft of the Fedora
> 13 Release Notes for the Beta release:
>
> http://docs.fedoraproject.org/drafts.html
>
> It's recommended that devel
On Wed, Apr 14, 2010 at 10:20:32 -0400,
"Paul W. Frields" wrote:
> The Documentation team has prepared and posted a draft of the Fedora
> 13 Release Notes for the Beta release:
>
> http://docs.fedoraproject.org/drafts.html
>
> It's recommended that devel
The Documentation team has prepared and posted a draft of the Fedora
13 Release Notes for the Beta release:
http://docs.fedoraproject.org/drafts.html
It's recommended that developers check out sections that are relevant
or important to them. If you find that a page needs changes, you ca
Next week is the wiki freeze for Fedora 13 Release Notes.
If you have something important that needs to be in the release notes,
update the appropriate wiki beat.
Go to
http://fedoraproject.org/wiki/Documentation_Beats
and select the appropriate beat. Then add a note to that beat.
Your update
56 matches
Mail list logo
