The branch 'f17' was created pointing to:
5f00cb3... Update repo commands to use branched release
On Tue, Feb 14, 2012 at 21:34:17 +0000, Dennis Gilmore ausil@fedoraproject.org wrote:
The branch 'f17' was created pointing to:
5f00cb3... Update repo commands to use branched release
Note this is a change from past practice. There are advantages and disadvantages to doing things this way. But mostly people should note that commits should be applied to both the F-17 and master branches for most changes going forward.
Bruno Wolff III (bruno@wolff.to) said:
On Tue, Feb 14, 2012 at 21:34:17 +0000, Dennis Gilmore ausil@fedoraproject.org wrote:
The branch 'f17' was created pointing to:
5f00cb3... Update repo commands to use branched release
Note this is a change from past practice. There are advantages and disadvantages to doing things this way. But mostly people should note that commits should be applied to both the F-17 and master branches for most changes going forward.
I asked about this on the releng channel. I'm working on comps file reorganization (as discussed at FUDCon, and on devel@), and if I start landing any of that in rawhide, it's going to break spin composition unless I can make the corresponding changes to someplace-other-than-F17 spin-kickstarts.
Bill
On Tue, Feb 14, 2012 at 17:05:27 -0500, Bill Nottingham notting@redhat.com wrote:
Bruno Wolff III (bruno@wolff.to) said:
I asked about this on the releng channel. I'm working on comps file reorganization (as discussed at FUDCon, and on devel@), and if I start landing any of that in rawhide, it's going to break spin composition unless I can make the corresponding changes to someplace-other-than-F17 spin-kickstarts.
That is a good reason for the change then. The reason that we hadn't in the past is that all of the changes were for the upcoming release and no one was doing stuff for the release after that so not branching made for less work and fewer errors of forgetting to commit to two branches. But if people are going to be working on F18 stuff now, then we want separate branches now.
Am Dienstag, den 14.02.2012, 17:05 -0500 schrieb Bill Nottingham:
Bruno Wolff III (bruno@wolff.to) said:
On Tue, Feb 14, 2012 at 21:34:17 +0000, Dennis Gilmore ausil@fedoraproject.org wrote:
The branch 'f17' was created pointing to:
5f00cb3... Update repo commands to use branched release
Note this is a change from past practice. There are advantages and disadvantages to doing things this way. But mostly people should note that commits should be applied to both the F-17 and master branches for most changes going forward.
I asked about this on the releng channel. I'm working on comps file reorganization (as discussed at FUDCon, and on devel@), and if I start landing any of that in rawhide, it's going to break spin composition unless I can make the corresponding changes to someplace-other-than-F17 spin-kickstarts.
Would you be willing to share some more details with us before you touch the kickstarts? What I have read on devel@ and heard at FUDCon was rather vague. I would like to see some files first, an actual implementation of what you have in mind. If there is a wiki page, that's fine, too.
Kind regards, Christoph
P.S.: That should propably be discussed on devel@ since it affects more people than just the spins SIG.
Christoph Wickert (christoph.wickert@googlemail.com) said:
Am Dienstag, den 14.02.2012, 17:05 -0500 schrieb Bill Nottingham:
Bruno Wolff III (bruno@wolff.to) said:
On Tue, Feb 14, 2012 at 21:34:17 +0000, Dennis Gilmore ausil@fedoraproject.org wrote:
The branch 'f17' was created pointing to:
5f00cb3... Update repo commands to use branched release
Note this is a change from past practice. There are advantages and disadvantages to doing things this way. But mostly people should note that commits should be applied to both the F-17 and master branches for most changes going forward.
I asked about this on the releng channel. I'm working on comps file reorganization (as discussed at FUDCon, and on devel@), and if I start landing any of that in rawhide, it's going to break spin composition unless I can make the corresponding changes to someplace-other-than-F17 spin-kickstarts.
Would you be willing to share some more details with us before you touch the kickstarts? What I have read on devel@ and heard at FUDCon was rather vague. I would like to see some files first, an actual implementation of what you have in mind. If there is a wiki page, that's fine, too.
https://fedoraproject.org/wiki/Features/ReworkPackageGroups
Will probably send some diffs around before anything goes on master.
Bill
Am Mittwoch, den 15.02.2012, 15:08 -0500 schrieb Bill Nottingham:
Christoph Wickert (christoph.wickert@googlemail.com) said:
Am Dienstag, den 14.02.2012, 17:05 -0500 schrieb Bill Nottingham:
Bruno Wolff III (bruno@wolff.to) said:
On Tue, Feb 14, 2012 at 21:34:17 +0000, Dennis Gilmore ausil@fedoraproject.org wrote:
The branch 'f17' was created pointing to:
5f00cb3... Update repo commands to use branched release
Note this is a change from past practice. There are advantages and disadvantages to doing things this way. But mostly people should note that commits should be applied to both the F-17 and master branches for most changes going forward.
I asked about this on the releng channel. I'm working on comps file reorganization (as discussed at FUDCon, and on devel@), and if I start landing any of that in rawhide, it's going to break spin composition unless I can make the corresponding changes to someplace-other-than-F17 spin-kickstarts.
Would you be willing to share some more details with us before you touch the kickstarts? What I have read on devel@ and heard at FUDCon was rather vague. I would like to see some files first, an actual implementation of what you have in mind. If there is a wiki page, that's fine, too.
https://fedoraproject.org/wiki/Features/ReworkPackageGroups
Will probably send some diffs around before anything goes on master.
Given that the feature has not been approved by FAmSCo and there are no technical deatils, this makes a lot of sense.
Regards, Christoph
El Tue, 14 Feb 2012 16:00:07 -0600 Bruno Wolff III bruno@wolff.to escribió:
On Tue, Feb 14, 2012 at 21:34:17 +0000, Dennis Gilmore ausil@fedoraproject.org wrote:
The branch 'f17' was created pointing to:
5f00cb3... Update repo commands to use branched release
Note this is a change from past practice. There are advantages and disadvantages to doing things this way. But mostly people should note that commits should be applied to both the F-17 and master branches for most changes going forward.
notting was planning to start to land the changes for f18 see the recent devel list thread on "Package categorization and distribution construction" so the changes needed on f17 and master are likely to differ.
Dennis
-
Bill Nottingham -
Bruno Wolff III -
Christoph Wickert -
Dennis Gilmore