Search results
From K5Wiki
Create the page "Testing releases" on this wiki! See also the search results found.
- ...in its git repository in order to provide stability and tighter control as releases approach. Normally development is done on the '''[[Master branch|master br ...ty. So, the master branch does not meet the stability requirements of our releases.3 KB (441 words) - 15:36, 4 October 2012
- ...actice. However even if a given pullup could wait until another scheduled testing release it should be responded to before the current release.4 KB (631 words) - 13:50, 30 November 2007
- == Releases == Additional information on future releases:3 KB (441 words) - 18:02, 3 January 2017
- ...h an explicit list will inherently become out of date when future software releases update the default enctype lists. ==Implementation and Testing Notes==4 KB (555 words) - 00:12, 16 February 2010
- .... Pkinit contribution. Large sections of new code need better review and testing. ...tributions include comprehensive test suites? New hires will work on more testing for existing code.4 KB (649 words) - 17:39, 10 January 2011
- Keytab stash file status: Will recoded some stuff, is re-testing, (and multiple releases) out.1 KB (174 words) - 17:40, 10 January 2011
- ...elease branch. He'll be fixing some bugs and working on documentation and testing. ...to migrating away from single DES, as that is a priority for the next few releases.2 KB (279 words) - 23:57, 3 January 2011
- ...s not currently used under Windows, these violations are not discovered in testing and create minimal pain, but do render moot the efforts made by other piece ..._db_set_option. Since we have no compatibility promises for libkdb across releases, these should be inventoried and removed.16 KB (2,715 words) - 13:24, 12 October 2010
- ...itory that you can use to commit to the master SVN repository: [XXXX needs testing] ...some quirks that result from changes in git-svn behavior over various Git releases. If you run into problems as a result, it's probably easiest to start over5 KB (832 words) - 19:24, 16 July 2012
- ;Will: Glenn was working on code... what's the rule on testing for null before calling <code>free()</code>? ;Greg: We recently made a massive move toward not testing. [ Was needed a long time ago for platforms that had a conforming C compile3 KB (459 words) - 15:48, 21 June 2011
- ...e project-wide copyright years from the master branch before preparing KfW releases. Make sure src/windows/version.rc is updated in this commit. ...the build process, then pushed to the authoritative repository when basic testing is complete.5 KB (911 words) - 13:13, 7 April 2019
- *** If the change isn't covered by automated tests, consider testing it by hand. ...personal github fork and waiting for Github Actions to finish building and testing it.10 KB (1,709 words) - 14:44, 6 July 2023