Search Results

Search found 4 results on 1 pages for 'burnersk'.

Page 1/1 | 1 

• Understanding branching strategy/workflow correctly

  - by burnersk

  I'm using svn without branches (trunk-only) for a very long time at my workplace. I had discovered most or all of the issues related to projects which do not have any branching strategy. Unlikely this is not going to change at my workplace but for my private projects. For my private projects which most includes coworkers and working together at the same time on different features I like to have an robust branching strategy with supports long-term releases powered by git. I find out that the Atlassian Toolchain (JIRA, Stash and Bamboo) helped me most and it also recommending me an branching strategy which I like to verify for the team needs. The branching strategy was taken directly from Atlassian Stash recommendation with a small modification to the hotfix branch tree. All hotfixes should also merged into mainline. The branching strategy in words mainline (also known as master with git or trunk with svn) contains the "state of the art" developing release. Everything here was successfully checked with various automated tests (through Bamboo) and looks like everything is working. It is not proven as working because of possible missing tests. It is ready to use but not recommended for production. feature covers all new features which are not completely finished. Once a feature is finished it will be merged into mainline. Sample branch: feature/ISSUE-2-A-nice-Feature bugfix fixes non-critical bugs which can wait for the next normal release. Sample branch: bugfix/ISSUE-1-Some-typos production owns the latest release. hotfix fixes critical bugs which have to be release urgent to mainline, production and all affected long-term *release*es. Sample branch: hotfix/ISSUE-3-Check-your-math release is for long-term maintenance. Sample branches: release/1.0, release/1.1 release/1.0-rc1 I am not an expert so please provide me feedback. Which problems might appear? Which parts are missing or slowing down the productivity?

  Read the article

• How to download source, modify source, recompile and build .deb package?

  - by burnersk

  I have to customize my Apache2 suExec module to ensure some special environment variables getting passed through suExec. How to download the source code form Debian package apache2-suexec, modify suexec.c - safe_env_lst, recompile and build a .deb package again to rollout on the production systems? I tried apt-get source apache2-suexec but didn't found the suexec.c within the occurred apache2-* folder. The altered source code should be like this: static const char *const safe_env_lst[] = { /* variable name starts with */ "HTTP_", "SSL_", /* NEW: Perl debugging variables */ "PERL5OPT=", "PERL5LIB=", "PERLDB_OPTS=", "DBGP_IDEKEY=", /* NEW: FCGI variables */ "FCGI=", "FCGI_CONNECTION=", "FCGI_RUNTIME=", "FCGI_STARTTIME=", draft based on: http://static.askapache.com/httpd/support/suexec.c

  Read the article

• VirtualBox won't use any kind of hardware acceleration

  - by burnersk

  I see an problem with VirtualBox hardware acceleration functionality... My system configuration: MSI PH67A-C43 (B3) (BIOS: 2.70) Intel Core i5-2400 Windows 7 Professional SP1 64-bit Oracle VirtualBox 4.1.10 Oracle VirtualBox Extension Pack 4.1.10 I can select the individual acceleration options such as PAE/NX, VT-x/VMD-V or Nested Paging within VM-Settings but if I start the VM the accelerations will be disabled as of the tooltip from CPU (right next to shared folders). Each acceleration is "Disabled". Does this sounds familar to anybody? How can I solve this?

  Read the article

• How do I create a rule in Outlook 2010 that moves emails without special headers to a folder?

  - by burnersk

  I like to create a rule in Outlook 2010 that moves emails not containing a special string within the email header field message-id to a folder. How to do that? Pattern: not contains "SPECIAL-STRING". Example E-Mail: ... Date: Fri, 1 Sep 2012 11:16:32 +0100 Message-ID: <bla.bla.bla@SPECIAL-NOT-STRING> MIME-Version: 1.0 ... Hi there :) Pattern matches because "SPECIAL-STRING" is not present (note there is a "NOT" between the words). Automatically moves those emails to folder INBOX/other-mails.

  Read the article

1