Le mer. 22 janv. 2025 à 23:55, sebb <seb...@gmail.com> a écrit : > > On Wed, 22 Jan 2025 at 14:40, Gilles Sadowski <gillese...@gmail.com> wrote: > > > > Hi. > > > > Le mer. 22 janv. 2025 à 14:29, Gary Gregory <garydgreg...@gmail.com> a > > écrit : > > > > > > On Wed, Jan 22, 2025 at 8:00 AM Gilles Sadowski <gillese...@gmail.com> > > > wrote: > > > > > > > > Hi. > > > > > > > > Le mer. 22 janv. 2025 à 13:12, Gary Gregory <garydgreg...@gmail.com> a > > > > écrit : > > > > > > > > > > It's unclear to me if we need the PMC's approval for this. We > > > > > certainly did not vote on it. > > > > > > Well, I certainly would like to know exactly what is proposed here. > > > > I gave quite a few directions. > > If I knew _exactly_ I would have precise proposals... > > > > > Does this affect one component, all components, if not all components, > > > which components? > > > > All. The purpose is to have a _one_ stop (one command/one > > maven target) to generate the whole TLP site, at any time > > (whether it's for a release candidate or a simple update after > > correcting a typo in a "template", or in a layout engine, or > > within static contents). > > It must be possible to release updated component sites as well, > without needing to rebuild everything.
This seems one of many implementation details; we don't even know whether there will be a single git repository for the whole of Commons, or one repository per component. [I'd guess that, if site files are all generated uniformly (from a "plugin"?) across all components, a single repository seem less work (?) in the longer term.] > > > > [...] --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
