[Google Code] New Home for WebLoginPE Bug/Template Reports

http://code.google.com/p/webloginpe/

Now that the project is on Google Code, we have a much easier way to track bug/template reports for not just the current release, but also for releases currently in development. Thus, instead of posting reports on the forum (where they can be buried and go unnoticed), we will be having all bug reports submitted via the following link...

http://code.google.com/p/webloginpe/issues/list

You will need a Google account to submit a bug/template report. As you start to type the labels for the issue report, Google will auto-suggest what to use. Here is the current list of labels (might change in the future as needed)...

Type-Defect = Report of a software defect
Type-Enhancement = Request for enhancement
Type-Task = Work item that doesn’t change the code or docs
Type-Review = Request for a code review
Type-Other = Some other kind of issue
Priority-Critical = Must resolve in the specified milestone
Priority-High = Strongly want to resolve in the specified milestone
Priority-Medium = Normal priority
Priority-Low = Might slip to later milestone
OpSys-All = Affects all operating systems
OpSys-Windows = Affects Windows users
OpSys-Linux = Affects Linux users
OpSys-OSX = Affects Mac OS X users
Milestone-1.3.1 = Stable code branch.
Milestone-1.3.2 = Beta = Beta code branch.
Milestone-1.4.0 = Alpha = Alpha code branch.
Component-Code = Issues regarding bugs in the code.
Component-Template = Issues regarding the templates.
Component-Lang = Issues regarding the lang files.
Component-Docs = Issue relates to end-user documentation.
Security = Security risk to users
Performance = Performance issue
Usability = Affects program usability
Maintainability = Hinders future changes

The most important labels are the Milestone and Component labels. Milestone shows which release you are working with, so we know what codebase the bugs reside in. Component let’s us quickly know what kind of bug we are dealing with at a glance. This helps us resolve issues quicker and easier. Type and Priority are also labels you should take a look at. OpSys deals with showing if a specific operating system is affected by the bug, although you will rarely ever have to use that label. Type-Enhancement replaces the "Feature Requests" topic we had. Use this if you want to suggest a change in a future release.

------------------------------

This is a link to all of the old bug report/suggestion topics. This is done so we do not have to keep them stickied, but developers can look through the topics in case we missed a bug that was previously reported, as well as for archival purposes.

Bug Reports - http://modxcms.com/forums/index.php/topic,18271.0.html
Template Issues - http://modxcms.com/forums/index.php/topic,27858.0.html
Feature Requests - http://modxcms.com/forums/index.php/topic,18272.0.html
Patches & Fixes - http://modxcms.com/forums/index.php/topic,18355.0.html

http://code.google.com/p/webloginpe/w/list

If you would like to help port over Scotty’s documentation to Google Code’s own Wiki, please feel free to do so. This is a community project, so anyone can help out. IIRC, you will need a Google account to edit / add new pages to the Wiki.

Who can add and edit pages to my wiki?

Only project members and owners can add and edit wiki pages for a particular project.

How do I join a project?

One of the project owners must use the project administration page to add your Google account email address to the project.

Stickies handled. Thanks for pushing forward with the effort!

I’m not really sure if I have done right but I made my ’multiple instances’ addition to v1.31 downloadable from
http://code.google.com/p/webloginpe/downloads/list

BobRay has told me to make a new ’branch’ but I’m completely new to an svn so I didn’t know how to do that.

Quote from: vhollo at Sep 09, 2008, 10:27 PM

I’m not really sure if I have done right but I made my ’multiple instances’ addition to v1.31 downloadable from
http://code.google.com/p/webloginpe/downloads/list

BobRay has told me to make a new ’branch’ but I’m completely new to an svn so I didn’t know how to do that.

You need a repository browser connected through something like TortoiseSVN. (You can also do it with the command-line version of SVN but I’m not used to working that way).

In the repository browser, you can right-click on the top-level directory (the one above "trunk") and create a "branches" subdirectory. There should also be a "tags" subdirectory added there. Then under the "branches" folder, add a "vhollo" folder and "commit" your work there using SVN. Other users can then merge your changes into the their working copy of the trunk and test them before you merge them into the trunk.

I tried to create the branch for you but my username and pwd were rejected so either I’ve forgotten them or I don’t have permission to create directories.

*update* I was able to create the tags and branches directories at Google Code. I think the problem was that I was trying to do it through IE7 rather than using an editor that integrates well with TSVN (PhpEd in my case).

I also created a vhollo branch and put a copy of the trunk there.  I hope vhollo can use it since I’m the "author" of it. We won’t know until he tries.

I use SVN a lot but not in a multiple-user scenario so feel free to jump in anyone and correct me if you have better suggestions about how to do this.

vhollo, the way for you to use the branch (I think) is to create an empty webloginpe directory on your machine, point your repository browser at the vhollo branch of the Google repository, and select "checkout."

This will give you a local copy of the trunk which is under version control. Make your changes to that copy, then use the "commit" command. That will put your new code in the Google repository in your branch. Others can then use "merge" to merge your changes into their copies and test them.

Information on using SVN can be found here: http://svnbook.red-bean.com/en/1.4/index.html.
Look especially at the section on branching and merging.

There is also information on branching, tagging, and merging using TSVN

here: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-branchtag.html
and here: http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-merge.html

It wasn’t easy and I left some ’strange footprints’ in the revisioning from 21 through 25 but finally succeded to add the "instances" version to the svn to my branch:
http://code.google.com/p/webloginpe/source/browse/#svn/branches/vhollo

Thanks for all the help, BobRay!

ps. What should I do with the uploaded zip at /downloads/list?

Quote from: vhollo at Sep 10, 2008, 04:30 PM

ps. What should I do with the uploaded zip at /downloads/list?

In theory, it shouldn’t ever be needed. But I guess there’s a chance that people without SVN might want to look at it at some point so maybe you could leave it there with a note about the branch.

Since we’ll have the stable download link going to MODx CMS, what do you guys think about using the Downloads tab at Google Code for beta releases of the script, since the "alphas" would be right from the SVN.

We could do a feature/addition freeze on the beta releases, ala Firefox/etc, and have those releases on GC.