Decide what to do with master and development code #276
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 milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tools/manjaro-tools#276
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
We should review both branches and decide what to do about them.
I think it makes little sense to move to dev branch. It is very different and when I last tested there were some issues afai remember.
diff is huge and practically impossible to compare ...
master seems to be working fine. I would opt to stick with it and go from there.
Created by: philmmanjaro
Master has to be reviewed also. We will see when we find time. I've released v0.15.4 for now.
ah well I meant master 😉
I don't see why we need to move everything again to different files, change var names. It's like starting over again. The diff is a total mess. No idea why we would need to do that.
Created by: philmmanjaro
Maybe some good code is there. Else we ditch it and go with v0.15.4 ;)
Created by: Chrysostomus
Just read through the diff. Much moving code around. Help command gives info about -U flag. Cleaning out the parts that configure thus. Some work towards supporting calamares netinstall better.
If master works as is and devel does not, I would stick with master and ditch devel. Maybe incorporate some specific commits. But in principle take master and work forward from there.
Btw, is netinstall with calamares something that we are actively working towards, or was that more of artoos own thing?
Created by: philmmanjaro
I think the net-install got modified upstream already, so we have to check if it still works. Anyway, if we find some useful code, we may use it. I had no time yet to even review the master changes yet.
my understanding is that we were considering to go on from stable-15.x branch - which is again a LOT different from master! 😉
Created by: philmmanjaro
Yep. That was the old code. Master was some like v0.16.0 ish, which might need some backports from v0.15 series. If no need we may ditch both and stick with v0.15.
Closing stale issue