Dear RG Team:

Chris wrote:
> Can we pause to agree on a definite policy for this kind of
> change?
> 
> This revision consisted partly of removing a feature, by
> commenting
> out a use of QUrl (in order to get the file to compile)
> rather than
> completing the conversion of it.  (Emanuel marked the
> omission with a
> big honking //@@@ comment -- it isn't just a silent
> change.)
> 
> What do we think of this kind of thing?  On the one hand it
> should
> permit building the application sooner; on the other hand
> it risks us
> leaving a feature incomplete and forgetting ever to restore
> it
> (especially if it's a subtle one).
> 
> I think I could agree to either policy -- "convert
> everything, leave
> nothing out" or "get it to compile and then put
> the lost bits back in"
> -- but whatever we do, we should be sure to agree on it, so
> that we
> can have a concerted effort to go and fix all the remaining
> //@@@
> points afterwards before releasing anything.

Well, I think we should convert most items.  I think if an item is too much 
work to convert, the person concerned should speak up before removing a feature.

I want stuff to compile, but I'd like to be informed as to which features are 
turned off and know everyone is on the same page.  I'm happy for you, Chris, to 
give the thumbs up or down on each case.  I typically defer to your desires 
concerning RG.

I definitely don't want to study each persons changes in detail--I don't have 
time for that.  I read the summary, and glance over the changes and move on.

I thought we already agreed not to do drastic changes without discussion first. 
 To me removing a feature is a drastic change.  I'd rather see the error at 
this point and know it is still available for fixing.  I usually just use the 
make error log as a reference for what needs completed.

Without discussing turning off or commenting out features first, I will not see 
the error in the log; I would not have heard about it--Unless the comment in 
the bug list says so; and there would be no mention of it in the wiki--unless 
someone is nice enough to add it.

....

So, I suggest we discuss this first, let Chris make the call, and indicate this 
in the wiki under things to do later.

Or, you can just ignore everything I say, and I'll just keep plugging away at 
the errors I know about.

Sincerely,
Julie S.



      

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to