- 16 Jul, 2020 1 commit
-
-
Mattia Rizzolo authored
Signed-off-by:Mattia Rizzolo <mattia@debian.org>
-
- 17 Apr, 2012 1 commit
-
-
Arno Töll authored
accept uploads only if an user could be obtained by the GPG signature Implement a form validator to verify that the imported key matches the * profile mail address * Update CHANGELOG
-
- 15 Feb, 2012 2 commits
- 28 Jan, 2012 1 commit
-
-
Arno Töll authored
* Extend GnuPG interface * Drop the scary upload hash verification. Instead, use GnuPG to verify all uploads - drop all unsigned packages * Write an updatekeyring cronjob which updates the mentors keyring. * Update configuration files * Update CHANGELOG, postpone sponsoring guidelines to the next release
-
- 21 Jan, 2012 1 commit
-
-
Arno Töll authored
-
- 30 Dec, 2011 1 commit
-
-
Arno Töll authored
-
- 03 Dec, 2011 1 commit
-
-
Arno Töll authored
-
- 30 Nov, 2011 1 commit
-
-
Arno Töll authored
-
- 27 Nov, 2011 1 commit
-
-
Arno Töll authored
-
- 05 Nov, 2011 1 commit
-
-
Arno Töll authored
-
- 08 Oct, 2011 1 commit
-
-
Arno Töll authored
-
- 02 Oct, 2011 2 commits
-
-
Arno Töll authored
-
Arno Töll authored
This file is supposed to document every commit you do which is supposed to be publicly announced. Please log here bug fixes, new features and any other invasive change which should be announced to debian-mentors once this version is deployed. The syntax is similar to the debian/changelog format - Make a new entry for every version you intend to deploy to the production site, associate it with the last commit which is included with the merge to live: e.g. debexpo (0xdeadbeef) * I just deployed merged master to live, including changes up to commit 0xdeadbeef - Update author and timestamp with author, date and time who deployed the change to live - Announce changes to debian-mentors, you can use the most recent CHANGELOG entry to summarize all changes
-
- 30 Sep, 2011 1 commit
-
-
Arno Töll authored
This file is supposed to document every commit you do which is supposed to be publicly announced. Please log here bug fixes, new features and any other invasive change which should be announced to debian-mentors once this version is deployed. The syntax is similar to the debian/changelog format - Make a new entry for every version you intend to deploy to the production site, associate it with the last commit which is included with the merge to live: e.g. debexpo (0xdeadbeef) * I just deployed merged master to live, including changes up to commit 0xdeadbeef - Update author and timestamp with author, date and time who deployed the change to live - Announce changes to debian-mentors, you can use the most recent CHANGELOG entry to summarize all changes
-