On 13 Jul 2021, at 10:20, Eric Timmons wrote:
Attila Lendvai writes:
what i would do:
- one branch that holds the bleeding edge. i'd call it main, just
to go
with the flow.
- branches for ASDF versions (down to the desired resolution,
probably
major.minor), so that you can
>
> Nah, a tag is supposed to never change. The mechanism for a "tag that
> changes" is called... a branch.
the user story that i desire is a label that someone with the commit bit
can move around freely, and then it gets automatically synchronized to
everyone else who pulls/fetches the repo
Attila Lendvai writes:
> what i would do:
>
>- one branch that holds the bleeding edge. i'd call it main, just to go
>with the flow.
>- branches for ASDF versions (down to the desired resolution, probably
>major.minor), so that you can easily cherry pick or backport fixes into
>
On Tue, Jul 13, 2021 at 9:34 AM Attila Lendvai wrote:
>>
>>
>> Would the "stable" branch be any different from the "release" branch?
>> If it's actually a not-so-stable development branch for 3.3 while a
>> separate branch contains development for 3.4, then maybe indeed
>> calling branches v3.3
>
>
> Would the "stable" branch be any different from the "release" branch?
> If it's actually a not-so-stable development branch for 3.3 while a
> separate branch contains development for 3.4, then maybe indeed
> calling branches v3.3 and v3.4 make more sense.
>
>
+1
what i would do:
- one
