On Sat, 2021-01-09 at 18:59 +0100, Hervé BOUTEMY wrote: > Le samedi 9 janvier 2021, 12:53:04 CET Oleg Kalnichevski a écrit : > > On Sat, 2021-01-09 at 10:09 +0100, Hervé BOUTEMY wrote: > > > Hi Oleg, > > > > ... > > > > > I know this was a long email, but there is no easy magic > > > solution: > > > there are > > > multiple solutions with pros and cons. Then it's all about > > > understanding > > > before deciding to move or not. > > > You currently have a working solution, that IMHO only has a > > > scaling > > > issue: > > > perhaps scaling is not a requirement for you. > > > > Hi Hervé > > > > Thank you so much for helping us and sharing your knowledge and > > experience with us. It is truly appreciated. > > > > The only important objective for me is to ensure that update and > > deployment of non-versioned content should not require a formal > > release > > and a release vote and ideally could be done by raising a PR with > > the > > website project by an external contributor. > since we did the work in november, you have this, isn't it? >
Yes, pretty much, but what I understood from what Michael has said, you intend to start moving non-versioned content from the main website projects to individual projects (sub-projects). This does not sound right to me. > > I personally think publishing release (version) specific content > > (project reports) to the artifact repository during a formal > > release is > > a very simple, practical, cheap and conceptually clean solution to > > the > > project, so I do not quite understand an aversion to this idea. > Ok I lost you with too many explanations. > I'll explain more in details the issues with the current setup. > Apart from the scalability issue, if in the future you added many > components > or many branches... > > Currently, in the versioned content, you have a multi-module site > that is > quite non-functionnal, because of the intermediate files stored in > the same > directory. > Example: > http://hc.apache.org/httpcomponents-core-5.1.x/project-reports.html > If you follow links from the left "Modules" menu, the links point to > "Not > Found" index.html: if you remove the last "index.html", you see the > module > content. > > If we look at svn view > https://svn.apache.org/viewvc/httpcomponents/site/httpcomponents-client-5.0.x/ > > The root cause is that this directory is supposed to be the > httpcomponents-client release documentation, but it also contains > some unversioned content (= > with "svn-site-role" Author) > > If we simply clearly split the versioned release documentation from > the > unversioned content, it would make things much more clean and we > could improve > the release documentation > Like having the release documentation in > http://hc.apache.org/httpcomponents-core-5.1.x/doc > > > I understand that my explanations seem theoretical and hard to > really > evaluate. > This can be tested easily without breaking the current setup, but by > adding > normal documentation fir the current SNAPSHOT: if you trust me, I can > work with > Michael to show that > > Are you interested? > I still do not quite what exactly you intend to do but whatever approach you take, as long as we do not need a formal release to publish non-versioned content, I would be interested to see it. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
