Hello,
The release process takes a couple of hours to process, in my current procedure,
I'm pushing the tags at the end when emails are sent and everything is tested
and uploaded.
This is not the best practice, so, I will push the tags sooner in the process.
Best Regards,
Eric
On 04.06.21 18:50, Sven Hartge wrote:
On 04.06.21 17:18, Dan Langille wrote:
On Fri, Jun 4, 2021, at 8:19 AM, Sven Hartge wrote:
On 04.06.21 08:46, Eric Bollengier via Bacula-users wrote:
If something is wrong, a new release is made and tagged as well.
Same goes for the provided archives. Please don't remove existing ones
and replace them with other archives with the same version.
A project should never do this.
As a packager, you have now made my job much bigger than it needs to be.
This is a non-trivial situation. If there is a problem with the release,
create another release. Your downstream will have much more respect for you
than if you do otherwise.
Please, never do this.
You *can* remove releases, if there are broken or dangerous, I have no
problems with that.
But please, please, please, do not reuse the version when you create the next
unbroken release.
Also please tag the exact point that the released archives where made in GIT
immediately. There may be a time where we need to examine the contents of the
archives and compare them to the code in GIT.
Grüße,
Sven.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
