You can find me around as tosky.
- User Since
- Apr 18 2015, 1:18 PM (242 w, 18 h)
Oh sorry, I missed that. It's the kind of information I wouldn't expect in the commit message.
Please commit it after the commit for the new Frameworks is made (so probably from Sunday onwards).
Fri, Dec 6
Thu, Dec 5
Wed, Dec 4
Tue, Dec 3
It only means that we need to plan the migration ourselves.
Mon, Dec 2
Sat, Nov 30
Fri, Nov 29
I think the removal of https://community.kde.org/Release_Team is a mistake. In fact there is an active release-team@ list, and it is worth having a page which describes it. It should be updated instead.
Thu, Nov 28
Wed, Nov 27
Tue, Nov 26
The release-team@ list is the place where to raise blockers.
Mon, Nov 25
Why should cervisia change from CVS? It's exactly what it is. It's not a generic interface to a generic content versioning system, but the interface to a specific one (CVS, which is Concurrent Versions System, but I bet that 90% of my colleagues would recognize it only be the acronym).
No need to change it here - we have definitely more work to do to switch every script to Python 3.
Sun, Nov 24
It's rare because people don't use it.
Maybe pinging a few Plasma people may be more effective, or though a mailing list thread. I don't know.
Sat, Nov 23
Fri, Nov 22
Before anything else you need to change the commit message (yes, just here, because reasons):
Thu, Nov 21
Wed, Nov 20
Tue, Nov 19
Mon, Nov 18
Sun, Nov 17
Anyway, the real world process is not even the one you are describing. The point is here is not to fix this set of script: it's to throw it away in the long run and have it something more flexible. Hence a minimal amount of work should go into keeping this scripts alive. Each branch can live on its own own until it's unified.
What is the gain? This branch can stay as it.
Sat, Nov 16
I disagree with this approach (see the other task).
And of course the kde4 branches won't need.any update: one is already gone, the other will be soon.
As I write initially:
- separate branches, as it's easier to adapt the current code;
- later we will transition all kf5 branches to use master, in a non disruptive way.
Fri, Nov 15
Thu, Nov 14
But we have been discussing about the naming and scope of the Applications releases way before the All About The Apps initiative. I think that @jriddell mentioned that it's consistent with the All About The Apps initiative, but at least I see the two changes unrelated to each other. Not sure what the others think about this.