As we mentioned two weeks ago, the final push to upgrade all remaining classic projects starts today. We’ll be starting with the longest-inactive projects, and working towards the present.
If you need to delay the upgrade for any reason, you must notify us immediately, so that we can add you to the delay list.
As I mentioned in the last platform updates post, we’re primarily focused on upgrade-related work lately, but we found time to put in a few enhancements to the platform in the last sprint.
A new macro was added to the wiki syntax. Putting [[members]] in a wiki article will produce a list of all the members of the project. By default, this is limited to 20 members, with a link to a full list if you’ve got more than that. You can link directly to that longer list, if you like. For example, here’s TikiWiki’s full list of developers.
Next, the interfaces for adding tags to tickets was improved to make it easier to find tags that you’ve already used. Starting to type a tag will produce a dropdown of tags from which to select.
And, we’ve added a $USER variable that you can use in ticket searches, which will be replaced, at search time, with the currently-active user. For example, if you search for reported_by:$USER, the variable $USER, you’ll get all the tickets reported by the currently logged in user. In this way, you can add a saved search to your ticket tracker so that each user can keep tabs on their own tickets.
So, if you look at the Allura ticket tracker, you’ll see a new “My Tickets” button under “Searches”, which will show you the tickets you’ve opened. (Of course, you’ll have to be logged in for that to work.)
We’re really looking forward to being done with the upgrade process, so that we can focus more on improving the developer experience, and we’d love to hear your feedback on what we should work on next. You can see what’s scheduled for upcoming sprints, and vote on tickets, in the Allura ticket tracker.
As you’re no doubt already aware, we’re in the process of upgrading projects to our new developer platform. The new platform is named Allura, and is in incubation at the Apache Software Foundation.
In recent weeks, we’ve been upgrading projects that have been inactive for a while. Now, it’s time to start upgrading everyone else. As you can no doubt understand, we’re anxious to complete this process so we can spend less time maintaining the old platform, and more time improving the new one. However, we also want to be sure that you have plenty of time to check out the new platform and have your concerns, if any, addressed.
We’re going to start upgrading active projects starting on Monday, April 22, starting with the longest-inactive and moving forward. Since each upgrade takes a different amount of time, depending on the size of the repositories, mailing list archives, and so on, we can’t tell for sure when we’ll get to your project.
If you’re ready to go ahead and upgrade your project now, or to read more what’s involved in the upgrade, you can do that at http://sf.net/p/upgrade/
If you have a specific concern about the upgrade, or need to delay the upgrade of your project, due to a release or other project activity, please get in touch NOW, at communityteam@sourceforge.net so that we can work something out.
As of this morning, you’ll notice a new feature in the SourceForge code browser. It’s pretty self-explanatory.
Clicking on the ‘Download Snapshot’ link will generate a tarball (tar.gz file) of the revision that you’re looking at. This snapshot is generated on the fly, so you’re certain to get the latest cut, but we cache that snapshot so that someone else requesting the same tarball won’t have to wait for it to generate.
If you’re interested, you can see the ticket and some of the implementation details in the ticket tracker, and you can see what else is coming down the road by perusing the upcoming milestones, also in the ticket tracker, and vote for stuff you’d like to see happen a little sooner.
Today’s push provides enhancements to ticket tracking, and the ability to compare selected revisions of a file, on the Allura platform, among other things.
First, we have a frequently-requested enhancement regarding assigning tickets to users. Rather than having to remember and type usernames, you can select from a list of project developers.
Or, if you prefer, you can type the username, which will do look-ahead searching of the available users that you could assign the ticket to.
This functionality is available for the ticket owner field, as well as any other field of type ‘User’ that’s attached to your tracker.
The full history of that issue may be seen in ticket #4299.
Next, we want to highlight a new feature in the code browser. You can now select specific revisions of a file and diff between them, either contextual or side-by-side.
In the screenshot, you’ll see two revisions selected. Revisions need not be contiguous.
Clicking the “Compare” button then shows the diff view for those revisions:
That’s in ticket #4929.
Other changes include a fix to bulk editing of tickets and the replacement of a component with an Apache-licensed alternative. This latter was needed as part of the Apache Software Foundation incubation of the Allura platform.
As always, you can see what’s coming in the near future by tracking the upcoming milestones in the Allura ticket queue, and you can influence what happens next by voting on the tickets you see there.
FileBot - The ultimate TV and Movie Renamer / Subtitle Downloader.