[aur-general] Upgrading a beta package?
Hi, I currently maintain the netbeans-beta package in the AUR. I was wondering, since netbeans was updated to 8.0 today (not yet in the official repositories), whether I should leave it at the latest development release (rc1) or upgrade to stable. Of course if/when 9.0 beta is released I will upgrade to that, but I don't know what the package should be in the meanwhile. Are there any official guidelines about this? (I wasn't able to find them on the wiki.) Thanks, Evert Van Petegem
On Wed, Mar 19, 2014 at 10:55 AM, Evert Van Petegem <evert.van.petegem@gmail.com> wrote:
Hi,
I currently maintain the netbeans-beta package in the AUR. I was wondering, since netbeans was updated to 8.0 today (not yet in the official repositories), whether I should leave it at the latest development release (rc1) or upgrade to stable. Of course if/when 9.0 beta is released I will upgrade to that, but I don't know what the package should be in the meanwhile. Are there any official guidelines about this? (I wasn't able to find them on the wiki.)
Thanks,
Evert Van Petegem
What are you trying to give to your users? Are you intending to provide a "currently beta if there is one" package or are you intending to provide a "forever beta" package? In the latter case I, personally, would think twice if I really wanted to use the package. cheers! mar77i
I don't think there's any particular policy regarding which package versions should be provided by a *-beta package. That said, I agree with Martti Kuhne: a "beta if there is one" package makes much more sense than an "always beta" package. In other words, always keep the *-beta package as up to date as possible. -- Jeremy
I don't think there's any particular policy regarding which package versions should be provided by a *-beta package. That said, I agree with Martti Kuhne: a "beta if there is one" package makes much more sense than an "always beta" package. In other words, always keep the *-beta package as up to date as possible.
I agree. I maintain rubymine-eap and decided to keep it as up-to-date as possible after some time. No EAP version currently? Official release is provided. This allows the users to use the newest possible version of software and not to worry about switching between rubymine and rubymine-eap. -- Kind regards, Damian Nowak StratusHost www.AtlasHost.eu
participants (4)
-
Evert Van Petegem
-
Jeremy Audet
-
Martti Kühne
-
Nowaker