#20: Request to tag FEL ks from master ----------------------------+----------------------------------------------- Reporter: chitlesh | Owner: kanarip Type: defect | Status: new Priority: major | Milestone: Fedora 11 RC Component: kickstart pool | Keywords: ----------------------------+----------------------------------------------- Hello there,
The fedora-livedvd-electronic-lab.ks has been updated to support the groupinstall @electronic-lab. This ks also fixes the dependencies issues which FEL spin failed during the last few days.
The new fedora-livedvd-electronic-lab.ks is in the master branch. Can you please from now on use this ks for FEL ?
The advantage of the structure used in this ks is to help us(FEL) divide the tasks among the FEL contributors.
All FEL apps goes to @electronic-lab. The rest of the software that enhance design experience are entailed on the ks.
#20: Request to tag FEL ks from master ----------------------------+----------------------------------------------- Reporter: chitlesh | Owner: kanarip Type: task | Status: assigned Priority: major | Milestone: Fedora 11 Beta Component: kickstart pool | Resolution: Keywords: | ----------------------------+----------------------------------------------- Changes (by kanarip):
* status: new => assigned * type: defect => task * milestone: Fedora 11 RC => Fedora 11 Beta
Comment:
Chitlesh, you *really* need to give commits to pull into the right branch.
E.g., I've now done;
git checkout F-11-Beta git cherry-pick 22b216589aae1c5d1cc6b9f5ff4e97f95009032b git push
I cannot just pull one file from master into F-11-Beta, I need to commit code(s)
Let me know if this is what you wanted.
#20: Request to tag FEL ks from master ----------------------------+----------------------------------------------- Reporter: chitlesh | Owner: kanarip Type: task | Status: assigned Priority: major | Milestone: Fedora 11 Beta Component: kickstart pool | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by chitlesh):
You have said in a mail on the mailing list that any updates to any ks should pass a review before tagging beta. This is the reason behind this ticket.
#20: Request to tag FEL ks from master ----------------------------+----------------------------------------------- Reporter: chitlesh | Owner: kanarip Type: task | Status: assigned Priority: major | Milestone: Fedora 11 Beta Component: kickstart pool | Resolution: Keywords: | ----------------------------+----------------------------------------------- Comment (by kanarip):
Replying to [comment:2 chitlesh]:
You have said in a mail on the mailing list that any updates to any ks
should pass a review before tagging beta. This is the reason behind this ticket.
Yes, I understand that, but you need to refer to the changes by commit code(s), or the merge might result in the wrong changes being pulled from one branch to another.
#20: Request to tag FEL ks from master ----------------------------+----------------------------------------------- Reporter: chitlesh | Owner: kanarip Type: task | Status: closed Priority: major | Milestone: Fedora 11 Beta Component: kickstart pool | Resolution: fixed Keywords: | ----------------------------+----------------------------------------------- Changes (by kanarip):
* status: assigned => closed * resolution: => fixed
Comment:
Closing the ticket as the appropriate commit has been pulled into F-11-Beta as per the conversation over IRC.
-
fedora-badges