deal with profile structure in master branch #165
Labels
No labels
Done
bug
buildiso
buildpkg
buildtree
critical
deployiso
duplicate
enhancement
help wanted
in progress
invalid
manjaro-chroot
note
old-not-relevant
optional
question
sonar
todo
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tools/manjaro-tools#165
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created by: philmmanjaro
At least with the release of v0.10.0-rc1 we should have migrated master branch of our iso-profiles to its needed structure of devel branch.
Created by: philmmanjaro
See also: https://github.com/manjaro/manjaro-tools-iso-profiles/issues/87
Created by: udeved
Just curious, why would we have a rc1?
I find this kind of pointless, in my view, rc should be only assigned to 1.0-rc,
Created by: philmmanjaro
Fine with me, do you change some on the given v0.10.0 or not, or is it final then?
Created by: udeved
"Final" in the sense, that 0.10 could be released without feeling bad about it.
The structure is stable, so 0.10.x will be fixes, I played around with the logger for buildiso, we may add some more user override data in $HOME if we want and so, but I don't plan changes in profiles shared folder, except we find out, the Packages-Desktop files for sonar or netrunner are redundant.
Created by: philmmanjaro
Ok, fine with me. So everything is prepared and tested. Sounds good. We should inform all about the upcoming profile change and then no worries about it ;)