26.04.2011 22:10, Christian Ohm wrote:
I'd like to see a move towards a process that doesn't result in countless
started things that need to be finished before we can even begin to think
about
a release.
But isn't this one of the inherent problems of FLOSS development?
Regards
- Kreuvf
On Wednesday, 27 April 2011 at 9:53, Kreuvf wrote:
26.04.2011 22:10, Christian Ohm wrote:
I'd like to see a move towards a process that doesn't result in countless
started things that need to be finished before we can even begin to think
about
a release.
But isn't this one of the
On 2011-04-24 12:43, Christian Ohm wrote:
0. New features are developed in feature branches. Bugfixes to a specific
feature go into the feature branch as well, even after it got merged.
(Generally, merges go only in one direction, no back-merges from master into
other branches.)
1. Merge
On Wednesday, 27 April 2011 at 20:54, Fastdeath wrote:
What I do not quite understand:
(Generally, merges go only in one direction,
no back-merges from master into other branches.)
that means we are not allowed to back merge branch unrelated bugfixes?
That means that you don't
#2673: The login page should have more info
--+-
Reporter: dak180 | Owner: Fastdeath
Type: bug |Status: new
Priority: normal | Milestone: unspecified
Component: Website |
#2674: Formatting buttons show up inconsistently
-+-
Reporter: dak180 | Owner:
Type: bug |Status: new
Priority: normal | Milestone: unspecified
Component: other | Version:
