On Aug 1, 7:27 am, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > On 2011-07-29 22:44, kcrisman wrote: > > > Right, but it would also seem that it is unwise to (say) try to add > > functionality on top of 4.7.1.rcx when tickets for overlapping code > > say "merged in 4.7.2.alphay". So, at least while Jeroen is release > > manager (which very happily seems to be an ongoing thing!) they must > > have some additional status than someone else's random fork-y 4.7.2, > > right? > > > So it would be helpful to have some clarification, if only to avoid > > rebasing. > > It's simply hard to say. If a ticket mentions "merged in > sage-4.7.2.alpha0", then it is very likely that it will be merged in > sage-4.7.2.alpha0. In practice, it will be merged unless there is some > obvious reason not to merge it.
:) > Keep in mind that non-released versions can change quickly. So your > sage-4.7.2.alpha0 downloaded today could be different from the > reviewer's sage-4.7.2.alpha0 downloaded tomorrow. So go ahead and > download non-released versions, but only use it for private development: > do NOT report bugs and do NOT post patches on top of that version. Maybe that is too strong. Instead, perhaps one should say that once a ticket #1234 is 'merged' in such a prerelease of an alpha, one might as well assume it will be merged before any ticket that depends on #1234, so one should say "depends on #1234" in one's new ticket for reviewers, rather than hoping one's new ticket #4321 will be merged first or something causing #1234 to be rebased. So that the prereleases are 'official' in the sense that once something is in it, it's wise to base on those tickets, but not necessary or advisable to download that actual version en masse. - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
