Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Stable versions

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Stable versions

    I know this is a user forum, but maybe someone will see this... Can we get stable versions more often? Or at least backport bugfixes? It's been three months since the last stable release. I have features that need to go live that depend on bug fixes!

  • #2
    Re: Stable versions

    The relatively long timeframe between stable releases seems to coincide with the push for subscriptions over the last couple years, and there may be a relation. I believe the terms of subscriptions/licensing allow the subscriber to retain their current version of AA in perpetuity if they cease their subscription and had been a subscriber for a minimum period of time (somewhere between a six months and a year), but of course, they would not be eligible for further updates. Under this scenario, I would guess Alpha would claim that the subscriber only had the right to the most recent stable release version prior to ceasing their subscription, regardless of whether the subscriber had downloaded and was using a pre-release version. The longer the timeframe between stable releases, the longer the release notes become with interesting new features and bug fixes, and the more tempted are subscribers to renew their subscriptions. It's a bit of a cynical view, but a case one could make. Or, it could simply be the crush of new features takes much longer to test for stability.

    Sparticuz, coincidentally, I was thinking about this today when I saw your post. It would be nice if Alpha were on a regular and more timely schedule of stable releases.

    Comment


    • #3
      Re: Stable versions

      Personally, I'm not as concerned with new features as I am with bug fixes. Many different software vendors have the ability to publish bug fixes with the current version of the software while still developing new features on a separate development branch. I would be fine with a feature freeze and they release a point release every six months (or whatever), while still fixing bugs in the current stable version. As it stands we need to wait for bug fixes to be released simultaneously with feature releases. I totally understand the staffing issues this creates, but as you say, we are spending alot of money on these subscriptions, and I think we should have a reasonable expectation that bugs will be fixed and released in a timely manner (once a month?).

      Having said that, Every time I find and report a bug, it's fixed very quickly in the pre-release version, and am very happy with that. But, of course, I can't go into production with those fixes. As it stands now, I have migrated my version 11 app to version 12, but can't go live until a stable patch with my bug fixes comes out.

      Comment


      • #4
        Re: Stable versions

        I always run the pre-release version, and it's as stable as the release version. At least for existing features.

        In rare ocasions pre-release builds become unstable for a week or two, but it's not frequent.

        Comment


        • #5
          Re: Stable versions

          Unfortunately, I can't rely on that. 50-75 people depend on my application up and running daily to do their jobs.

          Comment


          • #6
            Re: Stable versions

            Hi Sparticuz,
            Originally posted by Sparticuz View Post
            ...I have migrated my version 11 app to version 12, but can't go live until a stable patch with my bug fixes comes out.
            Would you share what bugs are preventing you to go live with version 12?

            Thanks!!!
            Edhy Rijo
            Progytech
            (Computer Consultants)
            The makers of CardTracking.Net
            www.progytech.com

            Comment


            • #7
              Re: Stable versions

              Originally posted by Progytech View Post
              Would you share what bugs are preventing you to go live with version 12?
              Specifically, the 'show-stopping' bug was with custom ascii exports on grid where the extension was not honored. We are using custom exports to download _custom_ csv's for use with mail merges in Office, and this is a necessary, daily task that our Accountants and Office Managers use.

              Comment


              • #8
                Re: Stable versions

                Sparticuz, thanks for sharing this info.

                For whatever is worth, I am using Export to Excel without problems so far with build 1693-4196.

                Did you submit a bug report for the custom ascii exports?
                Edhy Rijo
                Progytech
                (Computer Consultants)
                The makers of CardTracking.Net
                www.progytech.com

                Comment


                • #9
                  Re: Stable versions

                  I can't use export to excel because the csv file is very custom. Yes, the bug was fixed in pre-release about 2 months ago...that's why I'm frustrated...

                  Comment


                  • #10
                    Re: Stable versions

                    Originally posted by Sparticuz View Post
                    .. Yes, the bug was fixed in pre-release about 2 months ago...that's why I'm frustrated...
                    I totally understand your frustration, it happened to me too last year when I decided to use A5 for one of my projects, I learned to leave with the pre-release and report bugs as fast as possible to keep moving my application, then stay with that version until I have the need to move to another pre-release.
                    Edhy Rijo
                    Progytech
                    (Computer Consultants)
                    The makers of CardTracking.Net
                    www.progytech.com

                    Comment


                    • #11
                      Re: Stable versions

                      1711-4211 is as stable as the released version. Probably more.

                      Comment


                      • #12
                        Re: Stable versions

                        Thanks Roger, that is good to know.
                        Edhy Rijo
                        Progytech
                        (Computer Consultants)
                        The makers of CardTracking.Net
                        www.progytech.com

                        Comment

                        Working...
                        X