On 8/30/12 12:42 PM, Luis Finotti wrote:
Firstly, thanks all for the replies.
On Thursday, August 30, 2012 12:54:31 PM UTC-4, Simon King wrote:
Hi Luis,
On 2012-08-30, Michael Orlitzky <mic...@orlitzky.com <javascript:>>
wrote:
>
> In general, if you're trying to sidestep the mercurial workflow,
....
Are you? It seems to me that following the mercurial workflow is the
thing to do here.
If I understand correctly, you want to do a change in an old Sage
version and then apply the same change to a new version, but you do not
want to post the change to trac. So, why not simply create a patch with
mercurial in the old version (perhaps using mercurial queues) and apply
it to the new version? Of course, you *could* post such patch on trac -
but nobody forces you to actually do so.
Posting a patch on trac would be the easiest thing for me (or at least I
have instructions on how to do it) and I don't mind doing it at all. My
concern is that the code, at this point, is not usable and does not
follow the recommendations for developers. I'd very much like to use
trac as my main version control repository, but it seems that I'd be
polluting it with sub par code until close to the very end (which I am
not sure how far ahead it will be). If that is OK, let me know and I
will just do that...
I post in-progress code to trac because:
1. It's a backup of the code. There has been several times when I
wanted to go back to an old patch and work on it more, but the only
place I could find it was a copy I had put up on trac.
2. It lets others know I'm working on it, so they can contact me if they
want to help, or if they're interested in testing, etc.
3. All too often, I don't have time to finish it. Sometimes others come
and finish the patch for me! (Thanks everyone!)
I just clearly label the code as in-progress and list the current state
and issues with the code. (At least, I try to do that).
If/when we move to github or to bitbucket or something, where people can
easily push their own branches, it will be much more natural to push
your in-progress code up and collaborate.
Thanks,
Jason
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
