Re: [WEBSITE] More Fully Move to Git

On Fri, Aug 6, 2021 at 7:45 PM Dave Fisher wrote: > ...The branches are renamed: > > - status/projects > - status/ip-clearance > - status/clutch ... Great, thank you! Such prefixes will definitely help. -Bertrand - To

Re: [WEBSITE] More Fully Move to Git

Hi - > On Aug 6, 2021, at 6:15 AM, Bertrand Delacretaz > wrote: > > On Fri, Aug 6, 2021 at 2:43 PM Greg Stein wrote: >> >> Branches for a purpose are appropriate... > > Absolutely agreed! Ditto. Better one repository than 100s in most cases. (I understand why Sling is special ;-) ) > >

Re: [WEBSITE] More Fully Move to Git

On Fri, Aug 6, 2021 at 2:43 PM Greg Stein wrote: > > Branches for a purpose are appropriate... Absolutely agreed! But (to me) on GitHub the role of each branch can be hard to figure out, so I think that needs to be explicitly documented. Using conventions for branch names might help, like

Re: [WEBSITE] More Fully Move to Git

Branches for a purpose are appropriate. Avoiding that tool/feature, and (say) using distinct repositories is a version control anti-pattern. Cheers, -g On Fri, Aug 6, 2021, 03:59 Bertrand Delacretaz wrote: > Hi Dave, > > On Thu, Aug 5, 2021 at 6:39 PM Dave Fisher wrote: > > ...In Pelican we

Re: [WEBSITE] More Fully Move to Git

Hi Dave, On Thu, Aug 5, 2021 at 6:39 PM Dave Fisher wrote: > ...In Pelican we will have two branches for each directory... Just a quick comment on this: I often get crazy with repositories which use multiple branches "for production use" as they are often not discoverable. If you go this route

Re: [WEBSITE] More Fully Move to Git

> On Aug 5, 2021, at 5:47 AM, Bertrand Delacretaz > wrote: > > Hi Dave, > > On Wed, Aug 4, 2021 at 9:32 PM Dave Fisher wrote: >> ...I plan to complete the move of many of the files that are maintained by >> projects >> into an ASF-Pelican workflow like I recently completed for

Re: [WEBSITE] More Fully Move to Git

Hi Dave, On Wed, Aug 4, 2021 at 9:32 PM Dave Fisher wrote: > ...I plan to complete the move of many of the files that are maintained by > projects > into an ASF-Pelican workflow like I recently completed for www.apache.org... https://github.com/apache/incubator is currently built using JBake,

[WEBSITE] More Fully Move to Git

Hi - See https://issues.apache.org/jira/browse/INCUBATOR-268 I plan to complete the move of many of the files that are maintained by projects into an ASF-Pelican workflow like I recently completed for www.apache.org and other websites including httpd.apache.org