On Thu, 2014-04-03 at 11:05 +0200, Tino Mettler wrote: > Hi Patrick, > > in the past, I also had issues with git tags that are updated > afterwards. I'd like some official announcement as part of the release > process for each tag to know if I can work with it. Usually, those > announcements were sent to this ML, but I'd to know if it is part of > the formal release process.
A tag is official once it got set on a "permanent" branch. Any branch that is called "for-<some other branch>/<purpose>" is a branch which may (and usually does) get rebased and thus isn't permanent. In addition, I announce new versions (and thus tags) here on the list. The problem you had is when a tag appears on a non-permanent branch because I am testing a release candidate in the nightly testing, which pulls from the official repos. If that fails, I fix the problem and try again with an updated tag. As you found out, one has to tell git explicitly to fetch tag updates to get the latest tags. I checked, using annotated tags does not help, one still has to pull tags explicitly. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
