[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-dev
Subject:    =?UTF-8?Q?Re:_svn_commit:_r1886396_-_in_/subversion/site/publish:_./_doa?= =?UTF-8?Q?p.rdf_docs/rele
From:       "Daniel Shahaf" <d.s () daniel ! shahaf ! name>
Date:       2021-02-16 20:36:47
Message-ID: 01ededbd-015f-41e3-9a34-aa7490d41ecf () www ! fastmail ! com
[Download RAW message or body]

Daniel Sahlberg wrote on Tue, 16 Feb 2021 13:05 +00:00:
> Den tis 16 feb. 2021 kl 13:15 skrev Stefan Sperling <stsp@elego.de>:
> > On Tue, Feb 16, 2021 at 01:05:32PM +0100, Daniel Sahlberg wrote:
> > > What do you think about this?
> > > [[[
> > > List the new release on ^/subversion/site/publish/doap.rdf
> > > There should be a <release> section for each supported minor release
> > > with the <created> and <revision> being updated to the current release
> > > date and patch release number.
> > > Do not change anything else in the file (in particular the <created>
> > > under <Project> is the date when the Subversion project was created).
> > > ]]]
> >
> > That is crystal clear and should avoid mistakes going forward. Thank you!
> 
> r1886589

Is it worthwhile to automate this step?  doap.rdf changes rarely enough
that we needn't bother with "edit part of a file" logic; we can just
regenerate the entire file and  «svnmucc put » it into place, with a
comment indicating it's a generated file.
[prev in list] [next in list] [prev in thread] [next in thread]