In general, the new package system is designed for developers to only interact with the PNR a single time, to create the package, and never again. This is why it leverages git/etc so that their normal processes are "just right".
Since creating an incompatible change creates a "new" package, I think it is justified in this model for them to return to the PNR. And, I like the idea that they don't need to "plan ahead" in any way for this sort of thing vis-a-vis their development infrastructure. Jay On Thu, Apr 4, 2013 at 9:15 AM, Laurent <laurent.ors...@gmail.com> wrote: > > >> >> > But I see that many packages on Planet2 are using the master as the >> > package >> > source. Then how do the developers manage major versions and >> > development? >> >> I believe that most of these developers do not intend to ever break >> compatibility. But if they do, they can tag the last "Version 1" >> commit, change the PNR to point to the tag, then create a new "Version >> 2" package that uses "master". The PNR source record can be changed >> whenever you want and it is not cached, etc by users, so when you >> change it, they will get the update just like usual. > > > Ah wonderful, that answers my concerns. > > Thank you very much for your answers. > > Laurent > -- Jay McCarthy <j...@cs.byu.edu> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 ____________________ Racket Users list: http://lists.racket-lang.org/users