[Coco] Looking for Most Recent Vcc. Executable for Windows.

[Bill Pierce]

That was similar to what I've was thinking. We definitely need a "temp" branch for pushing our new changes, but also a stable "release" branch that reflects the current release.


-----Original Message-----
From: edward jaquay <ejjaquay at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Sat, Aug 21, 2021 4:41 pm
Subject: Re: [Coco] Looking for Most Recent Vcc. Executable for Windows.

Regarding creating a branch for each release.  That would be less confusing
than having the working branch named after an older release.  But since we
are not currently patching old releases we really don't need to keep old
branches.  Github keeps track of the release tags and the old source is
always still there.  .I am more in favor of naming the working branch
something that does not change with the releases and perhaps having a beta
branch that is a few commits ahead of what we are sure of for the next
release.

-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco