"Dave Goodell (dgoodell)" <dgood...@cisco.com> writes:
> You're not wrong about the advantages of a merge-based workflow.  I
> just don't think it changes what the community is choosing to do right
> now.

No worries.  I didn't notice previous workflow discussion and I've seen
history repeat itself with minor variations many times over the years,
so I thought it was worth commenting.

>>> Put differently: the dev tag is solely for ordering of nightly snapshot 
>>> tarballs.
>> 
>> It affects git describe output as a side-effect and when someone writes
>> the mailing list with a bug in a year-old nightly snapshot, you'll need
>> to query the repository (or have a better memory than me) to have any
>> idea what they're working with.  Perhaps you are blessed with users that
>> don't do things like this.
>
> Checking the repo isn't particularly onerous, IMO.  It's a lot easier
> than searching old bug tickets, which you're also likely to need to do
> when dealing with bugs reported against old snapshots.  Also, there's
> almost no scenario where a user should be reporting bugs against a
> years-old "master" snapshot.  

I'm glad you have such delightful users. ;-)

Attachment: pgp9pTgoBHEBB.pgp
Description: PGP signature

Reply via email to